
A website can expose the same content at several addresses. Search engines then need to decide which version best represents it. A canonical annotation helps express the preferred version, but the choice needs to reflect the actual relationship between the pages.
Reconstructed archive: April 2013. Written in November 2026 using contemporary historical sources. The archive date organizes this series; this text is not a recovered original.
The April 2013 discussion
Google published examples of common canonical mistakes on April 8, 2013. The guidance included inappropriate destinations and conflicting declarations. It showed how a small technical setting could describe the wrong relationship even while the page appeared normal to a visitor.
Identify genuine duplicates first
Two addresses that display the same service description may be duplicates. A service page and a detailed project example are usually different resources with different purposes. Do not point every page at the homepage simply because it is the best-known address. Begin with a content inventory and explain what each page contributes.
Check the destination as a customer would
The preferred address should lead to relevant, working content. After a redesign, verify that it does not point to an old address that fails or to a page describing a different service. A change saved in an SEO extension is not enough; inspect the result delivered on the live page.
Avoid conflicting configuration sources
A template, CMS feature, and extension can each generate canonical information. Ask the developer to identify the source being used and whether the declarations agree. Keeping a single clear configuration is easier to maintain than troubleshooting several overlapping rules after traffic changes.
Distinguish canonical choices from moving a page
A preferred-version hint and a redirect serve different purposes. If a page has permanently moved, customers following the old link still need a useful destination. Plan the URL mapping and the customer experience together rather than treating all duplicate or obsolete addresses as the same kind of problem.
Keep the decision documented
Record the preferred address and why it was chosen for important content. Include these checks in launch reviews and after substantial routing changes. The details of search processing can evolve, so consult current guidance for implementation. The durable lesson is to make a deliberate, accurate choice instead of accepting a default that nobody has checked.
June 2019: a retired tool setting did not replace site configuration
This note preserves the reconstructed June 2019 archive, written in November 2026. Google announced the retirement of Search Console’s preferred domain setting on June 18, 2019, pointing to site signals such as canonical declarations, sitemaps and redirects instead.
Historical source retained: June 18, 2019 preferred-domain announcement
Record the intended protocol, hostname and public route for important content. Align menus, relevant internal links and sitemap entries with that choice while preserving useful incoming routes. Test representative deep pages as well as the homepage before applying broad routing rules. A remembered setting in a retired tool is not evidence that the current website expresses a consistent preference.
Explore website design and support, SEO services, or contact Guardian Solutions to discuss your next step.
Historical source: Google announcement dated 2013-04-08.
