Comparisons

Canonical vs noindex

A canonical tag says “this page is a version of another URL; show that one in search,” while noindex says “do not keep this page in the index at all.” Use a canonical for duplicates whose signals you want gathered on one URL, and noindex for pages that should not appear in search under any URL.

Both tags decide what ends up in the index, which is why they get mixed up. The difference is what happens to the page. A canonical points to another URL: search engines are asked to treat the two as one page and show the canonical one, and links pointing at either version count towards it. noindex points nowhere: the page is dropped from the index and nothing is consolidated.

They are also different kinds of instruction. Google treats rel=“canonical” as a strong hint, not a command, and can pick a different canonical if other signals disagree, such as internal links, the sitemap or redirects. noindex is a directive that Google follows when it can crawl the page and see it. That last condition matters: a page blocked in robots.txt is never fetched, so its noindex is never read.

Google’s documentation advises against using noindex to choose a canonical within one site. If two URLs show the same content, a canonical (or a redirect) tells the search engine which one you want. noindex on one of them just removes it, and any links pointing at it stop helping the other.

In Search Console the two show up differently as well. Pages with a canonical elsewhere appear as “alternate page with proper canonical tag”, which is normally fine. Pages with noindex appear as “excluded by noindex tag”, which is fine when it is on purpose and a problem when it is not.

Side by side

AspectCanonicalnoindex
What it saysThis URL is a version of another; index that oneDo not index this URL
Kind of signalA strong hint the search engine may overruleA directive, followed when the page is crawled
Where it goesA rel="canonical" link in the head, or an HTTP Link headerA robots meta tag, or an X-Robots-Tag HTTP header
Links to the pageConsolidated on the canonical URLNot consolidated anywhere
Typical useTracking parameters, sorted or printed versions, syndicated copiesThin pages, internal results, thank-you pages, personal views
Needs crawling to workYesYes: never block a noindex page in robots.txt
In Search ConsoleAlternate page with proper canonical tagExcluded by noindex tag

When to choose Canonical

  • The same content is reachable at several URLs, and you want one of them in search.
  • You publish a copy of an article elsewhere and want the original to rank.
  • Every indexable page should also carry a canonical to itself, so stray parameters do not create duplicates.

When to choose noindex

  • The page should not be found in search at all, whatever URL it is on.
  • The page is too thin to be useful yet, and you want it live for visitors but out of the index until it has more.
  • The page is personal or temporary, such as a result view or a confirmation page.

An example from our own sites

Every page on audacian.eu is prerendered with a canonical to itself, in every language, and the build checks canonicals, hreflang and uniqueness. A /work topic page with fewer than three distinct pieces of work stays live but carries noindex and leaves the sitemap until it has enough in it. Shared results of our AI search checker (a tool URL with ?site=) answer with noindex, because each is one person’s result, and point their canonical at the tool page. On Videojam, our own platform, the coverage report dated 23 October 2026 lists 92 URLs as alternate pages with a proper canonical and 367 pages excluded by noindex, both on purpose.

Questions

Can a page have both a canonical and noindex?
It can, but the signals pull in different directions, so use it only where either outcome is fine. Our shared checker results are the case: the result URL stays out of search either way.
Why did Google pick a different canonical from mine?
Because a canonical is a hint. Make the other signals agree: link internally to your canonical URL, list only it in the sitemap and redirect old versions to it.
Should I noindex duplicate pages?
Usually not. A canonical or a redirect consolidates the duplicates on one URL; noindex simply drops the page and its links stop helping.

Tell us what you're launching.

Book a 20-minute intro call, or email a few lines about what you're launching. We'll reply with a rough plan and a price range, whether or not we end up working together.