Free SEO Tool · No Signup Required

Free Noindex Checker

A noindex checker for one URL. It reads the page's served HTML and tells you whether a robots or googlebot meta tag asks search engines to leave the page out of their index. It does not read the X-Robots-Tag header, and the card says so and hands you the command to check it yourself.

No signup, no email
Same result every run
robots and googlebot tags
Reads the whole document
Any public URL
Free, no daily cap

What we checked

1 check, one URL. One GET of the page as VerandBot/1.0, redirects followed, 12 second timeout. Every <meta> tag whose name is robots or googlebot is read, anywhere in the served document and however long it is, and the check fails when its content contains the word noindex.

How the verdict is read

A noindex found is a fail, flagged for review: it is right on a thank-you or campaign page and wrong on a page you want found, and only you know which this is. No noindex is a pass for the meta tag only. The header row always reads not read, because it is.

What it cannot see

The X-Robots-Tag HTTP header is not read, so a noindex sent that way reports as a pass; run the command on the card, or open DevTools, Network, the page request, Response Headers. Also unseen: content="none", tags for other crawlers such as bingbot, unquoted attributes, a noindex added by JavaScript, and a robots.txt block that stops Google reading the tag. A PDF or other non-HTML file has no HTML to read, and a page that answers 4xx or 5xx is refused, not read. Whether Google has the page indexed is in Search Console, not here.

About this tool

How the Noindex Checker reads your page.

One fetch, every meta tag, one word to look for, and an honest line about the header it cannot see. The card is the tool in motion on an example page, looped, and each step lights up while the card is doing it.

Noindex Checker

Example page

example.com/services/

Check

<head>

<title>Services | Example</title>

<meta name="robots"

content="noindex, follow">

</head>

HTML read, 18,406 bytesPass

robots meta: noindexFail

X-Robots-Tag headerNot read

Check the header in a terminalCopy

curl -sI https://example.com/services/ | grep -i x-robots-tag

Set to noindex1 pass · 1 fail · 1 not read

One request for the page

The tool fetches the URL you typed as VerandBot, following redirects, giving up after twelve seconds. A page that answers with an error is refused rather than read, because a noindex on a 404 changes nothing.

Every meta tag is scanned

The whole served document is walked tag by tag, not just the first screenful, and every <meta> whose name is robots or googlebot is kept. No JavaScript runs, so this is the markup a crawler sees on its first read.

One word decides it

If any of those tags carries noindex in its content, alone or beside follow or nofollow, the check fails. The verdict asks whether it was meant, because on a thank-you page it usually was.

The header is yours to check

A server can send the same instruction as an X-Robots-Tag response header, which this tool does not read. The card marks that row not read and gives you the one command that shows it.

noindex, explained

What a noindex meta tag does, and why a stray noindex tag goes unnoticed.

Noindex is the one line that takes a working, linked, fast page out of Google entirely. Here is where it can live, how it differs from nofollow and a robots.txt Disallow, how it ends up on pages nobody meant to hide, and what it does not do.

What noindex is

Noindex is an instruction to search engines: you may fetch this page, but do not keep it in your index and do not show it in results. It is the opposite of a block. The crawler has to be allowed in, read the page, find the instruction and act on it. Google drops a noindexed URL from its results the next time it crawls the page and sees the rule, and keeps it out for as long as the rule is there.

There are exactly two places the instruction can live. The first is a meta tag in the page's HTML, which is what this checker reads:

<!-- every crawler that honours robots meta tags -->
<meta name="robots" content="noindex">

<!-- Google only -->
<meta name="googlebot" content="noindex">

The second is an HTTP response header, sent by the server before any HTML at all. It is the only way to noindex a PDF, an image or any other file that has no <head> to put a tag in, and it is often set in a CDN rule, a server config or a framework's middleware rather than in the page template:

HTTP/1.1 200 OK
Content-Type: application/pdf
X-Robots-Tag: noindex

This checker reads the meta tag and not the header. If a page's HTML is clean and its server sends X-Robots-Tag: noindex, the card will say no noindex was found in the tag, mark the header row not read, and give you the command below. Run it on any page that is missing from Google and passes here.

curl -sI https://yourdomain.com/page/ | grep -i x-robots-tag

No output means no header. In a browser, the same answer is in DevTools: the Network tab, reload, click the page's own request, then Response Headers.

Reading the tag: names, values and conflicts

The name says which crawler the tag speaks to. robots means every crawler that supports the convention; googlebot means Google alone, and other search engines use their own names, such as bingbot. This checker reads the two that matter for Google, robots and googlebot, and ignores the rest. Google treats both the name and the value as case-insensitive, and when rules conflict, the more restrictive one wins, so one noindex anywhere beats any number of index values.

The content is a comma-separated list. index and follow are the defaults and do nothing when written out. none is shorthand Google defines as equivalent to noindex, nofollow, and it is worth knowing because this checker looks for the word noindex and does not treat none as a match. If your template writes content="none", read it as a noindex even though the card passes it.

Noindex, nofollow and Disallow are three different instructions

They are routinely used as if they were interchangeable, and the mix-ups are where most indexing accidents come from.

Instruction	Where it lives	What it does
noindex	meta tag or X-Robots-Tag header	The page may be crawled but not kept in the index or shown in results.
nofollow	meta tag, header, or a link's rel attribute	Asks the crawler not to follow the page's links. It does nothing to the page's own place in the index.
noindex, nofollow	meta tag or header	Both at once: out of the index, and its links not followed. Common on thank-you and confirmation pages.
Disallow	robots.txt	The crawler should not request the URL at all. It controls crawling, not indexing, and a disallowed URL can still appear in results, with no snippet, if other pages link to it.

The dangerous combination is Disallow plus noindex on the same URL. Google's documentation is direct about it: if robots.txt blocks the page, the crawler never sees the noindex, and the page can still appear in search results. To take a page out of the index, leave it crawlable and noindex it; once it has dropped out, you can decide whether to block it too. Writing noindex inside robots.txt itself does nothing for Google, which stopped supporting that line in 2019.

The noindex that nobody meant to add

Most noindex problems are not decisions. They are leftovers, and they arrive in a handful of predictable ways:

A staging setting that shipped. A new site is built on a staging copy with search engines told to stay away, which is correct, and then the copy becomes production with the setting still on. WordPress has this as a single checkbox, "Discourage search engines from indexing this site" under Settings, Reading, and when it is ticked WordPress adds a robots noindex tag to every page. One box, the whole site.
A plugin or theme default. SEO plugins let you noindex whole content types, archives or taxonomies in one switch. A switch meant for tag archives, flipped for the wrong type, takes every service page with it.
A migrated template. A redesign copies the head from the confirmation page template into the page template, and the noindex travels with it.
A header nobody can see. A CDN or hosting rule written to hide a preview domain matches the live domain as well. Nothing in the HTML changes, which is why an HTML-only check, this one included, passes it.

The symptom is always the same and always slow: the page stops appearing, traffic to it fades over the next crawls, and nothing in the site's own analytics says why. After any rebuild, check the pages that earn enquiries first: the home page, each service or practice-area page, and the pages your best-performing searches land on. Search Console's Page indexing report lists every URL Google has excluded because of a noindex, under the reason "Excluded by 'noindex' tag", and it is the fastest way to see the whole site at once.

Removing a noindex, and why the page does not come back at once

Take the noindex out at its source: the CMS setting, the plugin's per-page or per-type option, the template, or the server rule if it is a header. Then check the served page again, here for the tag and with the command above for the header, because a cached copy or a second rule is a common reason a fix does not take. Google only learns the rule is gone when it recrawls the page, so a page can stay out of results for days or weeks after the fix. In Search Console, URL Inspection shows what Google saw on its last crawl, and a request for indexing asks it to look again. Resubmitting the sitemap helps on a large site where many pages were affected.

One trap on JavaScript sites: if the served HTML carries a noindex and a script removes it after load, Google may never run the script. Its JavaScript guidance says that when it encounters a noindex it may skip rendering, so a noindex removed client-side may not be removed at all. If a page should be indexed, the noindex must not be in the original HTML, which is exactly what this checker reads.

Noindex is not privacy

This is the misunderstanding that matters most to a firm whose website is a regulated communication. A noindexed page is still on the public web. Anyone with the link can open it, it can be forwarded, bookmarked and archived, and other crawlers that do not honour the tag, or honour it differently, can still fetch it; Google's own documentation notes that some search engines may interpret noindex differently. Firms noindex thank-you pages, landing pages built for a paid campaign, and old rate, fee or performance pages, sometimes on the belief that noindex takes them out of circulation. It takes them out of Google's results. It does not unpublish them, and a page that makes a claim is still making it to whoever lands there.

Willowdale Equity's own newsletter thank-you page is a clean example of noindex used correctly: its source carries noindex, nofollow, because a confirmation screen has no business in search results, and nothing on it needs to be hidden from anyone who has the link. That is the test. If a page should not be found in Google, noindex it. If it should not be read by anyone, take it down or put it behind a login; noindex was never built for that.

Noindex and AI answers

For Google, the relationship is simple. Google says a page must be indexed and eligible to show with a snippet to appear in AI Overviews or AI Mode, so a noindexed page is out of Google's AI answers along with its ordinary results. If you want a page in Search but want to limit what AI features quote, the finer controls are the snippet rules, nosnippet and max-snippet, not noindex.

Other assistants are a different mechanism. ChatGPT, Claude and Perplexity reach sites through their own named crawlers, and those crawlers are governed first by the robots.txt rules for their user agents. Noindex is a search-indexing instruction; whether an assistant's crawler honours it is each operator's own policy, so do not rely on it to keep a page out of AI answers outside Google. To decide which AI crawlers may read the site, the robots.txt is the file to look at, and the Robots.txt Checker and the AI Crawler Access Checker below read it by name.

Why this one

Why choose Verand's Noindex Checker?

Six things that are true of this tool, each one backed by a line in the code that runs it.

No signup, no email wall

The request carries a URL and nothing else. There is no account, no session and no database behind the tool, so there is nothing for us to keep about you.

Reads the whole document

Some of the product's checks read only the first 100,000 characters of a page. The noindex scan reads every character of the served HTML, so a tag late in a very long page is still found.

Deterministic

The tag is found by a fixed pattern over the served markup. No model reads the page, so the same page gives the same answer every time.

The product's own check

This is the noindex check Verand's deep crawl runs on every page of every customer site every two weeks, where it is filed at the highest severity. Called directly, not a lighter demo.

Names what it cannot see

The header it does not read is a row on the card marked not read, never a quiet pass, with the command to check it yourself beside it.

$0, no daily cap

Each run is one page fetch, so it costs nothing and is never metered. The one limit is a courtesy to the sites being fetched: 20 checks a minute per visitor.

Questions

Frequently Asked Questions About the Noindex Checker

Noindex against nofollow and Disallow, getting a page back, and what the tag does not do.

What is the difference between noindex, nofollow, and disallow?

Noindex tells a search engine it may crawl the page but must not keep it in the index or show it in results. Nofollow asks it not to follow the page's links, and does nothing to the page's own place in the index; noindex, nofollow does both. Disallow is a robots.txt rule that tells the crawler not to request the URL at all, which controls crawling rather than indexing. That difference is why the two should not be combined: a disallowed page is never fetched, so its noindex is never seen, and Google says such a page can still appear in results.

Why is my page not indexed after I removed the noindex tag?

Usually because Google has not recrawled it yet, since it only learns the rule is gone on its next visit. Check three things first. Run this checker on the live URL, because a cached copy or a second template can still be serving the tag. Check the X-Robots-Tag header, which this tool does not read, with curl -sI and the URL, or in your browser's DevTools. And if the site relies on JavaScript to remove the tag, move the fix into the served HTML, because Google may skip rendering a page whose original HTML says noindex. Then use URL Inspection in Search Console to request indexing.

Should you remove the noindex pages from the sitemap?

Yes, once they have dropped out. A sitemap is the list of URLs you want indexed, so a noindexed URL in it sends Google two opposite instructions, and Search Console reports the conflict. The exception is the short window after you add a noindex to pages that are already indexed: keeping them listed for a short while is a common way to prompt the recrawl that lets Google see the new rule. After that, take them out.

Should staging sites use noindex or password protection?

Password protection, or an IP allowlist. Noindex only asks search engines not to list the site; the site stays publicly reachable by anyone with the address and by any crawler that ignores the rule. A login stops everyone, and it cannot ship to production by accident the way a noindex setting can, which is the most common way live sites end up hidden. If you use noindex on staging as a second layer, add it to your launch checklist to remove.

Can a noindex be set in the HTTP header instead of the page?

Yes. The server can send X-Robots-Tag: noindex as a response header, and Google treats it the same as the meta tag. It is the only way to noindex a PDF, an image or another file with no HTML head. This checker does not read headers, so a page noindexed that way will pass here. To check, run curl -sI followed by the URL and look for an x-robots-tag line, or open DevTools, the Network tab, the page's request and its Response Headers.

Does noindex keep a page out of AI answers?

Out of Google's, yes: Google says a page must be indexed and eligible for a snippet to appear in AI Overviews or AI Mode, so a noindexed page is not a candidate. For other assistants, such as ChatGPT, Claude and Perplexity, it is not something to rely on. They reach sites through their own crawlers, governed by the robots.txt rules for their user agents, and whether each one honours noindex is that operator's policy. It also does not make the page private: anyone with the link can still read it.

After the check

Stay in the index. Then give it something worth citing.

A page without a stray noindex is only eligible to be found. Verand writes articles from your own expertise and credentials, so Google and the AI assistants have something of yours worth naming. It then tracks where you rank and where ChatGPT, Gemini, Perplexity, Claude and Google's AI answers mention you, re-checks every page on each crawl, and gates every draft so a claim your regulator would not allow never publishes.

Start for free See pricing

services.htmlwriting

<head>  <title>Services | Your Firm</title>  <meta name="description"    content="What we do, and for whom.">  <link rel="canonical"    href="https://yourfirm.com/services/">  <!-- no noindex: this page is meant to be found --></head><!-- Written for your authority. --><!-- Found on Google and in AI answers. --><!-- Tracked where the answers name you, --><!-- and gated before it publishes. -->