Noindex is a robots directive that asks compliant search crawlers not to show a page or resource in search results while visitors can still access it.
What Noindex means
Noindex controls index presentation, not access control. Sensitive material needs authentication or removal; robots.txt is a crawl instruction and can prevent a crawler from seeing a meta noindex.
Noindex is a robots directive that asks compliant search crawlers not to show a page or resource in results while the URL can remain accessible to visitors and links.
A practical inspection workflow
Choose meta robots for HTML pages and X-Robots-Tag for non-HTML resources. Keep the directive visible to the crawler and make the page’s intended index state explicit.
What to verify
Fetch the rendered HTML and response headers, verify the directive, check URL Inspection, then allow recrawling time before judging removal.
Limits and common mistakes
Do not block a URL in robots.txt and expect Google to reliably read its noindex directive, or use noindex as a privacy control.
Before adding noindex, state the business and user reason for keeping the URL accessible but out of search. Common cases include an internal-results page, a temporary campaign state, or a staging environment. Then choose the correct delivery method, add a regression check, and record the intended reversal condition. For staging, treat noindex as one release gate alongside access controls and production-readiness checks, never as the sole protection for confidential content.
How the Directive Is Seen
Use either <meta name="robots" content="noindex"> in an HTML document or X-Robots-Tag: noindex in an HTTP response; the header can also control non-HTML resources. Do not block a URL in robots.txt when Google must crawl it to see the noindex directive.