Toolkit Shelf
Find

Robots.txt + Sitemap Checker

Use this robots.txt and sitemap checker to verify basic search discovery signals before launching, indexing, redirecting, or submitting a site.

Checks a public page

Live checker

Robots.txt + sitemap checker

Status
Run a guarded check for /robots.txt and /sitemap.xml.
Robots.txtNot checked

0 sitemap declarations found.

Sitemap.xmlNot checked

Not checked URL or sitemap index entries found.

User-agent *Not checked

This is a basic rules summary, not a full crawler simulation.

Review notes
  • Checks only the public origin robots.txt and sitemap.xml. Local, private, reserved, non-http, and credentialed URLs are blocked.
Scope note

This checker verifies the conventional robots.txt and sitemap.xml URLs for one public origin. It does not crawl the site, execute JavaScript, validate every sitemap URL, or simulate a specific search engine bot.

Data freshness

No live response has been fetched yet. Run the checker to record a point-in-time source timestamp.

Web QA reports are launch checks, not crawler verdicts. Search engines, social platforms, consent flows, JavaScript rendering, and cache timing can still change what users or bots see.

What it checks

Robots.txt + Sitemap Checker fetches a site's robots.txt and sitemap.xml, then reports their status, declared sitemap locations, User-agent: * rules, URL counts, and sample sitemap entries. It checks the supplied host only and does not replace a full crawl.

Check method

Discovery check method

Discovery report = guarded origin check + /robots.txt fetch + /sitemap.xml fetch + Sitemap declarations + User-agent * Disallow summary + sitemap loc count

The checker only fetches conventional robots.txt and sitemap.xml URLs for one public origin. It does not crawl the site or simulate a search engine bot.

How to use

Steps

  1. Paste a site homepage, domain, or any public URL from the site.
  2. Run the check to request the origin robots.txt and sitemap.xml files.
  3. Review robots status, sitemap status, Sitemap declarations, User-agent: * disallow rules, and sitemap URL samples.
  4. Fix missing or blocking discovery signals before submitting URLs or relying on organic indexing.

Example

Sample check

Robots declarationSitemap: https://example.com/sitemap.xml
Blocking ruleUser-agent: * with Disallow: / is flagged
Sitemap sampleFirst sitemap <loc> URLs are shown for quick inspection

Checker use

Best for

  • Checking launch, migration, campaign, or support URLs before requesting indexing or handing the page to another team.
  • Capturing concrete page evidence such as redirects, headers, canonicals, robots directives, metadata, schema, headings, image alt text, or internal links.

Before relying on it

Check first

  • Treating one fetched URL as proof that every page, device, locale, redirect, or logged-in state behaves the same way.
  • Ignoring fetch guardrails, blocked private destinations, truncated bodies, JavaScript-rendered tags, or platform-specific preview caches.
  • Submitting or promoting a page before checking the final URL, canonical target, noindex signals, status code, and source-specific warnings together.

Details

What to know before using the output

GuardrailsPublic origin only

Localhost, private networks, reserved IPs, credentials, non-http URLs, and unsafe redirects are blocked before requests are made.

Fetch scoperobots.txt and sitemap.xml

The tool checks the conventional files at the origin root. It does not fetch arbitrary paths or crawl linked pages.

Body limitCapped scan

Large files are truncated to keep the check bounded. Use a full SEO crawler for exhaustive validation.

Source notes

References used for this checker

Google Search CentralDocuments robots.txt files, rules, and how crawlers use them.Google Search CentralDocuments sitemap formats and sitemap submission guidance.MDN Web DocsDocuments the Fetch API used for bounded HTTP requests.

Benchmarks

How to read the output

Robots available: 200-range status.

A reachable robots.txt file makes crawl directives and sitemap declarations explicit.

Sitemap declared: Preferred.

Declaring Sitemap URLs in robots.txt gives crawlers a simple discovery path.

Disallow all: High risk.

Disallow: / for User-agent: * can block broad crawling unless it is intentional.

Method and limitations

Methodology and assumptions

Formula, inputs, limitations and review record
Check method

Discovery report = guarded origin check + /robots.txt fetch + /sitemap.xml fetch + Sitemap declarations + User-agent * Disallow summary + sitemap loc count

Inputs used

Site URL, robots.txt, sitemap.xml, Sitemap declarations, Disallow rules, Sitemap URL count

Limitations

Web utility checkers use bounded public fetches and visible parsing rules. They do not replace a full crawl, Search Console URL inspection, authenticated testing, or platform-specific debugging tools.

Review record

Method and sources checked on July 12, 2026. The documented method, source timing, validity conditions, and reliance limits were checked on this date.

Method provenanceExternal data · toolkitshelf.robots-sitemap-guarded-fetch.v1
Maintained by
Toolkit Shelf
Calculation class
External data
Method version
toolkitshelf.robots-sitemap-guarded-fetch.v1
Primary source
User-provided public URL
Source date
At each run
Source checked
July 12, 2026
Intended audience
Site owners, developers, editors, and launch reviewers checking one public URL at a time.
Valid when
The origin, /robots.txt, and /sitemap.xml must be publicly reachable. Results are bounded by redirect, timeout, and response-size limits.
Reliance boundary
The report checks conventional root files and basic directives; it is not a search-engine crawl verdict, complete robots parser, sitemap submission, or index-coverage report.
Data freshness
Each result is a point-in-time server request. Rerun the checker after the page, server, cache, or redirect behavior changes.
Cite this page

Toolkit Shelf. Robots.txt + Sitemap Checker. https://toolkitshelf.com/tools/robots-sitemap-checker

FAQ

Common questions

Does this prove Google will index my site?

No. It checks basic discovery files only. Indexing can still depend on page quality, canonical tags, noindex rules, internal links, redirects, rendering, crawl demand, and Search Console signals.

Why does it only check /robots.txt and /sitemap.xml?

Keeping the fetch scope fixed avoids turning the tool into a general crawler or proxy. Sitemap URLs declared inside robots.txt are reported for manual review.

Can this replace a technical SEO crawler?

No. Use it for a fast launch sanity check. Use a crawler or Search Console when you need full URL validation, noindex checks, canonicals, redirects, and coverage diagnostics.