Why it matters
Google extracts rel=canonical from the head and uses it in deduplication and canonical selection, but the tag is very often wrong, so Google treats it as a strong hint rather than an order. With more than one canonical on a page, Google will likely ignore all of them.
How to meet it
Give every indexable page a self-referencing canonical, and point duplicates (tracking parameters, print views, sort orders) at the preferred URL. Use absolute URLs on the chosen origin. Output the tag from one layer only, making sure the CMS, an SEO plug-in and the front-end framework do not each add one, and put it in the server-sent head, not only in JavaScript-rendered HTML, with no invalid element (such as an img or iframe) before it, because Google stops reading the head at the first invalid element. For PDFs use an HTTP Link header.
How to test it
A crawl finds no indexable page with zero or several canonicals, or with a relative or placeholder value; raw and rendered HTML carry the same canonical; URL Inspection shows the user-declared and Google-selected canonical as equal on key templates.
How Regensbot covers it
Decided from one URL.
An audit reads the response, the headers, the HTML, robots.txt, the sitemaps and the structured data, and the finding shows the evidence it saw.
Sources
Google documents03
- 01How to specify a canonical URL with rel="canonical" and other methodsGoogle Search Central (opens in a new tab)
- 025 common mistakes with rel=canonicalSearch Central blog (8 April 2013) (opens in a new tab)
- 03Use valid HTML to specify page metadataGoogle Search Central (opens in a new tab)
Claims in the knowledge base08
- D2-C032ConfirmedHow is HTML interpretedShown on screen
- D2-C031ConfirmedHow is HTML interpretedShown on screen
- D2-C418SourceLightning session E: Managing Duplicates and Site MovesGoogle's documentation
- D2-C417ConsistentLightning session E: Managing Duplicates and Site MovesSaid on stage
- D2-C379ConsistentHandling web duplicationSaid on stage
- D2-C035n/aHow is HTML interpretedThe author's interpretation
- D2-C831SourceHow is HTML interpretedGoogle's documentation
- D2-C873ConfirmedLightning session E: Managing Duplicates and Site MovesSaid on stage
Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)
- Confirmed
- Google's documentation states the same thing.
- Consistent
- Google's documentation supports it without stating it.
- Source
- The claim is the cited document itself.
- n/a
- Nothing to verify: a quotation, framing, opinion or analysis.