Google Chose a Different Canonical: A Duplicate URL Check Worksheet
Tuohai editorial guide · Reviewed and published October 5, 2026. The worksheets are blank working templates, not client results.
Your HTML declares a self-referencing canonical, but Search Console reports a different URL selected by Google. Before copying another tag across the site, compare three addresses: the inspected page, the declared canonical and Google's selected canonical.
A canonical declaration expresses a preference for duplicate or highly similar content. Google's canonical documentation treats it as a strong signal, not an instruction that must prevail. Content and other technical signals also matter.
Google chose a different canonical: record all three URLs
Use indexed-version information to record the user-declared canonical and Google-selected canonical, alongside the inspected URL and check date. Hostnames, trailing slashes and parameters deserve separate attention even when the addresses look similar.
Visit all three addresses and record responses, final destinations and main content. If the declared target redirects again, document that too. A working inspected page does not establish that both targets work.
The URL Inspection documentation says a live test cannot predict Google's canonical selection. “Current HTML corrected” and “Google selected the new version” need separate records.
If Google's selection is unavailable, leave it unknown. A site: result or another URL appearing first does not fill that field. Without authorized Search Console access, inspect public signals without claiming to know Google's decision.
Compare the main content before changing tags
Should these pages share one representative version? A tracking-parameter copy or simultaneously accessible old and new paths may contain the same article. Establish the intended long-term version before aligning signals.
If both pages should appear independently, compare the answers buyers receive. In a hypothetical example, two packaging selection pages target different conditions but change only the application title. Their tables, limits and sample procedures remain identical. Different titles do not establish different content tasks.
Distinct purposes need genuine material, such as different scope, structural explanations or confirmation conditions. Do not invent test results to fill a gap, or merge model pages without the product owner's approval. This example is not a client case.
Google's Page indexing report advises ensuring substantive differences when you believe the inspected page is not a duplicate of Google's selected version. That is not a fixed extra-word requirement.
Record language too. Do not casually point an independently useful English page to the Chinese homepage to concentrate supposed authority. Canonical guidance recommends a same-language canonical where one exists. Language and regional presentation need separate consideration.
Align redirects, canonical tags, internal links and sitemaps
Compare four signals together: redirect destination, canonical declaration, internal-link target and sitemap version. Redirects and canonical declarations are strong signals; sitemap inclusion is weaker. Do not assume one conflicting signal must win.
For HTML, inspect the canonical link in <head> and record its absolute URL. Multiple conflicting targets require checking template or plugin output, not appending another tag. If HTTP Link headers declare a canonical, inspect those as well.
Where scripts affect rendering, compare initial HTML with the rendered declaration. Google recommends setting the canonical in source where possible and avoiding JavaScript changes to it. Record discrepancies for a developer; JavaScript use alone does not prove canonicalization failed.
Check the target itself. A redirect, inaccessible page or unintended noindex may conflict with the retention decision. Confirm useful content and indexing intention before aligning the referring page's signals.
Complete a canonical-conflict worksheet
Use one record per URL group. Keep authorized client indexing data and screenshots out of public articles.
| Check | Current evidence | Intended arrangement and owner |
|---|---|---|
| Inspected URL, language and date | ____ | ____ |
| User-declared canonical | ____ | ____ |
| Google-selected canonical and record date | ____ | ____ |
| Responses and final destinations of all three | ____ | ____ |
| Shared content and substantive differences | ____ | ____ |
| HTML and HTTP canonical declarations | ____ | ____ |
| Initial versus rendered declaration | ____ | ____ |
| Internal-link and sitemap versions | ____ | ____ |
| Retain/merge/add material/unverified | ____ | ____ |
| Correction and later indexing recheck | ____ | ____ |
For genuine copies, approve the retained version and align signals. For distinct tasks, fix incorrect declarations and support differences with real material. If Google's selection remains unknown, deliver the verified conflict without saying canonical selection is corrected.
Do not use robots.txt to force the preference by blocking another version. Google also advises against using noindex to force canonical selection within a site. These controls serve different purposes.
Frequently asked questions
Why can Google choose another URL despite a self-canonical?
The tag expresses preference, not the outcome. Compare content and the redirect, linking and sitemap signals rather than treating tag presence as acceptance.
Is blocking the duplicate simpler?
robots.txt is not a canonicalization tool. Blocking crawling does not establish removal from the index and may prevent reading the declaration. Decide the URL's purpose first.
Does seeing the target in a site: result prove the fix worked?
It is a search-result clue, not a replacement for Google's recorded canonical selection. Confirm public signals first and later record any changed selection separately.
Conclusion: align purpose and technical signals
When Google chooses a different canonical, establish whether the three URLs represent one task or distinct tasks. Fix the evidenced conflict, then separate current output acceptance from Google's later selection.
You can request Tuohai's free human SEO audit, in Chinese. The full human audit is free; scope, materials and scheduling are agreed separately. There is no guaranteed response time, canonical selection or ranking outcome.
Sources
Read on October 5, 2026. These official links open Chinese-language documentation. The worksheet does not guarantee acceptance of your preferred URL.