Canonical tags explained: choosing the preferred URL

Understand what a canonical reference does

A rel="canonical" link identifies a preferred URL for duplicate or very similar content. Google treats canonical annotations as a signal, not an instruction it must follow. The tag does not redirect a visitor, and Google may select another URL.

A canonical also is not an access restriction or a way to hide private content. Decide whether the requirement is consolidation, a permanent move or access control before choosing a mechanism.

<link rel="canonical" href="https://example.com/guides/caching">

Reference: Google Search Central: Consolidate duplicate URLs

Choose a destination that represents the same content

Compare the proposed destination with the page being audited. A tracking variation of an article and the clean article URL may represent the same content. A category listing and a single product generally serve different purposes; a shared template does not make them duplicates.

Look for template mistakes such as every page pointing to the homepage, a staging hostname remaining in production or a canonical inherited from another article. Open the destination deliberately and verify the actual content before applying a site-wide change.

Keep the surrounding signals consistent

Use the preferred URL consistently in internal links and sitemap entries. Avoid declaring one canonical in HTML while presenting conflicting preferences elsewhere. Google recommends absolute canonical URLs and consistent signals across your site.

SiteAudit extracts the first matching canonical from the fetched HTML and resolves its reference. It does not visit that target or prove that there is only one declaration. Inspect source templates if you suspect duplicate tags, and use Search Console to see Google’s selected canonical.

Reference: Google Search Central: Canonical best practices

Verify a canonical change

Test both a normal page and a variant that was causing duplication. A homepage-only check will not catch a canonical hardcoded into a content template.

1. Read the exact canonical value and compare it with the intended public URL.
2. Check that the destination responds with the equivalent content and is suitable for indexing.
3. Review the source for conflicting declarations and update internal links or sitemap entries as needed.
4. Audit representative pages again and follow up on Google’s interpretation in Search Console.