Investigate Google choosing the wrong service page as canonical

Confirm the unexpected destination

Use the indexed URL Inspection details rather than a live test to identify Google's selected canonical when that information is available. Write down the affected URL, intended destination, selected destination, and observation date. Open both pages. The surprising choice may reveal a real overlap rather than a broken tag.

Source checks: Google Search Central: Fix canonicalization issues · Google Search Central: Canonical URL methods · Google Search Console: URL Inspection

Compare the customer's job on both pages

For a service website, compare what the visitor needs, how the work is scoped, and what happens next. A furnace-repair page and a heating-service overview can coexist if one explains a specific repair decision and the other helps choose among services. If both offer the same short description and form, merely changing headings may not establish separate purposes.

Inspect the signals you control

Ask the editor to check the canonical in delivered HTML and any relevant header, redirect destination, sitemap URL, and internal navigation spelling. Look for a template that copied another page's canonical or links that consistently lead to the unwanted version. Check whether the selected destination itself is available and indexable before trying to make it the replacement.

Choose differentiation or consolidation

Match the repair to the page relationship.

• Fix a wrong generated canonical when the pages genuinely serve different needs.
• Use meaningful service-specific explanations and evidence to distinguish separate pages.
• Redirect a retired duplicate to the appropriate surviving service page.
• Align links and sitemap entries with the chosen preferred destination.
• Keep the repair bounded to the affected cluster before changing the whole site.

Avoid restrictive experiments without a plan

Noindex removes a URL from indexing consideration; it is not the preferred tool for persuading Google to choose another canonical within a duplicate group. Pointing every page to the homepage can suppress useful service destinations. Do not label a competitor's appearance or one manual search as canonical evidence. Work from the actual cluster and delivered signals.

Record reevaluation without promising selection

After publishing, confirm the intended signals on the live pages. Revisit indexed evidence later and record whether the selected canonical changed. If the choice remains different, reassess the visitor-facing distinction before making another technical edit. Compare search performance at the canonical destination so you do not interpret a duplicate URL's missing data as all traffic disappearing.

Illustrative repair and overview conflict

An illustrative heating website declares /furnace-repair as its own canonical, but Google selects /heating-services. Both pages originally describe the same generic callout. The owner adds repair-specific symptoms, inspection scope, and repair-versus-replacement boundaries to the repair page, while the overview becomes a service chooser with direct links. This gives the pages distinct jobs without inventing a ranking promise.

The page comparison records the repair-specific symptoms and inspection boundaries that were absent from the original version. The owner checks that the overview now links directly to the repair page and does not repeat the same generic description as its entire body. Both pages are then tested on a phone so the distinction is useful to customers as well as visible in page output.

Questions about this task