Finding: Page Excluded From Search Indexing (noindex)
This finding means the scanned page tells search engines not to index it. It is an SEO/visibility signal, not a security finding — and it is frequently intentional. The point of this finding is to make sure it's intentional.
Last updated August 12, 2026.
What it means
A page can be excluded from search results via an X-Robots-Tag: noindex HTTP response header, or a <meta name="robots" content="noindex"> tag in its <head>. Nivaronix found one or both on the scanned page.
Why it matters
Noindex is a completely normal, deliberate choice for pages you don't want in search results — internal tools, thank-you pages, duplicate print views, legal boilerplate. The failure mode this finding exists to catch is different: a noindex tag left over from a staging environment, added while a page was being reworked, or set by a CMS/theme default and never removed, quietly keeping a page you actually want found out of search results indefinitely.
Does this affect your Nivaronix security score?
This is an SEO/visibility signal, not a security finding. Nivaronix reports it at Info severity, and Info-severity findings carry a 0-point deduction — this result does not change your Nivaronix security score.
What Nivaronix checks
Nivaronix checks the scanned page's response headers for an X-Robots-Tag value containing noindex, and scans the page body for a meta tag named robots or googlebot whose content attribute contains noindex. Either source triggering is reported as noindex present; the evidence lists which source(s) matched.
Example evidence (illustrative — not live scan data)
https://example.com/staging-preview: meta robots tag: noindex, nofollow
How to fix it
- Confirm whether this page is actually meant to stay out of search results. If it is, no action needed — this finding is informational.
- If it isn't, remove the
X-Robots-Tag: noindexheader from your server/CDN config, and/or delete the<meta name="robots" content="noindex">tag from the page template. - Check whether a CMS-level or theme-level default is the source, so the same mistake doesn't recur on other pages.
How to verify the fix
Re-run the Nivaronix scanner and confirm it now reports the page as indexable. Search engines also need to recrawl the page before the change takes effect in actual search results — requesting reindexing in Google Search Console speeds that up.