Excluded by ‘noindex’ Tag: What It Means and How to Fix It
Short answer: Google crawled the page, found a noindex rule, and left the page out of search, as the rule asked. If you don’t want the page in Google, do nothing. If you do, find where the noindex comes from (a meta tag, an HTTP header, or a CMS or plugin setting), remove it, and ask Google to crawl the page again.
What the status means
Search Console lists it in the Page indexing report (Indexing → Pages) as a reason pages are not indexed. Google’s help describes it under the name “URL marked ‘noindex’”: “When Google tried to index the page it encountered a ‘noindex’ directive and therefore did not index it.”
Unlike a robots.txt block, the page was crawled. Google read it, saw the rule, and followed it. Nothing is broken on Google’s side, so this is a setting to check, not a crawl problem to debug.
Step 1: decide if the page should be indexed
Open the status and go through the example URLs. Noindex is the right choice for pages that must exist but shouldn’t show up in search: login and account pages, cart and checkout, thank-you pages, internal search results. Leave those alone.
Act on pages that should bring visitors: articles, product and category pages, your home page. One quick sign of a mistake is a noindexed URL in your XML sitemap. The sitemap says “index this”, the page says “don’t”.
Step 2: find where the noindex comes from
Run URL Inspection on one URL and open the page indexing details. It confirms noindex was detected and whether it came from the robots meta tag or the X-Robots-Tag header. Then look in these places:
A meta tag in the HTML
<meta name="robots" content="noindex"> <meta name="googlebot" content="noindex">
View the page source (not the browser’s element inspector, which shows the page after scripts ran) and search for noindex.
An HTTP header
Servers, CDNs and some plugins send noindex as a header. It never shows in the source, so check the response:
curl -sI https://example.com/page | grep -i x-robots-tag # x-robots-tag: noindex <- this is the cause
WordPress settings
- Settings → Reading → “Discourage search engines from indexing this site”. Since WordPress 5.3 this adds a noindex meta tag to every page. It is often left on after launch.
- Yoast SEO: in the post’s Yoast box, open the Advanced tab. “Allow search engines to show this content in search results?” must not be set to No. The default for each content type is set in Yoast’s settings.
- Rank Math: open the post’s Rank Math panel, go to the Advanced tab, and check that Robots Meta is set to Index. Site-wide defaults live under Titles & Meta.
Leftovers from staging
A site built with a blanket noindex on staging can keep it after go-live, through an environment variable, a header rule on the host, or a template condition. If a whole section or the whole site is excluded, check this first.
Step 3: remove it the right way
- Remove the tag or header on the server (or change the CMS setting). Google says that if it finds noindex in the original HTML it may skip rendering, so removing the tag with JavaScript is not reliable.
- Make sure the page can be crawled. If robots.txt blocks it, Google can’t see that the noindex is gone. See Blocked by robots.txt.
- Clear caches (page cache, CDN) so Google gets the new version.
- Run a live test in URL Inspection. Google’s help says to confirm the fix this way. When it shows the page as indexable, click Request indexing.
For many URLs at once, fix the cause, then click Validate fix in the report. Google says validation usually takes up to about two weeks and sometimes much longer.
If the page then lands in Crawled – currently not indexed, the noindex is gone and Google is now judging the page itself. That is a content question, not a tag question.
Using noindex on purpose
Noindex keeps a page out of search but leaves it working for visitors. Use the meta tag or the header, keep the page crawlable, and don’t list it in your sitemap. Robots.txt is the wrong tool for this job: it stops crawling, so Google never sees the noindex. Our noindex tag guide and X-Robots-Tag guide show both methods in full.
To check a batch of pages, the free meta tag checker checks 30 URLs from your sitemap and flags any with noindex in a robots or googlebot meta tag or in the X-Robots-Tag HTTP header.
Frequently asked questions
Is "Excluded by 'noindex' tag" an error?
Only if you want the page in Google. Google did what the page asked. For pages like login, cart or thank-you pages, it is the right result and needs no action.
I removed the noindex. Why is the page still excluded?
Google has to crawl the page again to see the change. Run a live test in URL Inspection, then click Request indexing. The report updates after the next crawl.
Can noindex come from somewhere other than the HTML?
Yes. A server, CDN or plugin can send it as an X-Robots-Tag HTTP header. It does not show in the page source, so check the response headers.
Does removing noindex with JavaScript work?
Not reliably. Google says that when it finds noindex in the original HTML, it may skip rendering, so a script that removes the tag never runs. Remove it on the server.
What if the page is also blocked by robots.txt?
Then Google cannot crawl it and cannot see that you removed the noindex. Unblock the page in robots.txt first.