Canonical Points to a Noindex URL: Fixing the Contradiction

What this means

A canonical tag (rel="canonical") tells search engines which URL is the preferred, indexable version of a piece of content. A noindex directive (meta robots tag or X-Robots-Tag header) tells search engines to keep a URL out of the index entirely.

This issue fires when the canonical target, the URL this page nominates as the one to index, is itself marked noindex. You are directing ranking signals toward a page you have separately told Google to drop. A canonical target should always be an indexable page that returns a 200 OK response, not one blocked by noindex.

Why it matters

These are contradictory instructions. The canonical says "this is the URL to index and to consolidate ranking signals onto." The noindex on that same URL says "do not index this page." When you rely on a search engine to resolve a contradiction, you hand the decision to its interpretation rather than stating your own preference clearly.

Google does not recommend combining these signals. In practice, Google often assumes the canonical is a mistake and ignores it, leaving the canonicalized page without a valid canonical. Because the named target is noindex, Google may also decline to consolidate signals onto it. Outcomes are unpredictable: Google may drop the canonical, drop the target, or keep neither URL indexed. John Mueller has been direct that you should pick one signal or the other, because a noindexed canonical may or may not be honored, and SEO works best when your preference is unambiguous.

For more on how each directive behaves, see our canonical tags complete reference and our meta robots and X-Robots-Tag reference.

How it gets flagged

A crawler flags this when it follows a page's canonical link, requests that target URL, and finds a noindex directive on it. Screaming Frog reports it under the Canonicals tab as part of its non-indexable canonical checks; Sitebulb surfaces it as a canonical-to-noindex hint. The crawler compares the destination's indexability against the expectation that a canonical resolves to an indexable, 200-response page, and raises the issue when noindex breaks that expectation.

You can confirm it in Google Search Console: inspect the affected URL and watch for indexing states that reflect the conflict, or review the Search Console page indexing report for pages excluded by noindex that other URLs point to as canonical.

How to fix it

Resolve the contradiction so both signals agree. Decide which URL you actually want indexed, then pick one of two paths.

Option A: Point the canonical to an indexable URL

If the noindex on the current target is intentional, that URL was never the right canonical. Repoint the canonical to a page you genuinely want indexed (one that returns 200 and has no noindex).

<!-- Before: canonical points to a noindex page -->
<link rel="canonical" href="https://example.com/staging-page/">
  (that page sends:) <meta name="robots" content="noindex">

<!-- After: canonical points to the indexable page -->
<link rel="canonical" href="https://example.com/products/blue-widget/">

Option B: Remove the noindex from the canonical target

If the named canonical really is the URL you want to rank, then it should not be noindex. Remove the noindex from that target page (both the meta robots tag and any X-Robots-Tag header) so it can be indexed.

<!-- Remove this from the canonical target -->
<meta name="robots" content="noindex,follow">

<!-- Replace with (or simply omit the noindex) -->
<meta name="robots" content="index,follow">

Also check the HTTP response headers, since a noindex set there overrides what the HTML claims:

# Remove a header like this on the canonical target
X-Robots-Tag: noindex

After the change, re-crawl the page and confirm the canonical now resolves to an indexable 200 URL. Do not try to keep both signals on the same page hoping to "hide" a duplicate while passing its value, that is exactly the mixed signal this issue warns against. Use one tool for one job: canonical to consolidate, noindex to exclude.

False positives

A few cases look like this issue but may be acceptable or harmless:

• Self-referencing noindex page. A page that is noindex and canonicals to itself is not really this issue, it is simply a noindexed page. There is no contradictory cross-URL instruction to resolve, though the self-canonical adds nothing.
• Staging or temporary noindex. If the target is noindex only on a staging environment and is indexable in production, the live site is fine. Verify you are auditing the production response.
• Stale crawl data. If you removed the noindex recently, an older crawl may still report it. Re-crawl and confirm against the live header and HTML before acting.

FAQ