adzup✦GOOD THINGS START WITH CURIOSITY.
STRATEGY × CREATIVE × TECHNOLOGYSay hello on WhatsApp ↗

Why did Google choose a different URL? A canonical review for business websites.

A practical brief for investigating duplicate URL signals before changing pages, redirects or your sitemap.

Read as text ↗
Make yourself comfortable
0% read
In this article
THE STARTING POINT

A practical brief for investigating duplicate URL signals before changing pages, redirects or your sitemap.

01 / THE FIELD NOTES

Start with the page you want a customer to reach.

A business can publish one service through several addresses: an old campaign URL, a new navigation route, a preview hostname and a version containing tracking parameters. That creates a management question before it creates an SEO task. Which address should remain the durable destination for that service, and what should happen to the others? Decide this with the person responsible for the website, rather than asking a developer to make every page point at the homepage.

This article is an editorial review of existing Google documentation on 19 November 2026, not an announcement of a new indexing rule. Google's canonical guidance describes ways to express a preferred representative URL. Those signals help communicate intent; adding a tag does not turn that preference into a guaranteed selection.

02 / THE FIELD NOTES

Ask for indexed evidence and a separate live check.

Google's URL Inspection documentation makes an important distinction: the indexed report can show the Google-selected canonical, while a live test cannot predict that selection. Ask for the exact inspected address, the reported selected URL and the date of the evidence. A screenshot saying a live page is available is answering a different question from which version Google has selected.

Build a small comparison sheet for the affected addresses. Include the current response, destination after any redirect, visible page purpose and declared canonical. Add whether each address appears in the sitemap and in prominent internal links. This sheet is an operational review format, not a prescribed Google report. Its purpose is to make conflicting instructions visible before a change is approved.

03 / THE FIELD NOTES

Resolve the business difference before consolidating.

Illustrative example: a textile supplier has a general fabric-manufacturing page and a separate technical page about fire-resistant materials. They share a company introduction but answer different purchasing questions. Treating them as interchangeable because their layouts look similar could hide the more useful specialist explanation. First identify whether the pages genuinely duplicate each other or deserve distinct content and navigation.

By contrast, an obsolete campaign address that repeats the current service page may no longer need to remain available independently. Google documents permanent redirects for deprecating duplicate pages, and canonical annotations for representative versions. Choose the behaviour that matches the intended customer journey. Preserve necessary campaign measurement deliberately, and test existing adverts before removing an address that paid visitors still use.

04 / THE FIELD NOTES

Give the implementation one coherent instruction.

Ask the delivery team to align the preferred destination across the canonical declaration, sitemap and ordinary navigation. Google notes that sitemap inclusion is a weaker canonical signal than explicit canonical mapping. A newly submitted sitemap therefore does not resolve contradictory page instructions by itself. When the site is generated by multiple systems, include the rendered page and response headers in the review so a second declaration is not overlooked.

Keep this acceptance task narrow. Record the chosen URL, the duplicate addresses being handled, the reason for the decision and the expected behaviour of each. If an unexpected external domain appears as canonical, escalate that finding for investigation rather than automatically copying the domain into the website configuration. Google's troubleshooting documentation discusses implementation problems and compromised sites among possible causes; the symptom alone does not establish which cause applies.

05 / THE FIELD NOTES

Close the task with evidence, then observe.

After release, test the actual public addresses again. Keep the deployment check separate from a later Search Console review: the first confirms what the website serves now, while the second reports what Google subsequently records. Requesting another crawl is a request, not a deadline or an indexing guarantee. Avoid repeatedly changing the preferred URL while waiting for updated evidence.

Your next measurement step is a dated review of the affected URL pair, followed by checks that customers and campaigns still reach the intended service. If the selected URL now matches the business decision, record that outcome. If it does not, return to the comparison sheet and investigate the remaining difference instead of buying another generic indexing package.

  • Name one durable destination for each genuinely duplicated page group.
  • Retain evidence of indexed selection and current live behaviour separately.
  • Assign an owner and review date for the affected addresses.
FROM READING TO A REAL PROJECT

What would this
look like for you?

Review the pages, technical foundations and business information behind your search visibility. Explore our ai search & seo service, or tell us what you are working on so we can discuss the scope.

Explore AI search & SEO ↗

Put the thinking into practice.

Sources & further reading

Platform references support the factual background. The planning recommendations are AdzUp’s editorial interpretation.

A useful read.
A clearer next move?

Keep exploring, or bring your questions to AdzUp.

← Back to the reading room

From “interesting”
to “let’s do this.”

Bring your questions. We’ll start with your business, your audience and the next move you want to make.

Put the thinking to work ↗