Duplicate, Google chose different canonical than user
Read the conclusion first
When Google selects another canonical, compare the actual pages and their signals before editing the tag. Canonical annotations express a preference for duplicate or very similar content. Align the intended destination's health, redirects, annotations, internal links and sitemap; keep genuinely distinct language pages distinct.
Applicable conditions
Applies to duplicate pages, protocol or parameter versions, and incorrectly merged language pages.
Before you open the report
The declared and Google-selected canonicals, redirects, sitemap entries and internal-link targets.
Use one concrete URL or report first. Keep account credentials and private visitor data out of shared notes.
Steps and verification
Create a side-by-side record of the competing URLs
Save the inspected URL, declared canonical, Google-selected canonical and last crawl. Open all relevant destinations without login. Compare final response, language, main content and task. Check whether the Google-selected page is a valid equivalent, an old host or a mistakenly shared template target.
Use the crawl date to distinguish a previous deployment from today's state. If the selected destination is outside your accessible property, record that limitation rather than inventing its inspection result. Similar titles alone do not establish duplicate content.
Remove conflicting signals at their source
Choose the preferred accessible, indexable destination for each equivalent group. Check rendered HTML and any canonical HTTP header, permanent redirects, internal links and sitemap inclusion. A tag pointing to one URL while navigation and sitemap promote another leaves conflicting evidence.
Repair template logic or URL normalization so the correction persists across representative pages. The intended canonical should not return an error, redirect unexpectedly or carry noindex. Do not use a removal request or robots block as a replacement for a proper canonical relationship.
Preserve translations and verify later selection
A genuine translation serves a different language need. Keep a suitable canonical in that language and separately verify alternate-language relationships. Pointing every translation to English to ‘combine authority’ can undermine the intended language pages.
Retest the delivered signals after release and retain the mapping and affected URL examples. Later inspect whether Google processed the update and selected the expected destination. A consistent implementation is a checked repair; Google's subsequent choice and search display are separate observations, not guaranteed by the tag.
Common mistake: canonical points to a non-indexable target
Conflicting signals make the desired outcome more uncertain; first ensure the target is healthy.
How to decide when you encounter different situations
Match your actual observation to a row before changing the page. If it does not match, collect the missing evidence first.
| What you see | Next step | How to confirm |
|---|---|---|
| The selected page is indeed equivalent | Determine whether it was reasonable to begin with | No need to change all duplicate versions |
| Canonical target is noindex or 404 | Fix canonical target health and signals | Target returns 200 and allows indexing |
| Different languages were merged | Check body content and association design | Do not point all to one language |
Four signals point to two different preferred URLs
Teaching scenario. Names, URLs and numbers illustrate the method; they are not customer or measured site results.
- What you observe
- Example: HTML prefers /guide/, the sitemap lists /guide-old/, and navigation links to the old URL. Google selects the old equivalent page.
- What it establishes
- A canonical is a signal rather than a command. Conflicting discovery and redirect signals complicate the intended choice.
- What to do next
- Confirm the pages are actually equivalent, then align the intended URL’s canonical, sitemap and internal links. Use a suitable permanent redirect if retiring the old page; do not canonicalize independent translations to one language.
What counts as a checked result
Check the preferred target returns useful indexable content. Reinspect the indexed canonical later; the live page cannot establish Google’s final selection.
If a required check fails, keep the error and return to the matching decision branch. A blank record means unverified, not passed.
Leave with a checked result, not another vague instruction
- Your deliverable
- A competing-URL comparison and a consistent intended canonical signal set.
- Stop and resolve this first
- Do not canonicalize different language tasks to one language merely to consolidate numbers.
Record missing evidence in the worksheet below. An unresolved test is useful information; a blank field is not a pass.
Checklist for this page
Fill in your own check results, then decide the next step. Blank means not yet verified, not normal. Content is saved only in the current local session and is not submitted to the server or AI.
Frequently asked questions
Will adding canonical eliminate all duplicates?
Not necessarily. Other signals need to be consistent; Google ultimately decides canonicalization.
Can I canonicalize a broken URL to a 404 target?
Choose a healthy intended target. Repair its response and content before relying on it as the canonical version.
Official materials and usage boundaries
This page provides operational judgment and checking methods, and does not show customer success cases. Calculation examples and request samples are teaching materials, not actual website metrics. Google's reports, conditions, and interfaces may change; please refer to the current official documentation.
Read the corresponding Google official documentationContinue with the relevant tool
Paste the delivered HTML into AISEO Site's HTML checker to read its declared canonical. The declaration must still be compared with Google's chosen URL.
See how it works →