Noindex Checker

Enter a URL to see whether Google is told not to index it, via a<meta name="robots" content="noindex"> tag, an X-Robots-Tag: noindexHTTP header, or a robots.txt rule that stops Google from seeing either.

Public check, no account needed. Reads the X-Robots-Tag header, the robots and googlebot meta tags, and the robots.txt rule Googlebot follows for the URL. Counts as up to two of the 60 checks an hour per IP: one for the page, one for robots.txt. Checking many URLs? The bulk checker reads up to 20 in one request.

Worked example

Illustrative result for a reserved example URL. Your check replaces it.

Blocked by noindex in HTTP header

The response header says noindex. It does not appear in view-source, and a clean meta tag does not cancel it.

Evidence
X-Robots-Tag: noindex
X-Robots-Tag header
X-Robots-Tag: noindex
Meta robots
<meta name="robots" content="index, follow">
Googlebot meta
not found
robots.txt, Googlebot
Allowed for /pricing by line 2: Allow: /, in the User-agent: * group (line 1).
HTTP status
200

What does a noindex checker test?

Every place a URL can tell Google to stay out, from one fetch of the final response and one read of its robots.txt:

  • The X-Robots-Tag header. X-Robots-Tag: noindex applies to every crawler, X-Robots-Tag: googlebot: noindex to Google only. It never appears in view-source. The X-Robots-Tag checker shows every agent group on its own.
  • The robots meta tag. <meta name="robots" content="noindex">in the HTML. Google lists none as "Equivalent to noindex, nofollow", so the checker counts it too.
  • The googlebot meta tag. <meta name="googlebot" content="noindex">is Google's documented way to keep a page out of Google only.
  • robots.txt. It cannot carry a noindex, but a Disallow that matches the URL stops Googlebot fetching the page. Google: "If a page is disallowed from crawling through the robots.txt file, then any information about indexing or serving rules will not be found and will therefore be ignored."

The result names the one that decides, and the line it came from. Indexable means nothing tells Google to stay out; whether Google then indexes the page is its call. Theindexability checker adds the canonical and the redirect chain.

How common is it? In ourpass over all 16,935 registered .gov domains, 106 of 9,078 reachable homepages were public content pages telling search engines to stay out: 80 with a noindex, 22 behind a robots.txt rule that blocks Googlebot, and 4 with both, measured on 22 October 2026.

Why does a page show "Excluded by 'noindex' tag" in Search Console?

Google crawled the URL and found noindex in the robots meta tag or the X-Robots-Tag header, so it left the page out of Search. If you meant it, nothing needs doing. If not, run the URL above to see which of the two carries it, remove it at the source, and request indexing in URL Inspection. If the checker shows the page clean, the report is describing an older crawl. The full walkthrough is onExcluded by 'noindex' tag: the fix.

How does noindex get added by accident?

Almost always by a setting or a deploy, not by someone deciding to hide the page:

  • A deploy ships a staging setting. A robots tag or header driven by an environment variable is right on staging and wrong in production, and the release goes out with it. See accidentally noindexed your site.
  • WordPress. "Discourage search engines from indexing this site" under Settings, Reading writes a noindex meta tag into every page.WordPress noindex fix.
  • Webflow. Turning off Sitemap indexing in a page's SEO settings writes a noindex meta tag. Webflow noindex fix.
  • Wix. The "Let search engines index this page" toggle in SEO basics, or the site-wide setting that overrides it. Wix noindex fix.
  • Shopify. A noindex condition in theme.liquid, the seo.hidden metafield, or a store still behind its password page. Shopify noindex fix.
  • Squarespace. The "Hide page from search results" toggle, or a noindex left in code injection. Squarespace noindex fix.
  • The server or CDN. A rule adds X-Robots-Tag: noindex to a path or host, and no template shows it.

For why one stray tag costs so much, readwhat noindex is and why it silently kills traffic.

Noindex vs Disallow: which blocks what?

Noindex blocks indexing. Disallow blocks crawling. Google calls robots.txt "not a mechanism for keeping a web page out of Google", and a disallowed URL "can still appear in search results, but the search result won't have a description." Put both on one page and the Disallow hides the noindex, so the page can stay indexed. To remove a page, allow the crawl and serve noindex. To stop crawling, use Disallow and expect the URL to linger. More innoindex vs Disallow.

How do you check many URLs at once?

The bulk checker reads meta robots and the X-Robots-Tag header for up to 20 URLs in one request. The robots.txt testertests up to 100 URLs against Googlebot, Bingbot and AI crawlers. For a whole site, thesitemap audit samples up to 200 URLs from the sitemap and flags each one that says noindex or is blocked by robots.txt. If the site has dropped out of Google entirely, start with the deindex triage.

How do you get alerted when noindex appears?

Monitor the URL instead of re-running a check. The free plan watches 1 site with 1 URL checked once a day and alerts by email, with no card and no end date. Starter is $39 a month for 15 sites checked every 30 minutes. Agency is $79 a month for 50 sites checked every 15 minutes, with white-label client reports. robots.txt is read every hour on every plan. A new noindex is confirmed with a second fetch before the alert goes out. Every new account starts with a 30-day free trial, 3 sites, no card required. Plans are on thepricing page.

Want this checked every 30 minutes?

30-day free trial, 3 sites, no card required. We re-check the URLs you choose, confirm a critical change with a second fetch, then alert Telegram and email. Plans are on the pricing page, and if you are weighing us against a tool you already use, the Little Warden comparison prices both sides from published numbers.

Start the 30-day free trial, 3 sites, no card required

What this check means

Noindex
Noindex is a rule, set in a meta tag or an HTTP response header, that tells search engines which support it to leave a page out of their index.
X-Robots-Tag
X-Robots-Tag is an HTTP response header that carries the same rules as the robots meta tag, optionally scoped to one crawler such as googlebot.
robots.txt block
A robots.txt block is a Disallow rule that stops a crawler fetching a URL. It prevents crawling, not indexing, and it hides any noindex on the page.

How to read the result

Verdict
One line: Indexable, Blocked by noindex in HTTP header, Blocked by meta robots noindex, or robots.txt blocks Googlebot. A robots.txt block wins, because Google never reads the page behind it.
Evidence
The header line, meta tag or robots.txt rule that decided, as the server sent it, so you can search your config for it.
X-Robots-Tag header
Every header group on the final response. Only the unscoped group and the googlebot group change the verdict; groups for other crawlers are listed for reference.
robots.txt, Googlebot
Whether Googlebot may fetch the final URL, with the deciding line and group. A missing robots.txt means no restrictions; one that answers 5xx or 429 makes Google stop crawling.
HTTP status
The status of the final response. A page that answers 4xx or 5xx is reported as not indexable even with no noindex.

Common causes

  • A deploy ships a staging robots tag or header to production.
  • A CMS visibility setting is left on after launch.
  • An SEO plugin noindexes a whole content type or archive.
  • A server, CDN or proxy rule adds X-Robots-Tag: noindex.
  • A robots.txt Disallow hides a noindex, or blocks a page meant to be indexed.

How do I check if a page is noindexed?

Enter the URL in the checker above. It fetches the page, reads the X-Robots-Tag response header and the robots and googlebot meta tags, then reads robots.txt to see whether Googlebot may fetch the URL at all, and shows the line that decided. By hand, search view-source for "noindex" and read the response headers in your browser’s developer tools: the header never appears in the source.

Can robots.txt noindex a page?

No. Google says "Specifying the noindex rule in the robots.txt file is not supported by Google." A Disallow rule stops crawling, not indexing: a disallowed URL "can still appear in search results, but the search result won't have a description." To keep a page out, let Google crawl it and serve noindex in the robots meta tag or the X-Robots-Tag header.

Noindex vs disallow: which keeps a URL out of Google

How long does it take Google to drop a noindexed page?

Until Googlebot crawls it again. Google drops the page from Search results when it crawls the page and extracts the noindex, and says that "depending on the importance of the page on the internet, it may take months for Googlebot to revisit a page." The URL Inspection tool in Search Console can request a recrawl. For an urgent removal, Google points to its removals documentation.

Does noindex in JavaScript work?

Adding one can; removing one is unreliable. Google documents adding a robots meta tag with JavaScript, but warns that "when Google encounters the noindex tag, it may skip rendering and JavaScript execution", so a script that removes or changes a noindex the server sent may never run for Googlebot. This checker reads the HTML the server returns, before any script runs, so a noindex added only by script will not show here.

Noindex and JavaScript in Google: what actually works

Google documentation behind each verdict

Read on .