---
title: Why your canonical tag might not be read at all
description: Attribute order, conflicting signals and self-reference. The canonical mistakes that quietly de-index pages.
url: https://moxseo.com/blogs/why-your-canonical-tag-might-not-be-read-at-all
date_modified: 2026-10-28
author: Ashish Khan
language: en_US
---

A canonical tag is one line of HTML that tells search engines which URL is the real one. It is also one of the easiest things to get subtly wrong in a way that produces no error, no warning, and no obvious symptom — just a page that never quite ranks.

## What is a canonical tag and what does it do?

A canonical tag is a `<link rel="canonical">` element in a page’s head that names the preferred URL for that content. When several URLs show the same or near-identical content, it tells Google which one to index and consolidate signals onto. It does not stop a page being crawled, and it works best when your other signals agree.

You can declare it in the HTML head or in an HTTP `Link` header. Google recommends choosing one method rather than both, because using both is more error prone, and it only accepts the `<link>` element inside the `<head>`. Details are in Google’s guidance on [consolidating duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) (checked October 2026).

## The tag is read as a hint, not an instruction

This is the first thing worth internalising. A canonical is a strong suggestion, not a directive. Google weighs it against other signals — [internal links](/tools/internal-link-finder/), [sitemap](/tools/xml-sitemap-validator/) entries, redirects, content similarity — and can disagree with you.

When those signals conflict, the canonical tends to lose. A page that canonicalises to itself while every internal link points elsewhere is sending two contradictory messages, and the links usually win.

Google’s own wording is that `rel="canonical"` is a strong signal, in the same class as a redirect, while sitemap inclusion is a weak one. In practice that means the tag is worth setting, but it will not rescue a site whose links and sitemap point at a different URL.

## Attribute order breaks naive checkers

Both of these are valid HTML and identical in meaning:

- `<link rel="canonical" href="https://example.com/page">`
- `<link href="https://example.com/page" rel="canonical">`

Search engines parse both correctly. Plenty of audit tools do not — they pattern-match on `rel` appearing before `href` and report the second form as having no canonical at all.

We know because we shipped that bug ourselves and caught it in testing before release. It is worth knowing that a tool telling you a canonical is missing may be telling you about its own parser rather than your page.

The specific failure: our checker required `rel` to appear before `href` in the tag. Against a test page using the reverse order — entirely valid HTML — it reported “No canonical tag” on a page that had one. Anyone acting on that would have added a second canonical and created a genuine problem where none existed.

## The failure modes that actually cost you

Ordered roughly by how often we find them and how much damage each does.

- **Canonical pointing at the homepage from every page.** A template mistake that tells Google the entire site is one URL.
- **Canonical pointing at a redirected URL.** The target then redirects somewhere else, so the signal dissolves.
- **Canonical pointing at a noindexed page.** You are consolidating authority onto a page you have told Google to drop.
- **Two canonical tags on one page.** Usually a theme and a plugin both emitting one. Google may ignore both, so keep only one.
- **Relative canonical with a broken base.** Resolves to a URL that does not exist.

Several more problems are listed in Google’s documentation: a canonical that conflicts with the one in your sitemap, a fragment (`#`) used as the canonical URL, a `<link>` placed outside the head, and a canonical injected or changed by client-side JavaScript when it could be in the HTML source. On WordPress, the duplicate-tag case is the most common one, and our [WordPress SEO](/services/seo/wordpress/) work usually begins by checking which theme or plugin is emitting each tag.

## What a correct canonical looks like

On an ordinary indexable page: one tag, absolute URL, pointing at itself, matching the URL in your sitemap and the one your internal links use. Same protocol, same subdomain, same trailing-slash convention.

Consistency across those signals matters more than the tag itself. Our [on-page audit tool](https://moxseo.com/tools/on-page-audit/) reports whether the canonical is self-referencing and shows the destination when it is not, so a mismatch is visible immediately.

## Canonical, redirect, noindex or robots.txt: which one should you use?

Use a redirect when the old URL should disappear, a canonical when several URLs must stay reachable but one should be indexed, and noindex when a page should not appear in search at all. Avoid robots.txt for choosing a canonical, because blocked URLs can still be indexed without their content and Google never sees the tag.

| Situation | Best tool | Why |
| --- | --- | --- |
| Old URL retired, content moved | 301 redirect | Users and crawlers both land on the new URL |
| Same page reachable with tracking parameters | Self-referencing canonical on the clean URL | Variants stay usable, signals consolidate |
| Syndicated copy on another site | Cross-domain canonical to the original | Names the source of the content |
| Page must not appear in search | noindex | Removes it from the index; do not use it to pick a canonical within one site |
| Hundreds of useless filter URLs | robots.txt for crawl control, plus canonical or noindex on what stays crawlable | See our post on faceted navigation and crawl budget |

## How Google chooses when signals disagree

![How Google chooses a canonical URL when signals disagree using internal links, sitemaps, redirects, HTTPS, URL structure, and content similarity](https://moxseo.com/wp-content/uploads/2026/07/how-google-chooses-canonical-url-when-signals-disagree-e1785309335214-1024x561.webp)Image Source: AI-generated visual by MoxSEO

Your canonical is one input among several. When they conflict, Google picks what it judges most likely to be correct, and the declared canonical does not automatically win.

- **Internal links** — which URL your own site links to most consistently
- **Sitemap entries** — which version you submitted
- **Redirects** — a redirect is a strong signal that the target should be canonical
- **HTTPS and URL structure** — secure and cleaner URLs are preferred
- **Content similarity** — whether the pages really are duplicates

Search Console reports the URL Google actually selected under the Page Indexing report. When that differs from your declared canonical, the gap almost always names the conflicting signal.

## Parameters, pagination and the cases with no clean answer

Most canonical guidance covers the simple case. The awkward ones are where real sites live.

- **Tracking parameters.** A self-referencing canonical on the clean URL handles these well and is the main reason to have one at all.
- **Paginated series.** Each page should canonicalise to itself, not to page one. Canonicalising page three to page one tells Google the products on page three do not exist.
- **Faceted URLs.** Canonicalise to the unfiltered category, except for facets you deliberately want indexed.
- **Syndicated content.** A cross-domain canonical pointing at the original is the correct tool, and one of the few cases where pointing off-site is right.

Two more cases catch international and e-commerce sites. Language variants should be linked with `hreflang` annotations, not canonicalised to one language, and Google ignores canonical annotations that carry `hreflang`, `lang`, `media` or `type` attributes. Our [hreflang validator](/tools/hreflang-validator/) and [international SEO](/services/seo/international/) service cover that setup. On online stores, product variants and filtered listings need the same care; see our [e-commerce SEO](/services/seo/e-commerce/) page.

## A five-minute check you can run today

Take your five most commercially important pages. For each one, confirm four things agree.

- The canonical points at the page itself, using an absolute URL
- That URL matches what your sitemap lists
- That URL matches what your internal links use, including trailing slash and protocol
- The page returns 200 rather than redirecting

If all four agree, the canonical is doing its job. If any disagree, that mismatch is a stronger signal than the tag, and it is what Google will act on.

Our [on-page audit](https://moxseo.com/tools/on-page-audit/) checks the first and fourth directly and shows the canonical destination when it is not self-referencing, which usually makes the mismatch obvious.

### A hypothetical example of a mismatch

Imagine a service page whose canonical says `https://example.com/seo-audit/`, while the sitemap lists `https://example.com/seo-audit` and the navigation links to `http://www.example.com/seo-audit/`. Three spellings of one page. The canonical is not wrong, but it is outvoted. The fix is to pick one form, redirect the others to it, and make the sitemap, internal links and canonical all use it. Then check the Page Indexing report to confirm the selected URL changes.

## Sources and further reading

- [How to specify a canonical URL with rel=”canonical”](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
- [The link element, HTML Living Standard](https://html.spec.whatwg.org/multipage/semantics.html#the-link-element)

## Make Every Canonical Signal Point to the Right URL

A canonical tag may look correct while conflicting internal links, redirects, sitemap entries, duplicate tags, parameter URLs, or noindexed targets quietly weaken it. Contact MoxSEO for a canonical and indexability audit that checks how your declared URLs align with the signals search engines actually use. We will identify incorrect canonical destinations, redirected targets, duplicate implementations, pagination mistakes, faceted-navigation conflicts, and URL inconsistencies that may be preventing important pages from ranking as intended.

[Schedule a consultation with MoxSEO](https://moxseo.com/schedule-consultation/) to review your highest-value pages and create a clear canonicalisation plan for your website. Our team will help you align canonicals, internal links, redirects, sitemaps, protocols, subdomains, and trailing-slash rules so every signal consistently supports the URL you want search engines to index.

## Frequently asked questions

### Should every page have a canonical tag?

Every indexable page should carry a self-referencing one. It costs nothing and removes ambiguity when URLs pick up tracking parameters.

### Can a canonical point to a different domain?

Yes, cross-domain canonicals are supported and are the correct tool for syndicated content. They are also easy to misconfigure, so use them deliberately.

### Does a canonical stop a page being crawled?

No. The page is still crawled. The canonical only affects which URL is indexed and consolidated.

### What if Google ignores my canonical?

Check what else is pointing elsewhere. Search Console reports the URL Google actually selected, and the gap between that and your declared canonical usually names the conflicting signal.

### Should I use a relative or absolute URL in a canonical tag?

Use an absolute URL. Google supports relative paths but warns they can cause problems later, for example if a test or staging copy of your site gets crawled and its canonicals point at the wrong host.

### Can I put the canonical in an HTTP header instead of the HTML?

Yes. Google accepts the canonical as an HTTP Link header as well as an HTML tag. Pick either the header or the HTML tag rather than both, so they cannot disagree.

### Is noindex a good way to choose a canonical?

No. Google advises against using noindex to pick a canonical within one site, because it blocks the page from Search entirely instead of consolidating it. Use a redirect or a canonical.

### How do I check which canonical Google chose?

Open the URL Inspection tool or the Page Indexing report in Search Console and compare the user-declared canonical with the Google-selected canonical. A difference points at a conflicting signal such as links or sitemap entries.
