Compare each page's main content

A product can be reachable through a category path and a tracking URL while showing the same main information. Google describes this as a normal reason for duplicate URLs. It compares the main content, so a shared navigation bar or footer alone does not establish that otherwise different pages are duplicates. Read Google's canonicalization explanation.

Start with the actual pages and their purpose. Do the variants help a visitor do different things, or is one simply another address for the same page? A query shared by two useful articles is a separate editorial question; it is not proof that their content is identical.

Google chooses a representative URL

Google groups pages whose main content is very similar and chooses a canonical. Redirects, canonical annotations and sitemap inclusion can influence that choice. Your preference remains a hint, so inspect Google's selected canonical rather than assuming the declaration was followed. The primary guidance describes this selection.

Normal duplication is not itself a spam-policy violation. Publishing unoriginal pages primarily to manipulate search rankings is a different question. Google's spam policies define abusive practices; a canonical tag is not a substitute for reviewing the content's purpose.

Choose the response that fits the variant

Different duplicate-URL situations need different decisions
SituationUseful decisionLimit to keep in view
A redundant URL no longer needs to work independentlyUse a permanent redirect to the retained page.The destination should represent the moved content.
A useful variant must remain accessibleConsider a canonical annotation to an equivalent preferred page.Google can choose a different canonical.
A URL should be excluded from SearchReview noindex for that exclusion purpose.Exclusion is different from canonical consolidation.
The main content is translatedReview language and regional relationships.A translated body is not automatically duplicate content.

Google advises against using robots.txt for canonicalization or using noindex to force a preferred canonical within a site. Keep canonical destinations, internal links and sitemaps consistent. Its consolidation guidance explains these limits.

Illustrative review: a product tracking URL

Suppose a campaign adds tracking parameters to a product link while the product description, price and purchase task remain the same. Compare that response with the ordinary product URL. Record whether the tracking URL needs to remain accessible and whether its canonical declaration identifies the equivalent preferred page.

If a different parameter selects a different product, compare the resulting content before treating it the same way. The parameter name alone cannot decide whether a redirect would discard something the visitor needs.

Investigate before changing URL behavior

  1. List the actual variants and open their final responses.
  2. Compare the main content and the visitor task.
  3. Choose which page should remain the representative.
  4. Review existing redirects, canonical declarations and internal links together.
  5. Apply the selected change and retest the same URLs.
  6. Inspect available Search Console evidence after Google processes the change.

Keep the original content and URL mapping recoverable. A site-wide rule based only on a percentage of repeated words can remove useful product, language or support pages. Record the reason for each redirect so an unrelated parameter variant is not swept into the same rule.

Questions readers ask

Should internal links point to the preferred URL?

Yes. Google recommends linking consistently to the canonical URL rather than a duplicate variant. Review navigation, contextual links and sitemap entries together so they do not describe conflicting preferences.

Does a canonical annotation redirect a visitor?

No. A canonical annotation identifies a preferred representative for search engines; a redirect sends the visitor to another URL. Choose according to whether the original address still needs to serve its own response.

canonical URLs, permanent redirects, noindex, localized alternatives, the duplicate-content implementation guide.

Primary references

Guidance checked on October 12, 2026. Examples are illustrative. This revision does not claim customer results or human expert approval.