Google canonical URL signals

Google canonical signals,
as documented

The canonical signals Google documents, how strong it says each one is, and what to avoid, in Google's own words. Verified from Google's pages on 2026-10-07.

Google describes canonicalization as the process of selecting the representative (canonical) URL of a piece of content, which helps it show only one version of otherwise duplicate content in its search results. This page lists the methods Google documents for indicating your preference, with the wording taken from Google's pages.

The signals and rules Google documents

Topic	What Google says	Source
Redirects	“A strong signal that the target of the redirect should become canonical.”Google: use permanent redirects "only when deprecating a duplicate page", and for the quickest effect use HTTP (server-side) redirects.	Google docs Verified 2026-10-07
rel="canonical" link annotations	“A strong signal that the specified URL should become canonical.”Google lists redirects first, then rel="canonical", in order of how strongly they can influence canonicalization.	Google docs Verified 2026-10-07
Sitemap inclusion	“A weak signal that helps the URLs that are included in a sitemap become canonical.”Google: all pages listed in a sitemap are suggested as canonicals, and Google decides which pages (if any) are duplicates based on similarity of content.	Google docs Verified 2026-10-07
Stacking signals	“these methods can stack and thus become more effective when combined.”Google: using two or more methods increases the chance of your preferred canonical URL appearing in search results.	Google docs Verified 2026-10-07
Hint, not a rule	“indicating a canonical preference is a hint, not a rule.”Google: it may choose a different page as canonical than you do, for various reasons.	Google docs Verified 2026-10-07
Not required	“none of them are required; your site will likely do just fine without specifying a canonical preference.”Google: if you do not specify one, it identifies which version of the URL is objectively the best version to show to users in Search.	Google docs Verified 2026-10-07
rel="canonical" link element	“The rel="canonical" link element is only accepted if it appears in the <head> section of the HTML.”Google: it only works for HTML pages, not for files such as PDF, and it can map an infinite number of duplicate pages.	Google docs Verified 2026-10-07
rel="canonical" HTTP header	“you can use a link HTTP response header with a rel="canonical" target attribute.”Google: this works for non-HTML documents such as PDF files, does not increase page size, and is supported for web search results only.	Google docs Verified 2026-10-07
Link element or header	“We recommend that you choose one of these and go with that.”Google: using both at the same time is supported but more error prone, for example one URL in the HTTP header and another in the link element.	Google docs Verified 2026-10-07
Absolute URLs	“Use absolute paths rather than relative paths with the rel="canonical" link element.”Google: relative paths are supported but can cause problems in the long run, for example if you unintentionally allow your testing site to be crawled. It also says to use absolute URLs in the HTTP header.	Google docs Verified 2026-10-07
Self-referential canonical	“Do include a rel="canonical" link on the canonical page itself (also known as a self-referential canonical).”	Google docs Verified 2026-10-07
Alternate-version attributes	“rel="canonical" annotations that suggest alternate versions of a page are ignored.”Google: specifically, rel="canonical" annotations with hreflang, lang, media and type attributes are not used for canonicalization. Use the appropriate link annotations for alternates, for example link rel="alternate" hreflang for language and country.	Google docs Verified 2026-10-07
Consistency across methods	“Don't specify different URLs as canonical for the same page using different canonicalization techniques.”Google's example: one URL in a sitemap but a different URL for the same page in rel="canonical".	Google docs Verified 2026-10-07
URL fragments	“Don't specify a URL fragment as canonical, as Google generally doesn't support URL fragments.”	Google docs Verified 2026-10-07
Internal links	“When linking within your site, link to the canonical URL rather than a duplicate URL.”	Google docs Verified 2026-10-07
JavaScript	“The best way to do this is to specify the canonical URL in the HTML source code and make sure that JavaScript doesn't change the canonical link element.”Google: if you cannot set it in the HTML source, leave it out and only set it with JavaScript.	Google docs Verified 2026-10-07
HTTPS over HTTP	“Google prefers HTTPS pages over equivalent HTTP pages as canonical, except when there are issues or conflicting signals.”Google's examples include an invalid SSL certificate, insecure dependencies other than images, an HTTPS page that redirects through HTTP, or an HTTPS page with a rel="canonical" to the HTTP page.	Google docs Verified 2026-10-07
hreflang clusters	“for canonicalization purposes Google prefers URLs that are part of hreflang clusters.”Google: specify a canonical page in the same language, or the best possible substitute language if none exists.	Google docs Verified 2026-10-07

Read on 2026-10-07. Google's pages showed "Last updated 2026-07-10 UTC" (consolidate duplicate URLs) and "Last updated 2026-08-20 UTC" (canonicalization). Notes under a quote are close paraphrases of the same page. Other search engines may treat canonical signals differently; this page covers only what Google documents.

Canonical vs noindex vs robots.txt

Google's best-practice list says which tools not to use for picking a canonical.

Tool	What Google says	Source
robots.txt	“Don't use the robots.txt file for canonicalization purposes.”Google: it may still index URLs that are disallowed in robots.txt without their content.	Google docs Verified 2026-10-07
noindex	“We don't recommend using noindex to prevent selection of a canonical page within a single site, because it will completely block the page from Search.”Google: rel="canonical" link annotations are the preferred solution.	Google docs Verified 2026-10-07
URL removal tool	“Don't use the URL removal tool for canonicalization.”Google: it hides all versions of a URL from Search.	Google docs Verified 2026-10-07

Cross-domain canonicals

The Google pages read for this reference do not include a setup guide for canonicals that point to another domain. They do mention the cases below.

Case	What Google says	Source
Syndication partners	“The canonical link element is not recommended for those who want to avoid duplication by syndication partners, because the pages are often very different.”Google: the most effective solution is for partners to block indexing of your content.	Google docs Verified 2026-10-07
Hacked sites	“Some attacks on websites introduce code that returns an HTTP 3xx redirect or inserts a cross-domain rel="canonical" link annotation into the HTML <head> or HTTP header.”Google: it may then choose the malicious or spammy URL instead of the URL on the compromised website.	Google docs Verified 2026-10-07
Copycat sites	“In rare situations, our algorithm may select a URL from an external site that is hosting your content without your permission.”Google: you can contact the site's host to request removal, and can file a request under the Digital Millennium Copyright Act.	Google docs Verified 2026-10-07

Examples

Google's own example of the link element in the head of a page.

<html>
  <head>
    <title>Explore the world of dresses</title>
    <link rel="canonical" href="https://example.com/dresses/green-dresses" />
  </head>
</html>

Google's own example of the HTTP header, sent for a non-HTML file (it uses a .docx whose canonical is the PDF).

HTTP/1.1 200 OK
Content-Length: 19
Link: <https://www.example.com/downloads/white-paper.pdf>; rel="canonical"

Check a page's canonical tag with the free canonical tag checker, and review the rest of a page's head with the meta tag checker. For related rules, see Google's robots meta tag directives and Google's sitemap rules.

Rules to remember

Google says redirects and rel="canonical" are strong signals and sitemap inclusion is a weak one, and that they can stack.
Google says a canonical preference is a hint, not a rule.
Google says not to use robots.txt for canonicalization, and does not recommend noindex for choosing a canonical within a single site.

URL structure basics: Google URL structure guidelines.

Redirect types in detail: Google redirects guide.

Questions

Which canonical signal is strongest?

Google lists, in order of how strongly they can influence canonicalization: redirects (a strong signal), rel="canonical" link annotations (a strong signal) and sitemap inclusion (a weak signal). It adds that these methods can stack.

Is rel="canonical" a command?

No. Google says indicating a canonical preference is a hint, not a rule, and it may choose a different page as canonical than you do.

Can I put rel="canonical" on a PDF?

Not as an HTML element, which only works for HTML pages. Google says you can send a rel="canonical" HTTP header for non-HTML files such as PDF, and it supports that for web search results only.

Should I use noindex or robots.txt to handle duplicates?

Google says no to both for canonicalization. It does not recommend noindex within a single site because it completely blocks the page from Search, and it says not to use robots.txt because disallowed URLs may still be indexed without their content.

Do I need a canonical tag on every page?

Google says none of the methods are required, but it does include a self-referential rel="canonical" on the canonical page itself in its do list, and recommends it in its example.

What does Google say about cross-domain canonicals?

The pages read for this reference give no setup guide for them. They say rel="canonical" is not recommended for avoiding duplication by syndication partners (block indexing instead), and that hacks can insert a cross-domain rel="canonical" pointing to spammy content. Check Google's pages directly for anything beyond that.

How current is this page?

Every quote was read from Google's pages on 2026-10-07. The pages showed "Last updated" dates of 2026-07-10 UTC (consolidate duplicate URLs), 2026-08-20 UTC (canonicalization) and 2026-08-21 UTC (troubleshooting). Google can change its documentation, so treat the linked pages as the final word.

Sources

How to specify a canonical URL with rel="canonical" and other methods (Google Search Central), read on 2026-10-07
What is URL canonicalization (Google Search Central), read on 2026-10-07
Fix canonicalization issues (Google Search Central), read on 2026-10-07

Let Balzac write the articles.

Type your website. Balzac finds the searches you can win, writes articles built to rank on Google and get cited by ChatGPT, and publishes them for you.

3 free articles · No card needed