Canonical vs Noindex: Which to Use (and Why Not Both)
Can you use a canonical tag and noindex on the same page?
You can, but you usually shouldn't. A canonical asks Google to merge the page into another URL; noindex asks Google to drop it. Google's John Mueller advises picking one.
- •Want the page out of search entirely: use noindex alone.
- •Want its signals merged into another URL: use a canonical alone.
- •Google doesn't recommend noindex to steer which URL becomes canonical.
- •A canonical that points to the page itself plus noindex is not a conflict.
What Each Tag Tells Google
noindex (a robots meta tag or an X-Robots-Tag header) is a rule. Google’s documentation says that once Googlebot crawls the page and sees it, Google drops the page entirely from its search results, even if other sites link to it. It only works if Google can crawl the page, so it must not be blocked in robots.txt.
rel="canonical" is a strong signal, not a rule. It says: this page is a copy, please treat that other URL as the main one. Google usually follows it, but it can pick a different canonical.
Put both on one page, pointing at different URLs, and you’re asking for two different outcomes: “remove me” and “merge me into that page.”
What Google Has Said About Using Both
In its documentation: Google doesn’t recommend using noindex to prevent a page from being picked as canonical within a single site, because noindex blocks the page from search completely. It calls rel="canonical" the preferred solution for duplicates.
John Mueller, 2021: in a Search Central office-hours video he said both can be OK, and the choice depends on your preference. With noindex the page is definitely not shown; with a canonical it’s more likely not shown. He added that you can technically use both, and that if external links point at the page, Google may be able to forward some signals.
John Mueller, 2024: asked on Reddit whether that still held, he said he would just pick one, noting that links on a noindexed page “can be picked up, but it’s not guaranteed.” His point: make your preference clear instead of relying on maybes.
So the combination isn’t forbidden, but it gives you no reliable benefit. Choose the tag that matches what you actually want.
Which One to Use
| The page is… | Use | Examples |
|---|---|---|
| A duplicate of another live page | Canonical to the main URL | Tracking parameters, sort orders, print versions, product variants with the same content |
| Useful to visitors but not for search | noindex (keep it crawlable) | Internal search results, thank-you pages, thin tag archives, account pages |
| Gone, with a replacement | 301 redirect | Discontinued product with a newer model, merged articles |
| Gone, with no replacement | 404 or 410 | Deleted pages with nothing similar |
| Never worth crawling | robots.txt Disallow | Endless filter combinations, internal search URL spaces |
One caution on the last row: robots.txt stops crawling, so Google can’t see a noindex or a canonical on a blocked page. Don’t combine a Disallow with either tag and expect the tag to work.
The exception: a self-referencing canonical
A noindexed page whose canonical points to itself isn’t a conflict: it isn’t asking to be merged anywhere. Many templates output a self-referencing canonical on every page, so internal search or thank-you pages often end up with both tags. That’s fine. The problem is only noindex plus a canonical that points to a different URL.
Where the Conflict Usually Comes From
Few people add both tags on purpose. They usually come from two systems that don’t know about each other:
- Pagination: one setting noindexes page 2 and beyond while a template points their canonical at page 1. Neither is needed: each page in a series should have its own self-referencing canonical, as covered in pagination and canonical tags.
- Filter pages: facets get a canonical to the category “for duplicates” plus a noindex “to save crawl budget.” Google’s crawl budget guide notes noindex doesn’t save crawling anyway; robots.txt does.
- Headers you can’t see in the HTML: an
X-Robots-Tag: noindexadded by a server rule, CDN or edge function on a whole path, while the page itself prints a canonical. View-source won’t show it; the response headers will. - Leftovers: a noindex added during a staging push or a redesign that nobody removed, while the canonical stayed.
- Logged-out views: a page that shows noindex to logged-out visitors (Googlebot is always logged out) but canonicalizes to a public page.
A Note on “noindex, follow”
“follow” isn’t a separate rule in Google’s robots meta tag documentation; following links is simply the default. And in 2017 Mueller said that a page kept on noindex for a long time is eventually treated like noindex, nofollow. Don’t count on a long-term noindexed page to pass value through its links. More in noindex, follow explained.
How to Find Pages With Both Tags
Check the HTML and the headers; either can carry the noindex.
URL=https://example.com/shoes?color=red # noindex or canonical in the HTML curl -s "$URL" | grep -iE 'name="robots"|rel="canonical"' # noindex or canonical in the HTTP headers curl -sI "$URL" | grep -iE '^x-robots-tag|^link:'
In Search Console, open the “Excluded by ‘noindex’ tag” examples in the Page indexing report and inspect a few: if the user-declared canonical is a different URL, you’ve found the pattern. Our free canonical checker tests 30 URLs from your sitemap and flags any that carry noindex or point their canonical elsewhere; a page listed in your sitemap shouldn’t do either.
How to Fix It
- List the affected URLs and group them by template.
- Decide what each group is for. A duplicate of another page? Something that shouldn’t be in search? Or gone?
- Duplicates: remove the noindex and keep the canonical.
- Not for search: keep the noindex, and make the canonical self-referencing or remove it.
- Gone: replace both with a 301 to the replacement, or a 404/410 if there isn’t one.
- Fix the source, not the page: the plugin setting, template, server rule or CDN rule that added the tag.
- Recheck in URL Inspection with a live test to confirm what Google now sees.
FAQ
Which wins when a page has both?
Google hasn’t published a rule for it. Noindex is a rule Google follows, while a canonical is a hint, and Mueller’s advice is to avoid the question by picking one.
Does noindex pass link value to the canonical URL?
Not reliably. Mueller has said links on a noindexed page can be picked up but it’s not guaranteed. If you want signals merged into another URL, use a canonical (or a 301) without noindex.
Should noindexed pages be in my sitemap?
No. A sitemap should list pages you want indexed. Listing noindexed URLs sends mixed signals.