Short answer: Google crawled the page, found an instruction telling it not to index the page, and obeyed. The instruction is a noindex directive, sent either in a <meta name="robots"> tag in the page's HTML or in an X-Robots-Tag HTTP header. If you want the page in Google, remove the directive, then ask Google to recrawl it.
Is it a problem?
Only if you want that page in search. (Google's help page for the Page indexing report lists the same reason as "URL marked 'noindex'"; the report itself shows "Excluded by 'noindex' tag".) Thank-you pages, login pages, internal search results and tag archives are often noindexed on purpose, and Search Console lists them under this reason too. It becomes a problem when the list contains pages that should rank: the homepage, service pages, product pages or blog posts.
The four usual causes
| Cause | Where the noindex comes from | How common |
|---|---|---|
| WordPress "Discourage search engines from indexing this site" left on after launch | A noindex,nofollow robots meta tag WordPress adds to every page (since WordPress 5.3; older versions wrote a robots.txt Disallow instead) | Very common after a new build or a migration |
| An SEO plugin setting (Yoast, Rank Math, All in One SEO) | A robots meta tag on one page, one post type or one taxonomy | Common, often set by mistake on a whole post type |
| Staging settings copied to the live site | A meta tag or a server rule from the staging copy | Common during migrations and redesigns |
| A server, hosting or CDN rule | An X-Robots-Tag: noindex response header | Less common, and the hardest to spot because it never shows in the CMS |
How to find which one it is
The fastest way is the free noindex checker: paste the URL and it names the meta tag, the googlebot tag, the X-Robots-Tag header or a redirect hop, with the exact line. To do it by hand:
- URL Inspection in Search Console. Paste the URL, open "Page indexing" and look at "Indexing allowed?". Run "Test live URL" to see the page as it is now, not as Google last saw it. When the answer is No, the result normally names where the directive was found: the robots meta tag or the X-Robots-Tag header.
- Check the HTML. Open the page, view the source and search for
noindex. A line like<meta name="robots" content="noindex">means it comes from the page, usually WordPress or an SEO plugin. - Check the headers. If the HTML is clean, the directive is in the response headers. Run
curl -I https://example.com/pageand look forX-Robots-Tag. That one comes from the server, the host or a CDN rule, not the CMS.
How to fix it
- WordPress setting: Settings → Reading → untick "Discourage search engines from indexing this site", then save.
- SEO plugin: open the page's SEO settings and allow it in search results. Then check the plugin's search appearance settings for the post type or taxonomy, because that setting is the default for every page of that type.
- Header: remove the
X-Robots-Tag: noindexrule from the server config,.htaccess, hosting panel or CDN rules. - Then tell Google: in URL Inspection, run the live test, confirm "Indexing allowed? Yes", and click "Request indexing". For many pages, open the Page indexing report and click "Validate fix" on this reason.
One trap: Google can only see that the noindex is gone if it is allowed to crawl the page. If robots.txt also blocks the URL, Google never re-reads it. Make sure robots.txt does not disallow the page you just fixed.
How long until the page comes back?
Google has to recrawl the page first. "Request indexing" asks for that recrawl sooner for a single page, with a daily limit on requests, and Google says validating a whole report typically takes up to about two weeks, sometimes longer. Rankings that were lost while the page was out of the index do not always come straight back, which is why catching a noindex on the day it appears matters more than fixing it later.
Catching it before Google does
Most noindex accidents happen during a launch, a redesign or a plugin update, and nobody notices until traffic drops weeks later. quietwatch checks each site you add every day for a noindex in the meta tag or the X-Robots-Tag header, robots.txt rules that block Googlebot, and Cloudflare settings that refuse crawlers, and emails you when something changes. You can check any page for free right now.