Noindex Checker — Find Indexing Blockers Instantly
Check if any URL is blocked from search results. Detects noindex directives in both the
meta robots tag and the X-Robots-Tag HTTP header — the two places a page can be silently
excluded from Google. Free, no signup, check if your page is indexable in seconds.
How to Use the Noindex Checker
Check whether any URL is blocked from Google's index in three steps — no account, no install, no waiting.
Step 1 — Enter Any URL
Paste the full URL you want to check, including https://. This works on any publicly accessible page — your own site, a client's site before you take it on, or a page you have just published. Prafero fetches the live page directly, so the result reflects exactly what exists right now.
Step 2 — Click Scan
Hit Scan. Prafero checks both the meta robots tag in the page's HTML and the X-Robots-Tag in the HTTP response header — the two separate places a noindex directive can be set. Most checkers only look at one. This tool checks both, every time.
Step 3 — Review the Result
Your indexability status appears instantly: indexed and crawlable, or blocked with the exact directive and where it was found. If a noindex directive is present, the result shows precisely which layer set it — the meta tag, the HTTP header, or both — so you know exactly where to make the fix.
What Is a Noindex Directive?
A noindex directive is an instruction that tells search engines not to include a specific page in their search results. It does not prevent the page from existing or from being visited directly — it simply tells crawlers like Googlebot to skip listing it when someone searches.
There are two separate places a noindex directive can be set, and a page can have either, both, or neither:
The meta robots tag — placed inside the page's HTML <head> section:
<meta name="robots" content="noindex">
The X-Robots-Tag HTTP header — set at the server level, part of the HTTP response rather than the page content:
X-Robots-Tag: noindex
The X-Robots-Tag exists because not every resource is an HTML page. Images, PDFs, and other file types have no <head> section to place a meta tag in — the X-Robots-Tag lets you apply the same noindex instruction at the server response level, to any file type.
When the two conflict, the more restrictive rule applies. If the meta tag says index but the X-Robots-Tag header says noindex, the page is excluded. This is the kind of conflict that is invisible unless you check both layers — which is exactly what this tool does in a single scan.
Why a Noindex Directive Is the Most Dangerous SEO Mistake
Most on-page SEO issues degrade performance gradually — a slow page loses some rankings over time, a missing alt text slightly weakens accessibility signals. A noindex directive is different. It is binary and immediate: the page either appears in search results or it does not, with no middle ground.
It produces no error. There is no broken link, no 404, no console warning. The page loads perfectly for every visitor who reaches it directly. The only symptom is silence — the page never appears for any query, and there is no obvious reason why until someone checks the source code or the HTTP headers.
It is invisible in normal browsing. Opening the page in a browser shows nothing unusual. The noindex tag has zero effect on how the page looks or functions for visitors. The only way to detect it is to inspect the page source or HTTP headers directly — which is precisely what this tool does in under a second.
It commonly survives staging-to-production deployment. Development and staging environments are frequently noindexed on purpose to prevent search engines from indexing unfinished work. When that environment is promoted to production, the noindex directive is sometimes left in place — either in a template, a CMS setting, or a server configuration — and the live page goes out into the world invisible to search.
Noindex vs Nofollow — What's the Difference?
These two directives are often set together but control entirely different things.
Noindex controls whether the page itself appears in search results. A noindexed page is excluded from Google's index entirely — it will not show up for any query.
Nofollow controls whether search engines follow the links found on that page to discover other pages. A nofollowed page can still be indexed and appear in search results; it simply tells crawlers not to pass authority through its outbound links or use them for discovery.
The two are frequently combined as noindex, nofollow — commonly used on thank-you pages, internal search results pages, and admin areas where you want the page completely excluded from both search visibility and link equity flow. They can also be set independently: noindex, follow keeps the page out of search results while still allowing crawlers to discover and follow links on it.
How Noindex Interacts with Robots.txt — The Mistake Almost Everyone Makes
This is the single most misunderstood interaction in technical SEO, and it causes a specific, recurring failure: a noindex directive that never takes effect.
Here is the mechanism. If a URL is disallowed in robots.txt, Googlebot will not crawl that URL at all. If Googlebot never crawls the page, it never reads the page's HTML or HTTP headers — which means it never sees the noindex directive sitting inside it.
The result is counterintuitive: a page can be blocked in robots.txt, carry a noindex tag, and still appear in Google's index. This happens when the page has external backlinks pointing to it. Google can list a URL in search results based on link signals alone, even without ever crawling the page's content, displaying it with no title or description — just the bare URL.
The fix is to choose one mechanism, not both. If you want a page excluded from search results, allow Googlebot to crawl it and let the noindex directive do its job. If you want to prevent crawling entirely — for example, to conserve crawl budget — use robots.txt exclusively and accept that an indirectly-discovered URL might still surface without content.
Use Prafero's Robots.txt Checker alongside this tool to confirm a page is not accidentally blocked from crawling at the same time you are trying to noindex it.
How to Remove a Noindex Tag — Platform-Specific Steps
If this tool detects a noindex directive on a page you want indexed, here is how to remove it on the most common platforms.
WordPress
Most WordPress sites set noindex through an SEO plugin rather than directly in the theme.
Check Settings → Reading → confirm "Discourage search engines from indexing this site" is unchecked. This single sitewide toggle is the most common cause of an entire WordPress site going noindexed.
If using an SEO plugin, check the post or page's SEO settings panel for a per-page "noindex" toggle and set it to allow indexing.
Clear any caching plugin after the change, since cached HTML can serve the old noindex tag for hours.
Re-run this checker on the live URL to confirm the directive is gone.
Shopify
Shopify does not noindex pages by default, but theme customizations or apps can inject the tag.
Check your theme's theme. liquid file for any conditional {% if %} block that outputs a robots meta tag.
Check installed SEO apps for a noindex setting applied to collections, products, or blog posts.
Re-run this checker on the live storefront URL after changes.
Webflow
Open the page in the Webflow Designer → Page Settings → SEO Settings.
Locate the "Hide this page from search engines" toggle and switch it off.
Check Project Settings for a sitewide indexing toggle that may override individual page settings.
Republish the site — Webflow only applies the change after a new publish, not automatically.
Next.js
Next.js sites commonly set noindex through the metadata API or a Head component, and this is a frequent source of accidental noindex during environment-specific configuration.
App Router: search for robots: { index: false } inside any metadata export in layout.tsx or page.TSX files.
Pages Router: search for <meta name="robots" content="noindex"> inside any <Head> component.
Check for environment-conditional logic — for example, code that sets noindex only when NODE_ENV is not production, which can misfire if the environment variable is misconfigured at deploy time.
Check middleware for any code setting the X-Robots-Tag header by route pattern.
Redeploy and verify with this checker on the production URL.
Cloudflare
If a noindex directive is being added at the edge rather than in the application code:
Check Cloudflare Workers for any script setting response. headers.set("X-Robots-Tag", "noindex").
Check Cloudflare Page Rules or Transform Rules for a rule that adds response headers matching the affected URL pattern.
Remove or scope the rule to exclude the URLs that should be indexed.
Verify with this checker — Cloudflare-added headers will show in the X-Robots-Tag result even though they never appear in your site's source code.
Common Noindex Issues This Tool Detects
Sitewide accidental noindex A single global setting — often a "discourage search engines" toggle, a staging configuration left active, or a misapplied server rule — applies a noindex directive across an entire site simultaneously. This is the highest-impact noindex mistake because every page is affected at once.
Noindex directive blocked by robots.txt from being discovered. Covered in detail above — the page is disallowed in robots.txt, so Google never crawls it to read the noindex tag, and the page may still appear in results via backlinks alone with no content shown.
Conflicting directives between the meta tag and the HTTP header. The meta robots tag says one thing, the X-Robots-Tag header says another. Google applies the more restrictive rule, which means the outcome may not match what you see when inspecting only the page source.
Noindex tag rendered by JavaScript, not present in initial HTML. A noindex directive injected by client-side JavaScript after the page loads may not be reliably detected by crawlers, depending on when and how the page is rendered. The safest approach is to set robots directives server-side wherever possible.
Incorrect directive syntax. Common typos like no-index, no index, or noIndex do not match the exact directive value search engines look for and are silently ignored — leaving the page indexed when the intent was the opposite.
Pagination accidentally noindexed A noindex rule intended for one section accidentally matches paginated URL patterns like /page/2/, /page/3/, suppressing the deeper pages of a category or archive from being discovered through search.
Related SEO Tools
A noindex directive is one piece of a page's overall crawlability and indexability picture. These tools inside SEO Space check the layers that work alongside it:
Robots.txt Checker: Check whether a URL is blocked from crawling entirely at the robots.txt level — the companion check to this tool, since a robots.txt block can prevent a noindex directive from ever being discovered or honored.
Sitemap Checker: validates any domain's XML sitemap. A noindexed page that still appears in the sitemap sends a conflicting signal to Google — this tool helps you catch that mismatch.
Meta Tag Analyzer: The robots meta tag is one of several meta tags that control how a page is indexed and displayed. Get a full audit of every meta tag on any URL, not just the robots directive.
Schema Markup Checker: Both noindex directives and structured data live in the technical layer of a page. Check what schema markup is present on any URL alongside your indexability audit.
SEO Score Checker: Want a complete on-page audit beyond just indexability? The SEO Score Checker covers meta tags, headings, internal links, canonical tags, and content length in a single health score.