Canonical URL: Choose the Preferred Page Version — Guide
Understand canonical URLs, choose a preferred page version, and avoid pointing canonical tags to redirects or unrelated pages. Read the steps and example.
A canonical URL identifies the preferred version among pages with duplicate or very similar content. It is a hint to search engines, not an access restriction or guaranteed command. Common duplicates come from tracking parameters, alternate paths, or HTTP and HTTPS versions. Choose the URL you want indexed, make it stable, and reference it consistently in internal links and sitemaps. A canonical tag should point to a relevant page that loads successfully.
Choose the preferred page version
Decide whether the canonical version uses HTTPS, a www host, trailing slashes, and a particular path format. Use the same choice across navigation, redirects, sitemap entries, and canonical tags. If two URLs contain substantially different information, do not canonicalize one to the other merely to consolidate traffic. A canonical page should represent the content of the duplicates, not a generic homepage.
Add a self-referencing canonical when useful
A link element in the document head can name the preferred absolute URL: link rel="canonical" href="https://example.com/page". A self-reference can make the preferred version explicit. Ensure there is one clear canonical value and that rendered HTML exposes it to crawlers. Avoid conflicting HTML and HTTP header canonicals. Parameterized pages may need special handling if filters create genuinely useful unique content.
Check redirects and indexing signals
Open the canonical destination and confirm it returns a successful page rather than redirecting or showing an error. Canonicalization is one signal among redirects, internal links, sitemap URLs, and content similarity. Search engines may select a different canonical if signals conflict. Use Search Console URL inspection to compare the declared canonical with the selected canonical after recrawling. Fix inconsistent internal links instead of relying on tags to resolve every duplicate.
Worked example
<link rel="canonical" href="https://example.com/products/blue-mug">
Tracking variant: https://example.com/products/blue-mug?utm_source=emailDoes a canonical tag redirect duplicate pages?
No. A canonical tag is an indexing hint; a redirect sends visitors and crawlers to another URL.
Reference and further reading
KEEP EXPLORING
Another useful idea.
Generate a Zod Schema from JSON Without Overfitting Samples
Infer nested Zod objects, arrays, unions, optional keys and null values, then refine the schema for your application.
robots.txt vs noindex: Crawling and Search Visibility
Choose between crawler access rules, noindex instructions and authentication without accidentally hiding the directive from the crawler.
Robots.txt Mistakes: Root Placement, Paths and Staging Rules
Review crawler policy mistakes involving file location, path case, staging block rules, sitemap directives and rendering assets.