Homepage noindex directive: scope and verification
If this finding appears in a report, a sampled homepage response or HTML contained a recognised noindex directive. Check the exact URL, final response and crawler-specific scope. This reference page does not inspect your homepage or establish its current Google indexing state.
Why this matters
When Google crawls an accessible page and reads an applicable noindex directive, that page is excluded from Search. A homepage directive does not automatically apply to every URL on the domain. A shared template or response-header configuration can affect other pages, but each affected response must be checked. This observation alone does not establish a site-wide removal or explain a traffic decline.
How to fix it
Confirm whether exclusion is intentional. Preserve it for content that should stay out of search, and use authentication where access must remain private. For an intended public search page, inspect HTTP X-Robots-Tag headers and robots or googlebot meta tags in delivered and rendered HTML. Remove an unintended rule at its actual template, CMS, server or hosting source; adding index elsewhere may not override another restrictive rule. Check representative URLs if the configuration is shared. After deployment, verify the actual responses and use Search Console URL Inspection. Google must be able to fetch a page to read its directives. Recrawling and renewed indexing are not immediate or guaranteed.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit