Canonical Tag and Noindex Together

Can you use canonical and noindex together?

The short answer: avoid it. Putting a rel=canonical tag pointing to another URL and a noindex directive on the same page sends Google two instructions that work against each other, and the outcome is unreliable. If the goal is to consolidate duplicate content, use canonical alone. If the goal is to keep a page out of the index entirely, use noindex alone. Combining them on the assumption that Google will neatly sort out the intended outcome is not a safe bet.

Why rel=canonical and noindex conflict

The conflict comes down to what each signal is actually asking for. A cross-page rel=canonical says: "this page is a duplicate — consolidate its ranking signals onto the target URL, and index that target instead." A noindex directive says something different: "drop this page entirely; do not serve it in search results." One is about redirecting credit toward another URL while keeping the page itself part of the index picture; the other is about removing the page from consideration altogether. Google cannot cleanly honor both goals on the same page at once.

Here's what that conflict looks like in code — a page with a noindex meta robots tag and a canonical pointing elsewhere:

<meta name="robots" content="noindex">
<link rel="canonical" href="https://www.example.com/preferred-page/">

Read literally, this page is simultaneously saying "don't index me" and "my signals belong over there, where that page should be indexed instead." Those are not the same instruction, and Google has to decide which one governs.

What Google actually does with the conflict

Gary Illyes addressed this directly in 2020: "something with noindex will never reach the serving index, but we will have the fetched copy for things like link graph calculation." In practice, noindex is a firm rule that Google obeys, while rel=canonical is only a hint that Google can choose to follow or override. When the two conflict on the same page, noindex tends to win — the page is dropped from the index — which means the consolidation the canonical was asking for may not actually happen.

There's a nuance worth understanding: Google still fetches (crawls) the noindexed page even though it won't serve it, and can use that fetched copy for things like link graph calculation. That's a narrow technical detail, not a reason to rely on the combination working as intended. John Mueller's guidance moved, by 2024, to a plain "just pick one" — don't mix the two signals on a single page.

What to do instead

The fix follows directly from the two goals being incompatible:

• To consolidate a duplicate page into a preferred one: use a cross-page canonical alone. Don't add noindex to the duplicate — the canonical is the mechanism meant to handle that consolidation.
• To keep a page out of the index entirely: use noindex alone, and drop the cross-page canonical pointing elsewhere. A self-referencing canonical alongside noindex is generally considered harmless, since noindex governs indexing regardless of what the canonical says about the page's own preferred URL.
• Don't use noindex as a way to force canonical selection. Adding noindex to a page in the hope that it will nudge Google toward picking a different URL as canonical is not a reliable technique — noindex removes the page from the index; it doesn't function as a canonicalization tool.

How to find pages with both a canonical and a noindex

This conflict tends to originate from systems, not from a single deliberate decision. Common sources include plugins or templates that automatically emit both a noindex and a cross-page canonical on paginated or faceted URLs, and developers who add noindex to "fix" a duplicate-content page that already has a canonical tag pointing elsewhere — not realizing the canonical was already the intended fix.

To find affected pages, crawl the site and check each page's HTML head and HTTP headers for the combination of a meta robots noindex tag (or an X-Robots-Tag header set to noindex) alongside a rel=canonical pointing to a different URL. Google Search Console's URL Inspection tool is also useful on a page-by-page basis: it will show both the noindex status and the user-declared versus Google-selected canonical, making the conflict visible for any URL you check individually.

Frequently Asked Questions