Free tool · no signup · runs now

Noindex checker

Search Console marks the URL “Excluded by ‘noindex’ tag” for one of two reasons: the directive sits in the meta robots tag or in the X-Robots-Tag header. This check reads both — the header cause is invisible to page-source tools that only look at HTML.

Part of the Technical SEO audit & onpage SEO audit group — also included in the free full scan.

Checks this exact page only — it does not crawl the rest of your domain.

Free scan · 3 a day without an account · anonymous preview · sign in to save the full report

Sample resultNo noindex directive (meta robots: none; X-Robots-Tag: none)Static example for Noindex checker; run the check above for your own result.

What it checks

See which directive — meta robots or the X-Robots-Tag header — excludes the URL from the index.

Meta robots tag content and the X-Robots-Tag response header; noindex and nofollow are both reported with the raw value that carried them.

Reads the no-JS response only, never runs JS. Follows up to 5 redirects.

How this check works — what it verifies, what a failure looks like, and how to fix it.

What good looks like

Good looks like neither source carrying noindex — the page is eligible for indexing, subject to robots.txt, the canonical and quality signals. A found directive reports as warn, not fail: noindex is exactly right for pages you deliberately keep out of search, and a fault only when the page should rank. A nofollow directive is reported the same way — indexing still works, but links from the page pass no equity.

Quick fix

Remove noindex from the meta robots tag or the X-Robots-Tag header when the page should rank; keep it when the exclusion is intended.

Noindex checker: the two places the directive lives

A noindex directive reaches crawlers through two channels. The meta robots tag — <meta name="robots" content="noindex"> — sits in the page head and is per-page. The X-Robots-Tag response header does the same job at the HTTP layer, and it is the one you miss when you view source: edge workers, CDNs and hosting panels often inject it without any tag in the HTML. Search Console’s “Excluded by ‘noindex’ tag” status does not name the channel, so check both before editing anything.

Check the indexability signals around it

noindex vs robots.txt vs canonical

Three mechanisms keep a URL out of search results, and they fail differently. robots.txt blocks the crawl — the crawler never fetches the page, so it cannot read a noindex tag you placed there; blocked pages can even appear as bare results learned from links. A canonical points the URL’s signals at another address. Only noindex removes the page from the index while leaving it crawlable. Allow crawling, serve noindex, and keep the canonical self-referencing.

Test robots.txt directivesVerify the canonical self-reference

How to remove a noindex directive

Start where the check found it. A meta robots tag usually comes from a CMS setting or an SEO plugin’s page-level switch; an X-Robots-Tag header usually comes from a hosting panel, a CDN rule or an edge worker. Remove the directive, redeploy, then run the check again — the header and the tag must both be gone. Search engines pick the change up on their next crawl; you can request a recrawl for priority URLs from Search Console’s URL Inspection, but scheduling stays with Google.

Read the Search Console indexing guide

What the full scan adds

  • All 35 checks in one pass — one URL, every category, a single report.
  • Evidence on every row: the values found, why it fails, the fix, and a deep link per check.
  • Your score against the global distribution — see where you stand.
  • Sign in and the report is kept for 1 year; anonymous reports expire after 7 days.

Official source: Search Central, block indexing with noindex · Rule: metrics-noindex v1 · check explainers

Tracking a Google update? Run the update impact check or read the search update radar.

Frequently asked questions

Is the Noindex checker free?

Yes — free without an account. Check runs are rate-limited per day per IP and the verdict shows immediately; it is not stored. Sign in to run full site scans and keep those reports.

How often should I run it?

After every deploy that touches routing, templates or the checked file — and after each Google core update, to confirm nothing regressed.

Does the check run JavaScript?

No — it reads the no-JS response only, exactly what a crawler or AI agent sees when it fetches the URL.

How is this different from a full audit?

This page runs one check with its full criteria and fix notes. The free full scan runs every category at once and keeps the evidence per URL — use it once you know which checks matter.

Why does Search Console say “Excluded by ‘noindex’ tag”?

Google fetched the URL, read a noindex directive and dropped the page from the index. The status names the cause, not the channel — the directive may be in the meta robots tag or the X-Robots-Tag header. Remove it where this check found it, then request indexing for the URL in Search Console.

How long does removing noindex take?

Until the next recrawl of the URL — Google decides the schedule. Request indexing from URL Inspection for the priority pages, keep the sitemap current, and the page re-enters the index when Google refetches and sees the directive is gone.

Does this checker read Google’s live index?

No. It reports the directives on the URL itself — the meta robots tag and the X-Robots-Tag header. Whether Google has already dropped or restored the page is a Search Console URL Inspection question.

Related tools

All free SEO tools

Visdenda free toolsnoindex-checker · v1