Canonical mistakes that quietly kill rankings
A canonical tag is a page telling Google which URL is the preferred one. The common mistakes point it at a redirect, a noindexed page, a 404, or another host. What each one does and how to check the tag.
A canonical tag is a page telling Google which URL is the preferred one; the most common mistakes point it at a redirect, a noindexed page, a 404, or another host, and each one scatters the signals. When the tag names anything other than the final, indexable URL, the consolidation signal is misdirected and the page can lose its place.
What is a canonical tag?
A canonical tag is an HTML element in a page’s head that tells search engines which URL is the preferred version of that page. It sits in the head of the markup, under a link element:
<link rel="canonical" href="https://example.com/page">
The value is the URL the page wants to be known as. Links, content, and ranking history are meant to consolidate on that value.
What is the difference between self-referencing and cross-domain canonicals?
A self-referencing canonical names the page itself. It is the healthy default: the page is telling Google that this URL is the one to consolidate on.
A cross-domain canonical points at a URL on another site. It is used for syndicated content, where one site declares another’s version the canonical. It is rarely right for a regular page on your own site, and it sends the signals to a host you do not control.
Can a canonical point at a redirect?
A canonical that names a URL in a redirect chain gives the crawler another URL to reconcile and weakens the consolidation signal. The canonical checker flags a canonical that points at a URL that redirected in the request chain. That is a concrete fix: point the tag at the final 200 URL directly, not at a hop.
Can a canonical point at a noindexed page?
A canonical to a noindexed URL tells the engine the real page must not be indexed. If the target is noindexed, the source page can drop out of the index with it. Keep the canonical target indexable, or the tag consolidates the page into a URL that cannot rank.
Can a canonical point at a 404?
A canonical to a 404 points the consolidation signal at a dead URL. The page’s signals get nowhere, and the page can lose its place because it tells Google its preferred version does not exist. Point it at a live, 200, indexable URL.
What if the sitemap and the canonical disagree?
The canonical is the page’s own statement about the URL; the sitemap is a hint from the site. When the two disagree, the choice is left ambiguous, and the wrong URL can win the index. Make the canonical and the sitemap name the same final URL.
Can a canonical be in the body instead of the head?
No. A canonical placed outside the head is not a valid head link and is ignored. It must sit in the head of the page, not in the body.
Should the canonical be relative or absolute?
Relative canonical values are resolved against the page’s URL. If the same page is reachable on several hosts, a relative canonical resolves differently per host, which breaks consolidation. Use absolute URLs, with the scheme and host included.
How do I check my canonicals?
Run the URL through the canonical checker. It finds the canonical in the final HTML, resolves its target, compares it to the final URL after redirects, and flags a canonical that names a URL in the redirect chain. The indexability checker shows the canonical alongside the other directives in one request. You can also view-source and read the link tag yourself, but the checker resolves and checks the target for you.
A wrong canonical reroutes your signals for weeks before the chart shows it. stillindexed.com checks your pages’ canonicals and alerts you when something changes. Starter checks every 30 minutes, Agency every 15: https://app.stillindexed.com/auth/request
Questions
- What does a canonical tag do?
- A canonical tag tells search engines which URL is the preferred version of a page when several URLs serve similar content. It is a strong hint rather than a directive, so Google can and sometimes does choose a different canonical.
- Should a page canonical to itself?
- Usually yes. A self-referencing canonical removes ambiguity when a page is reachable through tracking parameters, trailing slash variants, or both http and https. Its absence is not an error, but its presence prevents a class of accidents.
- What happens if a canonical points at a redirect or a 404?
- The signal is wasted and Google falls back to choosing a canonical itself. A canonical target should be a URL that returns 200 and is itself indexable, otherwise you are pointing at a page that cannot be the preferred version.
- Can a canonical deindex a page?
- Indirectly, yes. If every page in a section canonicals to one URL, the others can be consolidated away and stop appearing in results. This is a common outcome of a templating mistake where the canonical is hardcoded.