⚠️ Conflicting signals — noindex takes priority, canonical is ignored

This page has both <meta name="robots" content="noindex"> and <link rel="canonical" href="https://sallymills.com/indexing/"> in its <head>. These directives point in different directions. noindex wins. The canonical consolidation to /indexing/ does not happen. Check view-source on this page to see both tags present simultaneously.

What this demonstrates

This page carries two directives in its <head> that conflict with each other. The <meta name="robots" content="noindex"> tag tells Google not to index this page. The <link rel="canonical" href="https://sallymills.com/indexing/"> tag signals that this page's preferred version is the Indexing Directives hub.

These cannot both be satisfied. noindex is an absolute directive. Canonical is a preference signal. When they conflict, noindex wins. The canonical consolidation does not occur.

Why it matters

This conflict is a common misunderstanding during migration and consolidation work. A team is deprecating old URLs. They add noindex to prevent indexation during the transition, and they also set canonicals pointing to the new preferred URLs, expecting both to work simultaneously.

The expectation: "noindex prevents this URL from being indexed, and the canonical passes signals to the destination." The reality: once noindex is present, Google stops processing this page as a content source. The canonical hint is ignored. The destination page receives no consolidation signal from this URL.

If you need to consolidate a page's signals into another URL, use a 301 redirect — not a noindex + canonical combination. Redirects pass link equity and tell Google definitively where the content has moved. A noindexed page with a canonical passes nothing.

The code

Both directives present in the <head> of this page — and the signal hierarchy that resolves the conflict.

<!-- This page's <head> — both directives present --> <head> <meta name="robots" content="noindex"> <link rel="canonical" href="https://sallymills.com/indexing/"> </head> # Signal hierarchy: noindex > canonical # Google sees noindex → stops processing this page as a content source # Canonical is a content-level signal → not processed when noindex is present # Result: /indexing/ receives NO consolidation signal from this page # If you need to consolidate AND suppress this URL: # Use a 301 redirect instead — not noindex + canonical HTTP/1.1 301 Moved Permanently Location: https://sallymills.com/indexing/

What Google does

  1. Googlebot crawls this page and reads the raw HTML response.
  2. In the <head>, it finds both a noindex meta tag and a canonical link tag.
  3. The noindex directive is processed first as an absolute signal. Google determines this page should not be indexed.
  4. Because the page is noindexed, Google does not process it as a content source. The canonical hint — which is a content-level signal — is not acted upon.
  5. The canonical destination (/indexing/) receives no consolidation signal from this page.
  6. This page is excluded from the index. The intended signal consolidation does not happen.

How to detect it

  • view-source Ctrl+U (Windows) / Cmd+U (Mac) → search for robots and canonical in the <head>. You'll find both present on the same page. Seeing a noindex meta tag alongside a non-self-referencing canonical is the conflict pattern to flag.
  • curl Open Command Prompt (Windows) or Terminal (Mac) and run: curl -L https://sallymills.com/indexing/noindex-with-canonical/ | grep -E '(noindex|canonical)' → Returns both tags from the raw response. The coexistence of a noindex and a cross-page canonical on the same URL is the signal. (Windows: replace | grep -E '(noindex|canonical)' with | findstr "noindex" or | findstr "canonical".)
  • Google Search Console This page appears under "Excluded by 'noindex' tag" in the Indexing report. The canonical destination (/indexing/) does not gain any consolidation signal from this page. If you expect signal consolidation from noindexed pages with canonicals, it won't appear in GSC.
  • Screaming Frog Crawl the site → Directives tab → filter for pages where Meta Robots column shows "noindex" AND Canonical URL column shows a URL that differs from the Address column. Any URL matching both conditions has this conflict. This is the most reliable way to find the pattern at scale.

How to fix it

Decide what you actually want to happen, and pick the right tool:

  • If the page should be removed and its signals consolidated to another URL: use a 301 redirect. Redirects pass link equity and tell Google definitively where the content has moved. Remove the noindex and canonical tags from the page and redirect instead.
  • If the page should be noindexed but remain accessible (e.g. preview page, draft): keep the noindex, but understand the canonical is not doing anything. Remove it to avoid confusion.
  • If the page should be indexed under a different canonical URL: remove the noindex. A canonical without noindex allows indexation to proceed with the canonical signal intact.

The key principle: noindex and canonical cannot work together as a combination. Noindex stops Google from treating the page as a content source, which is the prerequisite for canonical signals to be processed.

← Back to Indexing Directives