Marketing & Getting Customers
What does noindex mean, and how do I check whether a page is accidentally blocked?
The short answer
noindex tells a supporting search engine not to include a page in its search results. Check the page in Search Console, inspect the live HTML and response headers, and review your CMS or SEO-plugin visibility settings. If the rule is accidental, remove it and ask Google to recrawl the page.
Where the rule can hide
An HTML page can carry this instruction in its <head>:
<meta name="robots" content="noindex">
A server can also send an X-Robots-Tag: noindex response header. That header is easy to miss because it doesn't appear in the visible page. Google's noindex documentation confirms that either method can remove a page from Google Search after Google crawls it.
On WordPress, also check the page's SEO settings and Settings > Reading. A staging-site setting or an importer can unintentionally carry over to the live site. If one page is affected, inspect that page. If many are affected, start with the sitewide settings and templates.
Check it three ways
First, enter the exact URL in Search Console's URL Inspection tool. Read both the indexing result and the live test. Look for an explicit noindex finding and note whether Google could crawl the page.
Second, view the page source and search for noindex. Don't rely only on the browser's visual inspector because scripts and plugins can alter what you see.
Third, check the HTTP response headers with your host's diagnostic tool or a reputable header checker. If you're not comfortable changing server configuration, send the result to your host or developer rather than guessing.
Remove the block without creating a new one
If the page belongs in search:
- Turn off the page-level or sitewide
noindexsetting. - Clear site, plugin, and CDN caches.
- Confirm the live source and headers no longer contain the rule.
- Make sure robots.txt allows Google to crawl the page.
- Inspect the live URL again and request indexing.
That fourth step surprises people. Google has to crawl a page to see its noindex rule. Google's guidance says that if robots.txt blocks the URL, Googlebot may never see a newly added or removed instruction. Robots.txt isn't a substitute for noindex.
Keep noindex intentionally on private thank-you pages, internal search results, unfinished drafts, or other pages you don't want in public search. But remember that noindex is not access control. Anyone with the URL may still open the page. Password protection or proper authentication is what protects private material.
Sources and further reading
- Google Search Central: Block Search indexing with noindex
- Google Search Console: URL Inspection tool
A free next step
You don't have to build this alone
Bring your questions, share what you're working on, and meet other women building businesses from home. It is free to join.
Related Questions
- How do I check, request, and troubleshoot Google indexing for a page?
- What is a canonical URL, and why might Google choose a different one?
- What do impressions, clicks, CTR, and average position mean in Search Console?
- How do I find search queries in Search Console that are already bringing visitors to my site?
Related WAHMN resource
If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.