newscanonical for TYPO3

Missing canonical tags create duplicate content and cost TYPO3 news pages their rankings

A tx_news article is often reachable via three or more URLs: through the category path (/news/marketing/article-title), through the archive (/news/2025/03/article-title) and through a direct link (/news/article-title). Visitors notice no difference, but for Google it is a problem. Google sees three separate pages with identical content and has to decide which one is the “right” one. Without a canonical tag pointing to the preferred URL, Google splits the ranking signals across all variants and weakens each of them. newscanonical solves this for tx_news by generating a canonical tag on every news detail page that points to the definitive URL.

The extension is a focused SEO tool that does exactly one job: preventing duplicate content in tx_news. For websites with 100+ news articles, that can make the difference between page one and page three of Google’s results.

Typical use cases are news websites, magazines and press areas

The standard scenario is a corporate website with a news or blog section. A company publishes articles every week and files them under categories (products, industries, events). Each article appears both in its category list and in the overall archive. Without newscanonical, Google indexes every URL variant separately, which for 500 articles can add up to 1,500 indexed pages of duplicate content. Google Search Console reports this as “Duplicate, Google chose different canonical than user”.

The second scenario is online magazines with tag- and category-based list views. A magazine has 20 categories and 50 tags, and every article carries at least one category and two to three tags. The combinations produce dozens of possible URL paths per article. newscanonical consolidates all variants into a single canonical URL.

The third scenario is the press area of a listed company. Mandatory disclosures must remain available permanently and must not drop out of Google’s search results because of duplicate content. A correct canonical tag ensures that Google indexes the definitive version.

The technical architecture sets one link tag in the HTML head of each news detail page

newscanonical registers itself in the tx_news rendering pipeline and inserts a <link rel="canonical" href="..."> tag into the HTML head of the detail page. The canonical URL is calculated from the configured detail page PID and the news UID, regardless of which path the visitor took to reach the page.

Configuration happens in TypoScript: the detail page PID serves as the basis for the canonical URL. Optional parameters such as the URL structure (RealURL or TYPO3 site handling) and whether category segments are included in the canonical URL are controlled via constants.

The extension works as a hook in the tx_news rendering pipeline, not as a standalone plugin. It has no frontend output and no content element of its own. Its only visible effect is the canonical tag in the HTML source, which search engines read and visitors never see.

For it to work correctly, the detail page PID in the tx_news configuration and in the newscanonical configuration must match. If tx_news uses several detail pages (for example one per category), newscanonical has to be configured accordingly so that the canonical URL points to the right detail page.

Common problems are a wrong PID configuration, conflicts with the core canonical and redirect loops

Problem one: the wrong detail page PID. If the PID in the newscanonical configuration does not match the tx_news configuration, the canonical tag points to a page that cannot display the article at all. Google then ignores the canonical tag and picks a variant on its own. The fix: check PID consistency and compare the indexed canonical URLs in Google Search Console against the configured URLs.

Problem two: conflicts with the TYPO3 core canonical. Since TYPO3 v9.5, the core has generated its own canonical URLs through the SEO system extension (seo). If both are active, two competing canonical tags can appear in the HTML head. The fix: check whether the core canonical works correctly for news detail pages. If it does, newscanonical is redundant and can be deactivated. If the core canonical does not include the news parameters in the URL correctly, newscanonical remains necessary.

Problem three: redirect loops caused by faulty URL configuration. If the canonical URL points to a page that itself redirects to another URL, a loop results. This typically happens after a URL restructuring when old redirects were never cleaned up. The fix: review all redirects for news URLs and remove inconsistent entries.

From TYPO3 v12 on, Gosign checks whether the core canonical is enough

TYPO3 v12 changed how the core handles canonicals: the SEO system extension generates canonical URLs based on site handling and only takes over query parameters that routing resolves, for example through a route enhancer for tx_news. For many tx_news configurations with clean routing, the core canonical is therefore sufficient, so newscanonical is no longer needed. With every TYPO3 upgrade, Gosign checks whether the core solution generates the news canonical URLs correctly. If it does, we recommend deactivating newscanonical to remove a potential point of conflict. If the news URLs contain complex parameters or category paths that the core cannot resolve, the extension remains a valid solution. Either way, we recommend a systematic crawl with Screaming Frog or a comparable tool after the upgrade to check every news detail page for correct canonical behavior. A single misconfigured canonical tag can push dozens of pages out of the Google index, and for press pages or SEO-relevant blog articles that means an immediate loss of traffic.