Why do I have canonical tag issues? on Custom CMS

Canonical tags tell search engines which URL is the preferred version of a page.

• Canonical points to a different section or wrong URL Self-referencing canonical on
• Crawl the site and check canonical values per URL Ensure the canonical
• Set canonical on every page to the single preferred URL (usually itself

Canonical tags tell search engines which URL is the preferred version of a page. When they're wrong (pointing to a different page), missing on duplicates, or conflicting with other signals (e.g. redirects, hreflang), indexing and rankings can suffer. Fixing canonicals ensures Google knows which URL to index and consolidates signals on the right page. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then…

Canonical points to a different section or wrong URL. Self-referencing canonical on one URL but another URL canonicals to it (confusion). Missing canonical on parameter or duplicate URLs. Mix of trailing slash and non–trailing slash without consistent canonical. Hreflang and canonical conflict (e.g. multiple languages). Template errors so canonical is dynamic but wrong.

Common examples

A real-world example: after a site update, a business saw visibility drop for "Canonical issues". They checked Search Console, found the blocking issue, fixed it, and regained impressions over the following crawl cycles.

How to diagnose

Crawl the site and check canonical values per URL. Ensure the canonical URL is the one you want indexed. Use Search Console to see which URL is indexed when several are similar. Check for chains (A canonicals to B, B to C). Validate hreflang and canonical together if you have multi-language or multi-region.

Recommended fixes

Set canonical on every page to the single preferred URL (usually itself for the main version). For duplicates (e.g. parameters), set canonical to the main URL. Fix template logic so canonicals are correct. Resolve conflicts with redirects and hreflang. Re-crawl and use URL Inspection to confirm Google has the right canonical. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task.