What a robots.txt checker can verify
Toolmera fetches /robots.txt from the requested site origin and reports its HTTP status, number of User-agent sections, Allow and Disallow directives, declared Sitemap lines and whether a broad wildcard rule appears to disallow the entire site.
The preview shows the fetched file so you can inspect context yourself. This matters because robots rules are grouped by user agent and path, and a simple directive count cannot fully explain how every crawler will interpret a complex file.
Robots.txt controls crawling, not guaranteed indexing removal
A robots.txt Disallow rule is primarily a crawl-control mechanism. Blocking a URL from crawling is not the same as sending a noindex directive in a fetched page response, because a crawler that cannot fetch the page cannot read its meta robots tag.
Use robots.txt to manage crawling of appropriate paths, and use page-level indexing controls when your actual goal is to keep a page out of search results. Always test carefully before blocking large path patterns.
Sitemap directives inside robots.txt
Robots.txt can declare one or more Sitemap locations. The checker extracts those URLs so you can confirm whether the production site points crawlers to the expected XML sitemap or sitemap index.
A sitemap declaration is useful for discovery, but it does not override blocking rules and does not guarantee indexing. The URLs still need to be crawlable, canonical and valuable enough for search engines to process.