Canonical Tag Issues

Canonical signals help search engines choose a representative URL for duplicate or very similar content. Screpy provides Missing Canonical, Canonical Mismatch, and Duplicate Canonical filters.

Understand the findings

• Missing Canonical: no supported canonical link was found on the page.
• Canonical Mismatch: the declared canonical differs from the crawled URL.
• Duplicate Canonical: multiple pages declare the same canonical target.

A mismatch or duplicate can be intentional when parameters, print views, or equivalent variants consolidate to one preferred URL. It becomes suspicious when unique pages point elsewhere, targets fail, redirect, are blocked, or contradict internal links and sitemaps.

<link rel="canonical" href="https://example.com/preferred-page" />

Google treats rel="canonical" as a strong signal, not a command, and recommends consistent internal links and sitemap URLs. Review Google's canonicalization guidance.

Analyze canonical issues

1. Decide which URL should be preferred and why.
2. Confirm the target returns 2xx, is crawlable, and is not marked noindex.
3. Compare source and target content and search intent.
4. Check whether the canonical is absolute, valid, and rendered in the document head.
5. Compare internal links, redirects, sitemaps, and hreflang with the declared target.
6. Group mismatches by parameter, protocol, hostname, locale, and template.

Do not canonicalize unrelated pages to a category or homepage merely to reduce duplication. If a page permanently moved, use a redirect. If two pages serve different intents, improve their differentiation instead of pointing one away.

Example decision

Tracking-parameter URLs contain identical content and correctly canonicalize to the clean product URL, but internal links still generate parameters. Keep the canonical and fix internal URL generation. If unique regional pages all canonicalize to the global page accidentally, repair the locale template and review hreflang.

Verify the fix

Inspect the rendered head, request the target, and run a new crawl. Confirm canonicals are valid, consistent, and point directly to successful preferred URLs. Use Search Console URL Inspection to compare the declared and Google-selected canonical after recrawling.

Treat canonicalization as a signal system

A canonical tag indicates the preferred URL among duplicate or very similar pages. It is not a command, and it works best when redirects, internal links, sitemaps, hreflang, and content all support the same choice.

A self-referencing canonical is common for indexable pages. A different canonical can be appropriate for variants, tracking parameters, or syndicated content. The question is whether the selected URL is accessible, indexable, equivalent, and consistently referenced.

Diagnose canonical filters

For Missing Canonical, determine whether the page is indexable and whether duplicates can exist. For Canonical Mismatch, compare the declared target with redirects, protocol, host, trailing slash, and locale. Duplicate Canonical observations may reveal many URLs consolidating to one page; that can be correct or overly broad.

Never canonicalize unrelated pages to a category or homepage merely to suppress them. If a URL should disappear permanently, redirects, noindex, or a proper error response may be more appropriate depending on its purpose.

Expected data movement

After fixing templates, Missing and Mismatch counts should fall. The number of crawled URLs may not change because canonical tags do not prevent crawling. Search indexing can take longer to consolidate, and Google may choose another canonical when signals conflict.

Use URL Inspection to compare user-declared and Google-selected canonicals for important examples. Google's canonicalization guidance describes the relative strength and interaction of supported signals.

Frequently asked questions

Should a noindex page also have a canonical?

It can, but conflicting signals make intent harder to interpret. Decide whether the URL should be indexed, consolidated, or removed, then align directives instead of combining them without a clear reason.

Can a canonical point to another domain?

Cross-domain canonicals are supported for duplicate or syndicated content. Confirm ownership agreements, content equivalence, accessibility, and consistent internal signals before using them.