Website basics
Understand canonical annotations and their limits
A canonical annotation suggests the representative URL for duplicate content. It does not redirect the browser or force the search engine's choice.
On this page
Identify actual duplicates
Compare content and purpose before grouping URLs. Two articles about a similar topic are not automatically duplicates.
Point to a working representative
An HTML example is:
<link rel="canonical" href="https://example.com/guide/">Replace the example with the page's complete production URL. Check self-references and avoid a copied template that points every article to one address.
Align other signals
Keep internal links, sitemaps, and redirects consistent. For translated content, organize canonicals within the relevant language rather than collapsing every language into one page.
Inspect the selected canonical
Search Console can distinguish the declared canonical from Google's selected one. If they differ, investigate duplication, availability, and conflicting signals rather than assuming the annotation is mandatory.
Select the image to enlarge.
- Identify URLs with substantially the same content, not merely similar topics.
- Nominate the public representative with canonical. This does not redirect the browser.
- Check that internal links and the sitemap point to the same representative URL.
Choose the representative from the content relationship
Compare what the two addresses actually display before adding a canonical. A tracking parameter may leave the article unchanged, while a filter or language choice may change meaningful content. Similar-looking addresses alone do not establish equivalence.
Choose a representative that matches the material you intend to publish. Avoid treating a topic neighbor or the homepage as the automatic representative of every article. In a template, verify the generated value on several distinct pages.
Example: an article with a tracking parameter
Suppose an article is reached through a clean link and another carrying a campaign-related parameter. If the content is effectively the same and the clean URL is the intended public address, consider identifying it as the representative.
First verify that the parameter does not change the actual content. After adding the annotation, do not treat an unchanged browser address as a failure: canonical annotation is not navigation.
If the requirement also includes moving users to a consistent URL, design and test that behavior separately. Search annotation and the visitor's route answer different questions.
Distinguish declarations from observations
| Item | What it represents |
|---|---|
| Page canonical | The operator's declared representative |
| Internal links | Addresses offered to readers |
| Sitemap | Published addresses listed for discovery |
| Google-selected canonical | The search engine's observed selection |
If these disagree, identify the intended representative and review the relationship rather than changing one value in isolation.
For a translated page with its own content, do not simply collapse it into the Japanese version as though language were irrelevant. Organize the canonical choice for each language and the relationship between language editions separately.
After editing, verify the production declaration directly. Track the later search-side selection as another observation. This keeps the review specific about what the configuration expresses and what an external system has actually chosen.