Pages carry noindex directives that prevent them from appearing in search results. Verify every one is intentional.
By Seoxpert Editorial · Published · Updated
noindex is a one-way door: pages carrying it are pulled from Google's index. When applied accidentally — a staging rule pushed to production, a template-level directive, a CMS toggle left on — it silently removes content from search with no warning in Search Console for days.
An accidentally-noindexed high-traffic page loses all organic traffic within weeks of Google re-crawling it. Recovery is slow: removing the directive only restarts indexing; ranking takes additional time to re-establish.
Scanner reads each page's <meta name="robots"> and googlebot directives and the X-Robots-Tag HTTP response header. Any occurrence of "noindex" or "none" in either place flags the page.
Meta robots noindex (in the HTML head)
<!-- noindex: not shown in search results -->
<meta name="robots" content="noindex" />
<!-- target only Googlebot -->
<meta name="googlebot" content="noindex" />
<!-- remove: delete the tag entirely (not content="index") -->X-Robots-Tag HTTP header (applies to any resource type)
HTTP/1.1 200 OK
Content-Type: application/pdf
X-Robots-Tag: noindex
# Useful for non-HTML resources where meta tags are impossible (PDFs, images).No. It instructs Google not to include the page in search results, but Google must still crawl the page to see the directive. Do not also disallow the page in robots.txt, because that prevents Googlebot from ever seeing the noindex — the page may stay indexed from before.
Typically one to a few weeks, depending on how often Google re-crawls the URL. You can speed this up by requesting recrawl in Search Console, or by using the URL removal tool for urgent cases.
noindex,nofollow tells Google not to index the page and not to follow any links on it. Useful for private thank-you pages or internal tools that link to content that should also stay out of the index.
Pages are being excluded from Google's search index due to the presence of 'noindex' directives, either in the HTML meta tags or HTTP headers. This prevents the
This issue occurs when a page is marked with both a noindex directive and a rel="canonical" pointing to a different URL. This creates conflicting signals for se
Run a scan to see if Pages with Noindex Directives affects your pages.
Scan my website →