Can I use noindex and a canonical tag on the same page?
Google advises against it: use a canonical to choose between duplicate pages and noindex to keep a page out of search, not both. Google says noindex “will completely block the page from Search”, and no Google page we read says what Google does when both are present on one page.
The short version
- Google's current canonicalization page: “We don't recommend using noindex to prevent selection of a canonical page within a single site, because it will completely block the page from Search.
rel="canonical"link annotations are the preferred solution.” - Google's 2009 Search Central blog FAQ asks “Should I use a noindex robots meta tag on pages with a rel="canonical" link element?” and answers: “No, since those pages would not be equivalent with regards to indexing—one would be allowed while the other would be blocked.” The post is old, and its banner marks only its syndication advice as outdated.
- A 2013 Google post on common canonical mistakes says to “Verify the rel=canonical target doesn't contain a noindex robots meta tag” and to “Double-check that your rel=canonical target exists”.
- What a noindex does: “Google will drop that page entirely from Google Search results, regardless of whether other sites link to it.”
- We found no sentence, on the Google pages we read, about what happens to the canonical signal on a page that is also noindex. Treat anyone who states it as fact as guessing.
Which one do you mean?
| You want… | Use | Why |
|---|---|---|
| Several URLs with the same content to count as one | rel="canonical" on the duplicates, no noindex | Google lists “To consolidate signals for similar or duplicate pages” as a reason for a canonical. |
| A page kept out of search results | noindex on that page, and no canonical pointing to another page | Google says to use noindex to prevent indexing; it drops the page entirely. |
| A filtered or sorted list kept out of the index | noindex | Google's pagination guide: “block unwanted URLs from being indexed with the noindex robots meta tag”. |
| A full “view all” page kept out of results | noindex on it, and no canonical from the component pages to it | Google's 2011 post says to do both if you “strongly desire your view-all page not to appear in search results”. |
Why the pair is a bad idea
The two instructions pull in opposite directions on the same page: a canonical says another URL is the main version of this content, while noindex says not to show this page at all. The RFC that defines the link relation requires the canonical target to “identify content that is either duplicative or a superset of the content” of the page that names it, and advises against a target that “returns an error code, such as a 4xx response”. Google's own pages say canonicalization is “a hint, not a rule”, so a pair of conflicting instructions leaves Google to decide.
What Google's Page indexing report says about the statuses you are most likely to see: “URL marked 'noindex'” is “When Google tried to index the page it encountered a 'noindex' directive and therefore did not index it.” “Alternate page with proper canonical tag” means “This page correctly points to the canonical page, which is indexed, so there is nothing you need to do.” And “Duplicate without user-selected canonical” is “not an error, but is working as intended, because Google does not serve duplicate pages.”
Check one page for both
Paste the URL. The checker reads the meta robots and googlebot tags and the X-Robots-Tag header, reads the canonical tag, fetches the canonical target, and flags a noindex combined with a canonical to another URL.
What we tested
On 2026-10-19 we ran the live Meta, Canonical & Noindex Checker on small test pages we built for this guide, each carrying only the signals named in the table. The pages are on a throwaway preview, not part of this site.
| The page | What the checker reported |
|---|---|
noindex in a meta tag, and a canonical pointing to itself | noindex: “The page is set to noindex”, Review. Canonical: “Self-referencing canonical”, Passed. No conflict raised. |
noindex in a meta tag, and a canonical pointing to another page | “noindex combined with a canonical to another URL”: Fix before publishing. Its explanation: “The two signals contradict each other; search engines may ignore the canonical.” Advice: “Use either noindex or a canonical to the main URL, not both.” |
X-Robots-Tag: noindex as a header, and a canonical pointing to another page | The same “noindex combined with a canonical to another URL”: Fix before publishing. |
| A canonical pointing to another page, no noindex | “The canonical points to a different URL”, Review; noindex: “No noindex in meta robots or X-Robots-Tag”, Passed. |
| A canonical pointing at a page that is itself noindex | Only “The canonical points to a different URL” (Review) and “The canonical target returns 200”. Not flagged: the checker does not look at the target's robots directives, although Google's 2013 post says to verify the target has no noindex. |
So the checker catches the pair when it is on one page, in a meta tag or in a header. It does not catch a canonical that leads to a noindex page; check that by running the checker on the target too.
How to fix it
- Find where each instruction comes from. A canonical to another URL and a noindex often arrive together from an SEO plugin setting, a theme, or a template used for “thin” pages. The header version comes from the server, a CDN or a framework, and does not show in the page source.
- Decide what the page is for. If it duplicates a better page, keep the canonical and remove the noindex. If it should stay out of search, keep the noindex and remove the canonical to another URL.
- Do not block the page in robots.txt: Google says that if the crawler can't access the page, “the crawler will never see the noindex rule”, and the 2009 FAQ adds that a blocked page's canonical cannot be found either.
- Run the check again, and then use URL Inspection in Search Console to see which status the page gets once Google recrawls it.
What this can't tell you
It cannot say how Google will treat a page that carries both: that is not documented in the pages we read. The most direct official statements are a 2009 blog FAQ and a 2013 blog post, both marked by Google as old, plus the current advice not to use noindex to choose a canonical. We could not read Bing's help pages (they are not available as text), so this guide covers Google only.
Related: Excluded by ‘noindex’ tag, Duplicate, Google chose different canonical than user and Alternate page with proper canonical tag.
Sources
We read these official pages on 2026-10-19.
- How to Specify a Canonical with rel="canonical" and Other Methods (page dated 2026-07-10)
- What is URL Canonicalization (page dated 2026-08-20)
- Block Search Indexing with noindex (page dated 2025-12-10)
- Handling legitimate cross-domain content duplication - Google Search Central Blog (page dated 2009-12-15)
- 5 common mistakes with rel=canonical - Google Search Central Blog (page dated 2013-04-08)
- View-all in search results - Google Search Central Blog (page dated 2011-09-15)
- Pagination Best Practices for Google (page dated 2025-12-10)
- Page indexing report - Search Console Help
- RFC 6596: The Canonical Link Relation
Fixed this one? Before you send people to the page, run the full pre-publish check for everything else: indexing signals, link preview, broken links, alt text, structured data and HTTPS in one pass.