Does this fetch my URL?

No. Paste rendered HTML or response headers from your browser, curl, CDN, or crawler. The validator does not request the URL itself.

What is the difference between meta robots and X-Robots-Tag?

Meta robots lives inside HTML. X-Robots-Tag is an HTTP header and can apply to HTML, PDFs, images, feeds, exports, or any other response.

Can this tell whether Google indexed my page?

No. It checks directives in the snippet you paste. Use Google Search Console URL Inspection, coverage reports, or a live crawler for actual indexing and coverage state.

Why does this matter after validating robots.txt and sitemap.xml?

robots.txt and sitemap.xml handle crawl access and discovery. Meta robots and X-Robots-Tag can still tell search engines not to index the discovered page or file.

Should I use noindex or robots.txt?

Use noindex when a URL may be crawled but should not appear in search results. robots.txt controls crawling and can prevent search engines from seeing a page-level noindex directive.

Does valid index/follow guarantee snippets?

No. Snippet display also depends on visible content, snippet directives such as nosnippet or max-snippet, query relevance, and search engine policies.

Is my HTML or header text stored?

No. The check runs in your browser and does not upload, log, store, or share pasted content.

web validator

Meta Robots / X-Robots-Tag SEO Validator

Validate page-level indexability signals across meta robots, X-Robots-Tag headers, canonical targets, snippet controls, and launch noindex cleanup.

Results

Paste input and validate locally.

Status: Ready when you validate.
Indexability details: Ready when you validate.
Meta robots: Ready when you validate.
X-Robots-Tag: Ready when you validate.
Canonical: Ready when you validate.
Noindex?: Ready when you validate.
Nofollow?: Ready when you validate.

Rules & checks

Extracts meta robots content from rendered HTML copied from the final page head.

Parses X-Robots-Tag directives from pasted HTTP headers text for PDFs, feeds, images, exports, and CDN/server responses.

Detects noindex and nofollow, surfaces canonical href when present, and keeps index/follow plus snippet directives visible for release QA.

Pairs with robots.txt and sitemap.xml checks: robots.txt controls crawling, sitemap.xml suggests discovery, and meta/X-Robots directives control page-level index eligibility.

Keeps the check browser-local/offline; no HTML, headers, staging URLs, or launch notes leave the page.

When to use it

Run launch QA before removing staging noindex directives from a production page.
Investigate indexing drops where a template, CDN rule, or plugin may have left noindex/nofollow in place after release.
Check PDFs, image files, exports, feeds, or other file responses where X-Robots-Tag controls indexing outside HTML.
Verify CDN, reverse proxy, and edge header overrides during site migrations or domain moves.
Pair robots directive checks with canonical, sitemap.xml, robots.txt, URL, Open Graph, and JSON-LD validation in an SEO release checklist.
Audit CMS templates that change meta robots directives by environment, content type, or publish status.

Common errors

Leaving staging noindex directives in production templates after a launch or migration.
Setting an X-Robots-Tag header at the CDN, server, or object-storage layer that overrides an otherwise indexable HTML page.
Using noindex on a canonical target while other pages point canonical URLs at it.
Blocking CSS, JS, images, PDFs, or feeds with broad X-Robots-Tag rules without realizing search engines see the header.
Assuming robots.txt disallow, meta robots noindex, and canonical tags solve the same indexing problem.
Mixing nofollow with internal navigation pages where link discovery still matters.

Limitations

This tool does not fetch live URLs, crawl your site, or compare CDN/server headers against the rendered page automatically.
It does not parse robots.txt rules, sitemap inclusion, Search Console index coverage, or Google-selected canonicals.
It reports directive presence and key flags only; search engines can still make indexing decisions based on crawlability, canonicalization, quality, and policies.
It does not prove snippets will appear, because snippet eligibility also depends on page content, query context, and search engine policies.

Tips

Use noindex for pages you do not want in search results; use robots.txt for crawl control, not as a substitute for noindex on already-known URLs.
Check response headers separately from rendered HTML because X-Robots-Tag can affect files and pages without any meta tag.
Keep canonical targets indexable and self-consistent before submitting XML sitemaps or requesting indexing.
Compare template defaults against live headers when Search Console says Submitted URL marked noindex, Excluded by noindex tag, or Crawled - currently not indexed.
Watch snippet controls such as max-snippet, max-image-preview, noarchive, nosnippet, and unavailable_after when search appearance matters.
After this local structural pass, verify important live URLs in Search Console or a crawler that can fetch headers and rendered HTML.

Examples

Staging page protected from indexing

<meta name="robots" content="noindex, nofollow">
Result: noindex and nofollow are detected so the page should not be submitted for indexing.

Production page open to indexing

<meta name="robots" content="index, follow, max-snippet:-1">
Result: index/follow is visible and snippet controls are present in the pasted directive.

PDF or file blocked by header

X-Robots-Tag: noindex, noarchive
Result: header-level noindex is detected for non-HTML files, PDFs, exports, or CDN responses.

Canonical plus robots alignment

<link rel="canonical" href="https://example.com/page"><meta name="robots" content="index, follow">
Result: canonical is surfaced next to the robots directive for launch QA.

Deep dive

This meta robots and X-Robots-Tag indexability validator is a private launch-QA check for SEO teams, developers, and site owners who need to catch noindex, nofollow, noarchive, nosnippet, max-snippet, unavailable_after, and canonical conflicts before publishing.

Paste rendered HTML, HTTP response headers, or a copied <head> snippet to see whether a page is asking search engines to index, follow, suppress snippets, or stay out of results.

Use it after robots.txt and sitemap.xml checks to confirm that crawlers can discover a URL and that the page or file itself is not telling Googlebot to exclude it from search results.

Because the validation is browser-local, you can safely inspect staging pages, protected previews, unreleased migrations, client HTML, CDN header snippets, and draft CMS templates without uploading them to an external crawler.

FAQs

Does this fetch my URL?: No. Paste rendered HTML or response headers from your browser, curl, CDN, or crawler. The validator does not request the URL itself.
What is the difference between meta robots and X-Robots-Tag?: Meta robots lives inside HTML. X-Robots-Tag is an HTTP header and can apply to HTML, PDFs, images, feeds, exports, or any other response.
Can this tell whether Google indexed my page?: No. It checks directives in the snippet you paste. Use Google Search Console URL Inspection, coverage reports, or a live crawler for actual indexing and coverage state.
Why does this matter after validating robots.txt and sitemap.xml?: robots.txt and sitemap.xml handle crawl access and discovery. Meta robots and X-Robots-Tag can still tell search engines not to index the discovered page or file.
Should I use noindex or robots.txt?: Use noindex when a URL may be crawled but should not appear in search results. robots.txt controls crawling and can prevent search engines from seeing a page-level noindex directive.
Does valid index/follow guarantee snippets?: No. Snippet display also depends on visible content, snippet directives such as nosnippet or max-snippet, query relevance, and search engine policies.
Is my HTML or header text stored?: No. The check runs in your browser and does not upload, log, store, or share pasted content.

Related validators

web

Canonical & hreflang Validator

Validate canonical URLs, hreflang alternates, x-default fallbacks, absolute target URLs, and duplicate-content signals before search engines cluster or localize pages incorrectly.

web

HTML Meta SEO Validator

Validate rendered HTML document basics—charset, html lang, language targeting, and launch-readiness signals that support crawl, accessibility, and snippet QA.

web

robots.txt Crawl Control Validator

Validate robots.txt crawl control rules, sitemap hints, and staging-to-production indexing directives locally before launch.

web

Sitemap XML Validator

Validate sitemap.xml launch and indexation signals locally: urlset/index roots, absolute loc URLs, lastmod hygiene, and crawler discovery readiness.

web

URL Validator & HTTP Link Parser

Validate HTTP and HTTPS URLs locally, parse host/path, and catch malformed links before publishing, importing, or sending them to APIs.

web

Open Graph & Twitter Card SEO Validator

Validate rendered Open Graph and Twitter/X card tags for search-result snippets, social previews, share-card images, absolute URLs, and launch QA before publishing.

web

JSON-LD SEO Validator & Rich Result Schema Checker

Validate rendered JSON-LD structured data for schema.org syntax, rich-result readiness, visible-content alignment, and crawlable schema blocks before publishing.

Meta robots and X-Robots-Tag validation is browser-local. Pasted rendered HTML, response headers, staging directives, preview URLs, CDN rules, and client launch notes are not uploaded, fetched, logged, stored, or sent to a server.

Directive-presence validation only. Passing here does not prove live crawlability, robots.txt access, sitemap coverage, Google-selected canonical state, or final index eligibility.