Skip to content

Homepage carries a noindex directive - it is being removed from Google

A noindex directive is an instruction, either in the page's code, a robots meta tag, or in the server's response headers, an X-Robots-Tag, that tells search engines not to include a page in their results at all. This check found that this site's homepage carries a noindex directive. It is one of the most common and damaging mistakes an audit can find, usually left behind by a "block search engines" setting from a staging build or site migration that was never switched off. A noindex on the homepage removes the entire site from Google over the following crawl cycles, which means organic search traffic collapses to near zero. Because it is almost always accidental rather than intentional, it is also one of the fastest, highest-impact fixes an audit can surface. Your developer should remove the noindex directive from the homepage immediately. In WordPress, this is under Settings > Reading, by unticking "Discourage search engines." Otherwise, check the page source for a robots meta tag and the site's response headers for X-Robots-Tag. Once removed, re-request indexing in Google Search Console. Budget about thirty minutes, plus a wait for Google to recrawl.

Why this matters

A noindex on the homepage removes the entire site from Google over the following crawl cycles, which means organic search traffic collapses to near zero. Because it is almost always accidental rather than intentional, it is also one of the fastest, highest-impact fixes an audit can surface.

How to fix it

Your developer should remove the noindex directive from the homepage immediately. In WordPress, this is under Settings > Reading, by unticking "Discourage search engines." Otherwise, check the page source for a robots meta tag and the site's response headers for X-Robots-Tag. Once removed, re-request indexing in Google Search Console. Budget about thirty minutes, plus a wait for Google to recrawl.