Free noindex checker: see if Google and AI search can index your page.
Updated
This noindex checker reads every robots meta tag on one page and tests the page against your robots.txt for Googlebot, Bingbot and three AI search bots. You see in seconds whether anything keeps the page out of search, and out of the AI answers built on it.
Use it when a page won't show up in Google, after a launch or a migration, or before you ask Google to index something new. Free, with no signup and no email.
- Free
- No signup
- Results in about 15 seconds
- robotsNOINDEX, NOFOLLOW
- PerplexityBotBLOCKED
- GooglebotALLOWED
What the noindex checker reads on your page
Every rule that can keep one page out of an index, read the way the engines read it.
Status and redirects
Where the address lands and the code it answers with, so a redirect to a dead or hidden page never reads as clean.
Every robots meta tag
The general robots tag, Google's googlebot and googlebot-news, Bing's bingbot, and any tag that names an AI bot such as GPTBot. This is the meta robots checker part.
Each directive on its own
noindex, none and unavailable_after with its date decide indexing; nosnippet, max-snippet:0 and noai are judged too. Others, like nofollow, are listed as found.
robots.txt for five bots
Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot and PerplexityBot, each tested on this page's path with Google's matching rules.
The trap between the two
A page that says noindex but is blocked in robots.txt. Google never reads the tag, so it can still list the address.
Snippet rules for AI answers
nosnippet and max-snippet:0, which Google says keep a page's text out of AI Overviews and AI Mode.
A canonical that points away
Flagged as a note, because then another page is the one asking to be indexed.
From a page address to a clear verdict in five steps.
- 01
Enter a page
Any public page: a product page, a post, a landing page.
- 02
We fetch it as served
Following redirects, and noting where it lands.
- 03
We read its robots tags
Every meta tag a search or AI bot obeys, directive by directive.
- 04
We test robots.txt
For Google, Bing and three AI search bots, on this exact path.
- 05
You get the verdict
Indexable or not, why, and the line to change.
Why one noindex tag can keep you out of AI Overviews
Google says a page must be indexed, and allowed a snippet, to be shown as a link in AI Overviews or AI Mode. There are no other technical rules. So a single noindex left over from staging removes a page from Google's results and from its AI answers in one go.
The opposite mistake is just as common. Blocking a page in robots.txt doesn't remove it from Google: Google can't fetch it, so it never sees a noindex on it, and may still list the bare address.
For SEO this is the first check on any page that won't rank. For AEO it decides whether Google's answers can cite the page at all. For GEO, the AI search bots behind ChatGPT, Claude and Perplexity document robots.txt as their control, which is why we test their access too.
Reading your noindex check, verdict by verdict
The verdict at the top is Google's view of the page: what its robots meta tags and your robots.txt allow. When two rules disagree, Google applies the stricter one, and so do we.
Each check under it is passed, failed, worth a look or not checked. We mark a check as not checked when we couldn't see it, like the X-Robots-Tag header, rather than guess.
A clean result means nothing on the page or in robots.txt stops indexing. Google still decides what it indexes, and Search Console's URL Inspection shows its answer for your own sites.
| VERDICT | WHAT IT MEANS |
|---|---|
| Indexable | Nothing blocks it. No noindex and no robots.txt block. Google may index it, and nothing here stops AI Overviews from linking it. |
| Noindex | Kept out on purpose, or by mistake. A robots meta tag asks to keep the page out. Remove it if the page should rank. |
| Blocked | Google can't fetch it. robots.txt keeps Googlebot away. The address can still be listed, without a description. |
| Hidden | Two rules cancel out. noindex plus a robots.txt block: Google never sees the tag. Lift the block so it can. |
| Error | The page didn't load. A 4xx or 5xx code. Nothing is indexed until the page answers. |
How to remove a noindex you didn't mean to set
The tag came from your CMS:
look for a "discourage search engines" setting, and the per page indexing switch in your SEO plugin, before you edit the theme.
robots.txt hides the noindex:
remove the Disallow first, so Google can fetch the page and read the tag. To hide a page, use noindex and leave it crawlable.
The header says noindex:
an X-Robots-Tag set by the server or a CDN rule. Run the curl line from your report, then remove the rule in the server or CDN config.
It's fixed, but still missing:
Google has to crawl the page again. Ask for it with URL Inspection in Search Console, then give it time.
Find the tag in your page's head, or the header in your server config, and delete it:
<!-- In the page's <head> -->
<meta name="robots" content="noindex, nofollow">
# Apache (.htaccess)
Header set X-Robots-Tag "noindex"
# NGINX
add_header X-Robots-Tag "noindex";When to run a noindex check.
- Right after a launch: staging sites are often noindexed, and the tag can ship with the new site.
- After a migration: make sure old addresses redirect to pages that can be indexed, not to a hidden template.
- When a page never shows in AI Overviews: rule out a noindex or a nosnippet before you rewrite anything.
- When you hid a page on purpose: confirm robots.txt doesn't block it, or Google never reads your noindex.
- Before a client call: agencies check a prospect's money pages for a tag that quietly hides them.
One page at a time is slow. Zivooo checks them all.
Site Health checks every page of your site each month for noindex, robots.txt blocks and the rest of AI readiness, on your own keys, with the fix for each problem. $10 a domain a month after 7 days free, no card.
- Every page checked for noindex, every month
- robots.txt tested for AI search bots on each audit
- Track whether ChatGPT, Gemini and Google name you
- Send each client a branded report
A free noindex checker vs Search Console and browser extensions
Search Console's URL Inspection is the final word for Google, and it shows the response headers, but only for sites you've verified. A browser extension reads the headers of the page you have open, one page at a time. Site crawlers check every page, after you install and run them. This checker works on any public page with no install, and puts the robots meta tags, robots.txt and the AI search bots in one view. Two limits: it runs no JavaScript, and it doesn't read the X-Robots-Tag header. For an x-robots-tag check, use the curl line under your result.
Noindex, answered.
How do I check if a page is noindex?
Run it through this checker, or open the page's source and search for name="robots". The tag can also come as an X-Robots-Tag header, which curl -I shows. For your own site, Search Console's URL Inspection tells you whether Google may index the page.
What is the difference between noindex and disallow in robots.txt?
noindex lets Google fetch the page and tells it not to list it. Disallow stops the fetch, so Google never reads the page, and the bare address can still be listed if other sites link to it. To keep a page out, use noindex and don't block it.
Can Google index a page blocked by robots.txt?
Yes, as a bare address. Google says a blocked URL can still appear in results, without a description, when other pages link to it. robots.txt manages crawling; noindex manages indexing.
What is the X-Robots-Tag, and how do I check it?
It's the same rule as the robots meta tag, sent as an HTTP header, which also works for PDFs and images. Our fetch doesn't return headers, so run curl -sIL with the page address and look for x-robots-tag in the output.
Can a noindex page appear in AI Overviews?
Not as a link. Google says a page must be indexed and allowed a snippet to be a supporting link in AI Overviews or AI Mode. A nosnippet rule keeps its text out of those answers too.
Why is my page still not indexed after I removed noindex?
Google has to crawl it again before it sees the change. Check robots.txt doesn't block it, then request indexing in Search Console. Indexing is Google's decision, so a clean page can still take a while.
Does Google see a noindex tag added by JavaScript?
It may not. Google says that when it finds noindex in the page's code it may skip rendering, so a script that removes the tag may never run. If you want a page indexed, keep noindex out of the original HTML.
What is the difference between noindex and nofollow?
noindex keeps the page out of the index. nofollow tells search engines not to follow the links on the page. none means both at once.
Check the rest of the page.
- AI READINESS & TECHNICALSEOCanonical Tag CheckerSee which URL a page asks Google to index, and if that page works.Check my canonical
- AI READINESS & TECHNICALSEOGEORobots.txt CheckerValidate your robots.txt line by line and test any bot on any path.Check my robots.txt
- AI READINESS & TECHNICALSEORedirect CheckerSee where an address and its http, https and www versions end up.Check my redirects
- AI READINESS & TECHNICALAEOGEOSEOAI Readiness CheckerSee if AI search bots can reach, read and quote a page.Check my AI readiness
Find every hidden page, then get cited.
Your keys, your costs, $10 a domain. 7 days free, no card.