How to Check a Canonical Tag: Find Conflicts and Fix Them
A canonical tag tells search engines which URL should represent a page when several URLs contain the same or very similar content. It is useful for duplicate signals, but it is not a redirect and it cannot force Google to choose a URL that is unavailable or materially different.
Check the source first: Run the free canonical tag checker on the page you are investigating, then compare its result with the public URL and redirect behavior.
1. Look for the canonical link element
Fetch the page and find a link element whose relationship is canonical. Record its absolute URL, including the protocol, host, path and meaningful query parameters. A missing element is different from a canonical that points somewhere unexpected.
2. Check the common conflict patterns
- Missing canonical: the page gives no preferred URL signal.
- Self-referencing canonical: the canonical matches the final public URL and is often a clear default.
- Conflicting canonical: the HTML points to one URL while redirects, sitemap entries or internal links favor another.
- Cross-page canonical: several pages point to one URL even though each page has a distinct purpose.
3. Compare related signals
Check the final HTTP status, redirects, robots directive, sitemap entry and internal links. The canonical should use the final HTTPS URL, should not point to a blocked or error page and should match the content relationship you intend. A canonical does not repair a broken redirect chain or an accidental noindex.
4. Fix the source that generates the tag
Correct the CMS field, route template or framework helper that writes the canonical. Keep one canonical element per page. Use redirects when an old URL should permanently move, and use noindex only when the page should remain accessible but out of search results.
5. Verify the deployed page
Run the canonical tag checker again after deployment. Record the old value, the new value and the final status code. Use Google Search Console URL Inspection later to see whether Google has crawled the change and which canonical it selected; that result can take time to update.
Limitations
A checker can report what the public HTML says at the time of the request. It cannot promise which canonical Google will select or predict rankings. Treat the result as evidence for the next investigation, not as a guarantee.
If the page has several technical issues, run a free SeeSpect audit to review canonicals together with indexability, links, titles and security signals.