Google's public patent filings describe mechanisms for selecting canonical URLs that go well beyond what the documentation explains. Here is what those filings reveal.
Google's public documentation is written for webmasters. It's accurate, but it's also simplified. Patent filings are written for patent examiners. They describe the actual mechanisms, the edge cases, and the signal weighting logic in considerably more technical detail.
Reading patent filings isn't a way to "beat" Google. It's a way to understand what the system is actually doing, which makes it easier to work with rather than against it. The canonical selection process described in various Google patents is more nuanced than "Google reads the canonical tag and follows it."
Google's systems evaluate multiple signals when determining which URL to treat as canonical for a cluster of duplicate or near-duplicate pages. The canonical tag is one of those signals. It is not automatically the strongest one.
Signals that influence canonical selection include: the URL structure itself (shorter, cleaner URLs are often preferred), the distribution of inbound links across URL variants, which URL appears in the sitemap, which URL is referenced by internal links, the consistency of canonical tags across the cluster, and whether the page returns a 200 status code reliably.
When these signals agree, canonical selection is straightforward. When they conflict, Google's systems have to weigh them against each other. The outcome is not always predictable, and it can change over time as the site accumulates new links or as Google recrawls pages.
Google's documentation explicitly describes the canonical tag as a "hint" rather than a directive. This language is precise and intentional. A hint is information that informs a decision without controlling it. A directive would be binding. The canonical tag is not binding.
The practical implication is that you cannot rely on the canonical tag alone to resolve canonicalization problems. It needs to be reinforced by consistent signals from other sources. A canonical tag pointing to the www version of a URL, combined with internal links that consistently link to the www version, combined with a sitemap that only lists the www version, is a much stronger signal than the canonical tag in isolation.
There are documented conditions under which Google will ignore a stated canonical and select a different URL as canonical. Understanding these conditions is useful for diagnosing why your canonical tags aren't being followed.
If your canonical tag points to a URL that itself redirects to another URL, Google may select the final destination of the redirect chain as canonical rather than the URL you specified. This is a common error in sites that have undergone URL restructuring.
A canonical tag pointing to a URL that returns a 404, 410, or any other non-200 status code will be ignored. Google cannot treat a non-existent page as canonical. This situation often occurs after site migrations where old canonical tags aren't updated.
If the majority of inbound links point to a different URL variant than the one specified in the canonical tag, Google may select the more-linked URL as canonical. Link signals carry significant weight in the canonical selection process.
Cross-domain canonicals require explicit verification in Google Search Console to be treated as authoritative. Without that verification, a canonical tag pointing to a different domain may be ignored or treated with reduced weight.
Google has filed patents specifically addressing the problem of near-duplicate content generated by parametric URLs. These patents describe mechanisms for identifying URL clusters that serve substantively similar content and selecting a representative URL from the cluster.
The mechanism described involves analyzing URL structure, parameter patterns, and content similarity. URLs that differ only in parameter order or parameter value combinations, but serve similar content, may be clustered together and have a single canonical selected for the cluster.
The issue for e-commerce sites is that this selection process doesn't always choose the URL you'd want. If your base category page has fewer signals than a specific filter combination page that has accumulated links, the filter page might be selected as canonical for the cluster. That's the opposite of what you want.
Hreflang tags and canonical tags interact in ways that trip up multilingual sites regularly. The correct relationship is: each localized version of a page should have a self-referencing canonical, and hreflang tags should reference those canonical URLs. If a page's canonical tag and its hreflang tags reference different URLs, the signals conflict.
Google's patent filings on multilingual content selection describe a process that evaluates both sets of signals together. A canonical tag that contradicts the hreflang configuration creates ambiguity that the system has to resolve, and the resolution isn't always what you'd expect.
Patent filings describe mechanisms, not weights. Knowing that link signals influence canonical selection doesn't tell you exactly how much weight they carry relative to the canonical tag itself. That weighting is not disclosed and likely varies by context.
Patent filings also describe systems as they existed when the patent was filed, which may or may not reflect the current implementation. Google's systems evolve continuously. Patents are useful for understanding the general approach and the types of signals considered, not for predicting exact outcomes in specific situations.
The honest position is that canonical selection is a probabilistic process influenced by multiple signals. You can improve the probability of Google selecting the URL you prefer by making all your signals consistent. You cannot guarantee a specific outcome. That uncertainty is real and worth acknowledging rather than papering over.