Operational article · published
Choose a Canonical URL Representative
Select the version that should own a duplicate or near-duplicate content set and align every controllable signal. Includes a worked example and a release checklist.
Reviewed 2026-11-18 · Google guidance, fictional exampleThe task and the failure mode
Built for: Teams consolidating URLs, changing domains or platforms, normalizing route variants, and protecting established search and lead paths. This guide is for the person who must select the version that should own a duplicate or near-duplicate content set and align every controllable signal and leave a decision trail that implementation, editorial, analytics, or operations can review.
Choose the stable URL that gives the complete answer and works for the visitor. Group only duplicate or very similar pages. Permanently redirect a duplicate you are retiring; use rel="canonical" when an equivalent version must remain available. Keep a genuinely different service or product page separate. A canonical expresses your preference to Google; it does not guarantee which URL Google will select.
Decision brief
Compare the actual pages before choosing a representative. Check the service or product, audience, coverage, main content, and next action. A campaign parameter that changes only attribution can belong to the same group. A page with a different service, eligibility, or useful offer needs a separate decision.
Prefer a stable, working destination that you can maintain and link to consistently. Confirm that it returns the intended content with HTTP 200, can be crawled, and is eligible for indexing. A shorter address alone is not a reason to replace a page that serves the visitor better.
Choose how each duplicate should behave. A retired address can redirect permanently to its equivalent. An equivalent campaign URL may need to remain usable for attribution; it can serve the same page while declaring the preferred URL. Align internal links and sitemap entries with the chosen representative.
Follow a canonical and redirect loop across three equivalent URL variants →
Questions to answer before changing the system
- 01Do the proposed duplicates answer the same question and offer the same next action, or does one contain useful content the other lacks?
- 02Which URL should remain stable for visitors, internal links, and future editing?
- 03Must a duplicate remain available, or can it redirect permanently without losing a necessary user function?
- 04Do redirects, canonical annotations, internal links, and sitemap entries agree on that destination?
- 05Is an unexpected Google-selected canonical recorded in indexed URL Inspection data, or is the concern only an assumption based on a tag?
Workflow
- 01List the exact URLs in one proposed duplicate group. Open their final responses and compare the main content and action. Separate a distinct service, product, language, or useful filtered result before changing its canonical.
- 02Choose the preferred destination and write down why it serves this group. Check its final status, rendered answer, crawl access, indexing directives, and existing canonical. Repair a broken destination before pointing other URLs to it.
- 03For each duplicate, choose either permanent retirement or continued availability. Redirect a retired equivalent directly to the preferred URL with a permanent server-side redirect. Keep a necessary campaign variant available only where that serves the actual user or measurement requirement.
- 04Put one consistent absolute rel="canonical" URL in the valid HTML head of each retained equivalent page. Use a self-referential canonical on the preferred page. Check any HTTP-header canonical too; two mechanisms must not nominate different destinations.
- 05Update controllable internal links to the preferred URL and include that representative in the sitemap. Do not use robots.txt blocking or noindex as a substitute for canonicalizing an ordinary duplicate within the site.
- 06Reopen a retired alias, a retained campaign URL, the preferred page, and a genuinely different page. Check the full redirect path, initial HTML, post-render canonical, content, and next action. Make sure the different page still describes itself.
- 07After Google recrawls and processes the pages, compare indexed URL Inspection records for the user-declared and Google-selected canonical. The live test reports access to the fetched page and follows redirects without showing the destination. Verify redirect hops directly; use indexed records to see Google’s selection. Keep unresolved differences open and inspect their cause.
Evidence to retain
- A small URL map records the preferred URL, each alias or parameter variant, and the reason each is equivalent or separate.
- For a proposed duplicate, retain enough of both main answers and actions to explain the equivalence decision. A similar title alone is insufficient.
- Record the requested URL, redirect hops, final status, final URL, and canonical from the initial HTML. Compare the canonical after client rendering when the site changes its head in JavaScript.
- Check the preferred URL for the intended answer, indexing directives, self-canonical, and a working action. An HTTP 200 response containing an error message is not a useful representative.
- Identify the exact internal links and sitemap entries that should change. Keep a separate useful service page in the review as an unaffected example.
- Date any indexed URL Inspection observation and keep the declared and Google-selected canonical separate. A release check describes what the site serves, not what Google has already processed.
- Repeat the same URL sample after release and record any unresolved conflicting signals with their owner. A present canonical tag alone does not close a contradictory redirect or header.
Worked example: an old service path and an email campaign URL
- Preferred page
- A fictional service site uses https://example.com/services/drain-cleaning for its current drain-cleaning answer and booking action. It returns 200, is eligible for indexing, and declares itself canonical.
- Retired duplicate
- The old https://example.com/drain-cleaning address describes the same service and is no longer needed as a separate page. It permanently redirects directly to /services/drain-cleaning. Old internal links are updated to the destination.
- Retained campaign variant
- The email URL /services/drain-cleaning?utm_source=email serves the same content and must remain usable for the stated attribution setup. Its canonical points to the clean service URL. Internal links and the sitemap use the clean URL.
- Separate page
- /services/emergency-plumbing has different hours, service coverage, and a different request action. It stays separate and self-canonicalizes. Sharing a plumbing topic does not make it a drain-cleaning duplicate.
- Acceptance
- A reviewer tests the old path, campaign URL, clean service URL, and emergency page. The first redirects, the next two agree on the clean canonical, and the emergency page keeps its own canonical and action. Google selection remains a later indexed-data check.
Canonical decision record release checklist
- Every grouped URL has the same or very similar primary content and a compatible visitor action.
- A useful page with a distinct service, product, audience, or answer has its own decision.
- The preferred URL is stable, returns the intended HTTP 200 content, and is eligible for indexing.
- Retired aliases redirect to the equivalent destination without an unnecessary chain.
- Retained duplicates declare the same preferred absolute URL; the preferred page self-canonicalizes.
- HTML and HTTP-header canonical signals do not disagree.
- Internal links and sitemap entries use the approved representative.
- Robots blocking and noindex have not been used as a shortcut to consolidate ordinary duplicate pages.
- Initial and rendered content, canonical, and visitor action pass on the chosen examples.
- Postrelease Google selection is checked separately in indexed URL Inspection data when available.
What to measure—and what it does not prove
- Count the retired aliases that reach their approved equivalent through the intended permanent redirect. Keep unexpected destinations, loops, and failures visible.
- Count the retained duplicate examples that declare the approved representative and the preferred pages that self-canonicalize. Report the exact sample rather than implying a whole-site result.
- Check that the distinct-page example still has its own content, canonical, links, and action. Consolidating more URLs is not the success criterion.
- Record Google-selected canonical observations separately after processing. Technical agreement does not establish indexing, rankings, traffic, or a causal business result.
Boundaries and caveats
Google can select a different canonical even when the site declares a consistent preference.
A canonical is appropriate for duplicate or very similar content. It does not make a different service page equivalent to a broad category or homepage.
Do not block a retained duplicate in robots.txt to make its canonical work; Google must be able to fetch the page to read the annotation.
The drain-cleaning example is fictional. Its URL decisions depend on the stated content and tracking requirements, not a rule that every parameter or old path should receive the same treatment.
Primary sources
- Google Search Central: Canonicalization and duplicate URLsdevelopers.google.com
- Google Search Central: Redirects and Google Searchdevelopers.google.com
- Google Search Central: Site moves with URL changesdevelopers.google.com
- Google Search Central: Changing your hosting locationdevelopers.google.com
- Google Search Central: Build and submit a sitemapdevelopers.google.com
- Google Search Central: Troubleshoot canonicalization issuesdevelopers.google.com
- Google Search Console Help: Inspect a URLsupport.google.com
Start with one bounded case
Map one actual duplicate group and a useful page that must stay separate. Choose the representative and each variant’s redirect-or-retain behavior, then use the linked parameter guide and canonical-drift checks to verify that the decision survives the release.