How to fix pages accidentally set to noindex
The fastest way to lose a page is to tell Google to forget it.
Check this page now
Free, no signup. We fetch the page live and read what a search engine would see.
A noindex directive removes a page from search completely. That is exactly right for a thank-you page and catastrophic for a service page — and because nothing about the page looks different, it can sit there for months.
There are two places it can come from, and most people only check one.
What usually causes it
The staging setting that shipped
"Discourage search engines from indexing this site" in WordPress, or a platform's staging toggle, left on at launch. It noindexes everything, and the site simply never appears.
The X-Robots-Tag header
A noindex can come from an HTTP header instead of the page. It is invisible in view-source, which is why so many of these take months to find.
A template applying it too broadly
Someone noindexes one page type and the rule catches a section. Category pages, paginated archives and filtered views are the usual casualties.
Blocked in robots.txt as well
If the URL is also disallowed, crawlers cannot see the noindex at all — and the page can linger in results with no description. Allow crawling first, then noindex.
How to fix it
Check the page above
The meta tag checker reads both the robots meta tag and the X-Robots-Tag header, so a directive hiding in the headers shows up next to one in the markup.
Decide whether it is deliberate
Thank-you pages, internal search results, cart and account pages should be noindexed. Service pages, articles, category pages and anything you would want a customer to find should not.
Remove it at the source
In WordPress, uncheck the site-wide discouragement setting and the per-post SEO toggle. In Shopify and Webflow it is in page settings. If it comes from a header, it is in your server or CDN configuration, not the CMS.
Make sure the page is crawlable
Check robots.txt does not also block it. A crawler that cannot fetch the page cannot see that you removed the noindex.
Ask for a recrawl
Use URL Inspection in Search Console and request indexing for the important ones. The rest come back on the next crawl.
What the audit checks
- Pages with a noindex robots meta tag
- Pages with a noindex X-Robots-Tag header
- Pages that are both noindexed and blocked in robots.txt
- Which of them have internal links or traffic, and so probably should not be
Check part of it right now, free
These read a live page and tell you what a search engine sees. No signup, no email.
Meta tag checker
Every tag in the head of your page, read back to you the way a crawler sees it.
robots.txt checker
One file, read carefully — because the expensive mistakes all live in it.
The issues behind this
Each has a full entry in the issue library: what it is, what it costs a business, and step-by-step fixes for WordPress, Shopify, Webflow and custom builds.
Noindex on an important page
A page tells search engines to hide it from results.
robots.txt blocking resources
The site blocks the files needed to render its own pages.
Questions
Related
robots.txt errors
Four lines of text that can remove a whole website from search.
Canonical errors
Check the tag, understand what it is claiming, then make it say what you mean.
Crawl the site and list every page currently telling Google to ignore it
The free audit crawls the site, groups every finding, and returns the five things worth fixing this month in plain English. No card, no call.
Run a free audit