Canonical points to forwarding: Cause and Fix

Deposit the final address in the canonical

A canonical to an old HTTP address can only land in the main HTTPS version after several redirects. The actual goal thus remains unnecessarily indirect. Determine the final, content-matched address including the desired hostname and path spelling.

Example: Recognizing the Result

Illustrative example: The canonical points to /ratgeber-alt/, this address redirects to /ratgeber/. The desired final URL is already known.

Limit cause and implement correction

Change the source of the canonical in the template or CMS field and check the delivered response again. The destination address should directly provide the intended content. At the same time, check internal links and sitemap so that the same old intermediate address is not used. A redirection to a foreign content page must not simply be taken as a correct destination.

What makes you recognize a suitable correction

Spend the final matching goal directly in the canonical. Orient sitemap and internal links to the same address and verify their response.

Classification and boundaries

When is this indication not a clear error?

A forwarding does not automatically make the content unusable. The result initially shows an unnecessary or possibly contradictory intermediate signal.

Further documentation

Google: canonical URLs

Canonical Points to Redirection to CMS and Cause

Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are only linked where Canonical shows on forwarding a clearly own cause or fixed route in the respective system.

Canonical Points to Forwarding in WordPressCheck theme, SEO plugin, page builder, cache plugin and media library. Canonical shows up on redirection in TYPO3Target TypoScript, Site Config, Fluid Templates, Extensions, Language Tree and Caches. Canonical shows up on redirection in ShopwareExamine experience worlds, category templates, product data, variants, sales channels and SEO URLs. Canonical Points to Redirect in ShopifyTarget theme, collections, products, apps, metafields, markets and robots rules. Canonical Points to Redirect in WooCommerceCheck WooCommerce templates, WordPress theme, SEO plugin, product data and cache specifically. Canonical shows up on redirection in MagentoCheck catalog rules, layered navigation, product variants, store views, extensions and cache/indexer.

Frequent causes of this error

Template rulesA template generates the same technical error for many URLs, such as incorrect canonicals, missing H1 or empty meta data. Plugin conflictsMultiple plugins, apps or extensions write the same SEO signals and generate conflicting outputs. URL parameters and filtersFilters, sorts, tracking parameters or variants create indexable duplicates and crawl budget problems. Relaunch and migration residuesAfter relaunch, domain change or CMS migration, old URLs, canonicals, redirects and internal links remain in the system.

Related SEO Errors

Noindex in SitemapIf URLs are in the sitemap, but are excluded from the index via noindex Canonical is missingWhen a Missing Canonical Is Problematic—and When Not Canonical on NoindexIf the preferred URL itself must not be indexed Canonical on 404When signals are bundled to a non-existent page

Appropriate Seitenreport checks

This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.

Canonical CheckerConsider canonical goals, duplicates and consolidation.Open the check -> Indexability CheckerShare status code, noindex and canonical.Open the check -> Duplicate Content CheckerCompare duplicate or very similar content.Open the check ->

Canonical Points to Redirection: Cause and Fix