Canonical target is noindex: how to fix the conflict

What it means

This page has a rel="canonical" pointing to a URL that carries a noindex directive — in a <meta name="robots"> tag or an X-Robots-Tag response header. The source page asks Google to index the target, while the target asks Google not to. That conflict can cause both pages to disappear from the index.

Why it matters

A canonical is a consolidation signal: it tells Google "treat that URL as the authoritative version of this content." When Google follows the canonical and finds noindex on the target, its documented behavior is to interpret that noindex as applying to the entire duplicate cluster — so the source page, which has no noindex of its own, may be excluded because the page it canonicalizes to is excluded. This is one of the most damaging canonicalization mistakes because it is invisible in a simple crawl: the source page returns 200 with clean markup and no noindex, and the problem only surfaces when you check what the target actually says. Unlike a canonical pointing to a redirect, there is no "Google will probably figure it out" fallback — the two directives pull in opposite directions and noindex tends to win.

How to fix it

1. If the target should be indexed, the noindex is a mistake: remove the noindex meta tag or X-Robots-Tag header from the target and verify it returns 200 and is crawlable.
2. If the target's noindex is intentional, change the canonical on this page to point at a URL that is indexable — returns 200, has no noindex, and is not blocked in robots.txt.
3. If neither page should be indexed, apply noindex to this page too and redirect it to the correct indexable URL so users and links reach a live destination.
4. Verify the target's robots directives with a direct HTTP request (curl -I) rather than browser rendering — JavaScript-injected robots tags require a rendered crawl to detect.

When it's not a problem

If the noindex on the target is temporary — a page staged for review before launch — and you expect to lift it before the next crawl, the practical risk is low; Crawlinx still flags it because the crawler sees the state at crawl time. Likewise, if this page is itself excluded from the index by robots.txt and the canonical is only a soft hint for other crawlers, neither directive causes real harm. Review whether Google can actually reach the source page before treating this as urgent.

How common is it?

306 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.

Related guides

• Canonical Tags: How rel=canonical Fixes Duplicates
• Duplicate Content: How Canonicalization Fixes It
• Pagination SEO: rel=next/prev & Infinite Scroll
• Meta Robots & X-Robots-Tag: noindex/nofollow Guide