“Excluded by ‘noindex’ tag”: what it means and how to fix it
The page carries a noindex instruction, either a meta robots tag in the HTML or an X-Robots-Tag HTTP header. Google crawled it and left it out of search on purpose. If you meant that, there's nothing to do. If it's a page you want in search, something on your site added noindex.
- Google is following your instruction, not making an error.
- Fine for thank-you pages, tag archives and private pages.
- If real posts are listed, find what adds the noindex: a setting, a template or a server header.
What does Google say?
When Google tried to index the page, it found a noindex directive and didn't index it. If you don't want the page indexed, Google says you've done so correctly.
Paraphrased from Google's Page indexing report help.
Why does it happen?
- 01An SEO plugin or CMS setting on the page, or for all tag and category archives.
- 02A site-wide 'hide from search engines' option left on after launch.
- 03A layout or template in your framework that sets robots to noindex.
- 04A server or CDN rule that adds an X-Robots-Tag: noindex header.
- 05A staging or preview environment's settings copied to production.
Is “Excluded by noindex” a problem?
It depends on which URLs Search Console lists. Check them against these two lists.
Ignore it if
- The page is one you chose to keep out of search.
Fix it if
- Posts or landing pages you want ranking are listed.
- The count jumped after a deploy or a settings change.
How do I fix “Excluded by noindex”?
Check any single URL with URL Inspection. After fixing, open the issue in the Page indexing report and click Validate fix; Google says it typically takes up to about two weeks.
# after a real changeInspect URL → Request indexing # in the Page indexing reportOpen the status → Validate fix
- 1
Find the noindex
View the page source and search for 'noindex'. Look for <meta name="robots" content="noindex">. If it's not in the HTML, check the response headers for X-Robots-Tag.
- 2
Find what adds it
Check page-level SEO settings, site-wide visibility settings, your layout's metadata, and server or CDN header rules.
- 3
Remove it and test live
Fix the source, then run a live test in URL Inspection and confirm it reports indexing as allowed.
- 4
Request indexing
Click Request indexing for your most important pages, then Validate fix in the Page indexing report.
- 5
Don't block it in robots.txt too
If robots.txt blocks the page, Google can't see the noindex or its removal. Keep crawling allowed.
How does Blogizi handle “Excluded by noindex”?
Published Blogizi posts don't carry a noindex tag, and drafts aren't public at all. The only switch that adds noindex is 'Hide blog from search engines' in project settings, which applies to the whole blog. If your posts show up here, check that setting first.
Index checks for every post are part of Pro, $19/month with a 7-day trial for $0. Your AI agent can read the same statuses over MCP.
Search › IndexingChecked dailyFrequently asked questions
View source and search for 'noindex', or run URL Inspection. It tells you if indexing is allowed and why not.
Last reviewed October 23, 2026 against Google's Page indexing report help.
Related Search Console statuses
Blocked by robots.txt
Your robots.txt file tells Google not to crawl this URL.
Read the guide →Check itCrawled - currently not indexed
Google read the page and decided not to index it, for now.
Read the guide →Usually finePage with redirect
The URL redirects somewhere else, so Google indexes the destination.
Read the guide →Get every post indexed
Publish on your own domain with sitemaps and canonicals handled, and see which posts Google hasn't indexed without opening Search Console.
Ready to get started?
Your agents write. Blogizi publishes. Google sends the traffic to your domain.
