Quick answer

Use noindex deliberately for pages that should not appear in search results, such as private, internal, or low-value utility routes. Remove it from public pages that are intended to be indexed. A noindex finding is not automatically an error; its meaning depends on the page’s purpose and whether crawlers can receive the directive.

What the issue means

A page can send a noindex instruction in a robots meta tag or HTTP X-Robots-Tag header. The directive tells compliant crawlers not to index the resource. It does not make a page private, replace authentication, or guarantee immediate removal from every index.

Why it matters for SEO

An accidental noindex can keep a valuable page out of search results. An intentional noindex can protect search quality by excluding login pages, account screens, internal search results, or temporary variants. Blocking a page in robots.txt is not a substitute for noindex when the goal is de-indexing, because a crawler may need to fetch the response to see the directive.

How NOTABIS detects it

The noindex-directive rule examines measured robots directives in the page response. NOTABIS marks private, authenticated, or filtered-query contexts as intentional where the audit can identify that context; public pages with the directive remain reviewable. The report shows the affected URL and evidence available from the crawl.

How to check it yourself

Inspect both the HTML and response headers:

curl -sSI https://example.com/page
curl -s https://example.com/page | grep -i robots

Confirm the final URL after redirects, the environment being tested, and whether the page is genuinely intended for search.

How to fix it

If the page should be indexed, remove the accidental meta or header directive and deploy the correct environment configuration. Check shared layouts, staging flags, CMS SEO settings, and response middleware. If the page should remain excluded, document the reason and ensure the directive is consistently emitted on the final response.

After changing it, verify the live response and request reprocessing through the relevant search-engine tools when appropriate.

When it is intentional or does not need fixing

Login, checkout, account, internal search, duplicate-filter, and private application routes commonly need noindex. Do not remove it just to make an audit score better.

Related issues

Read canonical and noindex conflicts, missing canonical URLs, and HTTP error responses.

Run a NOTABIS audit

NOTABIS helps identify where noindex is present and provides page-level evidence so public and intentional exclusions can be separated.