A canonical URL is the preferred representative of duplicate or near-duplicate pages that a site signals to search engines for consolidation.
Meaning and scope
Canonicalization is the process of choosing one representative URL from a set of duplicate or very similar documents. A rel=canonical link can express the publisher's preference, but Google documents it as a strong hint rather than a command. Redirects, internal links and sitemap inclusion contribute separate signals, so they must not contradict the preferred URL.
Practical workflow
Inventory one URL family at a time: protocol and host variants, trailing-slash forms, tracking parameters, filters, print views and pagination. Decide whether each duplicate must remain reachable. If it should disappear for users, use a relevant permanent redirect; if it must remain available, point its canonical to the matching preferred document. A canonical target should return a successful response and remain indexable.
What to inspect
Check the rendered HTML and response headers on both the preferred URL and representative alternates. Then compare canonical tags, final URLs, internal links and sitemap entries in a crawl sample. Search Console's URL Inspection can show Google's selected canonical for an inspected URL, but a selected result is diagnostic evidence, not proof that every duplicate is resolved.
Limits and common mistakes
Do not canonicalize genuinely different products, pages with different primary intent, or every paginated page to page one by habit. Avoid chains, loops, a canonical to a redirect, or a noindex target. The durable result is one documented policy that is implemented consistently across templates.
Worked URL example and field checks
Consider a product reachable at https://example.test/widget, https://example.test/widget/, and https://example.test/widget?campaign=spring. If the clean, non-parameter URL is the preferred public page, each reachable duplicate should either redirect directly to that URL or, where it must remain reachable, expose exactly the same preferred canonical. The preferred URL should also point to itself. Internal menus, breadcrumbs, XML sitemap entries and any generated alternate references should use the clean URL, not merely rely on a tag to undo inconsistent linking.
<link rel="canonical" href="https://example.test/widget">The field check is explicit: capture the request URL, final URL after redirects, HTTP status, HTML canonical, robots meta or X-Robots-Tag, sitemap membership and at least one internal source link. A failure is not just a missing tag. It includes a canonical that changes between server HTML and the rendered DOM, a parameter URL listed in a sitemap while the clean version is canonical, or a canonical target that redirects. These are conflicting signals, so the repair is to choose one preferred document and align each field.
For pagination and faceted navigation, document the reason before applying a rule. Page two of a unique sequential list may contain material that should stay self-canonical, while a sort parameter that changes only order may have a different preferred URL. The same rule cannot be assumed for every parameter. Test a set of representative combinations rather than a single category URL, then repeat the sample after a template or platform release.
Google lists redirects and rel=canonical annotations as strong signals and sitemap inclusion as a weaker signal. That explains why a one-tag fix can be insufficient when other site systems disagree. It does not turn canonicalization into a guarantee: Google's selected canonical remains an outcome to inspect, especially when pages differ materially or other signals conflict.