Topic 03 / 18 primary articles
Canonicals and Duplicate URLs
Understand duplicate clusters, declared preferences, Google-selected representatives, and the signals that make canonical strategy coherent.
Start here / In order
Build the diagnosis
one step at a time.
These approved entry points establish the topic before the complete inventory below.
- 01
Duplicate: Google Chose a Different Canonical Than User
This status means Google grouped the inspected URL with duplicate or highly similar pages and selected another representative URL. Compare Google’s selected canonical with your preferred URL, then align redirects, canonical tags, sitemap inclusion, internal links, and content distinctness. Accept Google’s choice when it is the better representative.
- 02
Alternate Page With Proper Canonical Tag: Is This an Error?
“Alternate page with proper canonical tag” usually means Google found a duplicate or near-duplicate URL, recognized the canonical page you indicated, and indexed or evaluated the canonical instead. Confirm that Google selected the intended canonical and that the alternate URL is supposed to remain secondary. If both are true, there is normally nothing to fix.
- 03
Duplicate Without User-Selected Canonical: What Google Chose
“Duplicate without user-selected canonical” means Google found duplicate or highly similar URLs, did not find a clear canonical preference from your site, and selected a representative on its own. Inspect Google’s selected canonical, decide whether it is acceptable, and add consistent canonical signals only when you need to clarify the preferred URL.
Complete primary inventory
Every article
in this topic.
Understand duplicate clusters, declared preferences, Google-selected representatives, and the signals that make canonical strategy coherent.
Technical baseline
Alternate Page With Proper Canonical Tag: Is This an Error?
Learn why Search Console excludes an alternate page when its canonical tag works, how to confirm the selected canonical, and when no repair is needed.
Technical baseline
Canonical tags: what they solve, what they merely suggest
A canonical is a consolidation signal, not a cleanup crew. Use it for duplicates, not as a substitute for URL discipline.
Technical baseline
Canonical vs. Redirect vs. Noindex: Which URL Control Should You Use?
Choose among canonicals, redirects, noindex, robots.txt, authentication, 404, and 410 by defining the user, crawler, and search outcome you actually need.
Technical baseline
Duplicate Without User-Selected Canonical: What Google Chose
Understand why Google selected a canonical when your page declared none, how to inspect the duplicate cluster, and when to add or align canonical signals.
Technical baseline
Duplicate: Google Chose a Different Canonical Than User
Understand why Google selected another canonical URL and align redirects, canonical tags, sitemaps, internal links, and page distinctness.
Technical baseline
URL Parameters and SEO: Classify Query Strings Before You Control Them
Classify tracking, session, filtering, sorting, pagination, presentation, and identity parameters before selecting crawl, index, canonical, or redirect rules.
Technical baseline
Trailing Slash SEO: Control /page and /page/ as Separate URLs
Choose a consistent slash or nonslash path policy, redirect duplicate variants and align internal links, canonicals, sitemaps, routing and cache behavior.
Technical baseline
WWW vs. Non-WWW for SEO: Choose One Host and Enforce It
Choose a preferred public hostname, serve both variants securely, redirect the alternate host and align internal links, canonicals, sitemaps and structured data.
Technical baseline
Multilingual Canonical Tags: Keep Each Locale Eligible
How canonical tags and hreflang should work together across translated pages and same-language regional variants without consolidating useful locales away.
Claim checks
Do Canonical Tags Work Like 301 Redirects?
Canonical tags and 301 redirects are both strong canonicalization signals, but they are not interchangeable. Learn which one fits duplicate, moved, and retired URLs.
Technical baseline
Canonicalization QA Checklist for Duplicate URL Sets
Validate duplicate URL sets across canonicals, redirects, sitemaps, internal links, hreflang, structured data, rendering, and Search Console evidence.
Technical baseline
Userinfo in URLs: The Text Before @ Is Not the Host
Learn why username:password@host URLs are unsafe for canonicals, how userinfo can mislead readers, and how to normalize links, redirects, logs, and sitemaps.
Technical baseline
Unicode Normalization in URL Paths: NFC and NFD Canonicalization Checklist
Audit NFC and NFD Unicode URL paths across slugs, filesystems, databases, caches, redirects, canonicals, sitemaps, and percent encoding.
Technical baseline
Trailing-Dot Hostnames and Canonical URLs: example.com. Is a Different URL String
Understand example.com. versus example.com across DNS, URLs, TLS, cookies, origins, redirects, canonicals, caches, analytics, and security.
Technical baseline
Google Canonical Re-Evaluation Can Take Two Weeks: The July 2026 Troubleshooting Guide
Google now says duplicate clusters can persist up to two weeks after canonicalization fixes. Learn what to change, what to inspect, and when to wait.
Technical baseline
Syndicated Content and rel=canonical: Why Google Says Canonical Is Not the Main Fix
Google now explicitly says rel=canonical is not the recommended way to prevent syndicated copies from competing in Search. Here is what that means in practice.
Technical baseline
PDF SEO: How Canonical HTTP Headers Consolidate Non-HTML Documents
A technical guide to using HTTP Link headers for PDF canonicalization, including CDN delivery, duplicate formats, validation, and limits.
Technical baseline
Pagination SEO: Why Page 2 Should Usually Canonicalize to Itself
Google treats paginated URLs as separate pages and recommends self-referencing canonicals rather than pointing page 2, page 3, and later pages back to page 1. Here is the implementation logic.
Related reading
Useful supporting records.
Existing glossary references
Terms used
inside this topic.
These definitions are derived from glossary links already approved in the topic's article inventory.