List canonical, indexable URLs only
Avoid redirects, errors, duplicate parameter pages, and URLs explicitly marked not to be indexed.
DISCOVERY CHECK
Sitemap Checker
Score sitemap availability, structure, and declarations.
XML·Response·Health score
A domain checks /sitemap.xml at its root; a full file URL checks that exact location.
Data handling: this public address is sent to a GoTools server, which fetches the relevant site file. Do not submit private-network addresses, credential-bearing URLs, or sensitive query parameters. Read the Privacy Policy
Webmaster Technical SEO and AI Discoverability Guide
Learn how robots.txt, sitemap.xml, and llms.txt work together.
About sitemaps: present important URLs clearly to search engines
A sitemap is an XML file declaring important site URLs, or a sitemap index pointing to multiple sitemap shards. It helps search engines discover new and updated pages on complex sites, but submission does not guarantee indexing.
A healthy sitemap should be reliably accessible, structurally valid XML, served with an appropriate content type, and discoverable through robots.txt or search-engine tooling. This checker combines availability, structure, encoding, URL entries, declaration, and response performance into an explainable score.
Sitemap Best Practices
Use indexes for larger sites
Split maps by content type, language, or update cadence, then organize them with a sitemapindex file.
Expose via robots.txt and Search Console
Declare the sitemap in robots.txt and submit it in search tooling to observe fetching and processing issues.
Keep update signals honest
Update lastmod only for meaningful content changes so crawl scheduling receives useful signals.
Use the sitemap checker to verify that a public sitemap is reachable, valid UTF-8 XML, correctly structured as urlset or sitemapindex, and discoverable from robots.txt. It also checks URL counts, redirects, response time, and a limited set of child sitemaps. A passing result supports discovery but does not guarantee indexing.
How to use it
Enter a public domain or full sitemap URL, run the check, then review availability, XML structure, robots.txt declaration, URL count, redirects, response time, and any sampled child sitemaps. Resolve failed required checks before resubmitting the sitemap.
Worked example
Input
https://example.com/sitemap.xml
Output
Example result: HTTP 200 · urlset · 24 URLs · declared in robots.txt
Supported behavior and limits
- Accepts a public HTTP or HTTPS domain or full sitemap URL; private-network and credential-bearing destinations are blocked.
- Reads up to 512 KiB for analysis and validates up to 10 child sitemaps from a sitemap index.
- The protocol itself permits up to 50,000 URLs and 50 MB uncompressed per sitemap; larger sets require sitemap indexes.
Privacy and data handling
The public URL is sent to a GoTools server, which fetches the sitemap, robots.txt, redirects, and limited child sitemaps needed for the check.
Frequently asked questions
- Does submitting a sitemap guarantee immediate indexing? No. A sitemap is a discovery hint; crawling, indexing, and ranking remain search-engine decisions.
- Where should a sitemap be hosted? The common entry point is /sitemap.xml at the site root, but another public URL can be used if declared in robots.txt or search tooling.
- When should I use a sitemap index? Use a sitemapindex when a site has multiple sitemap shards, language sections, or a large collection of URLs.
- Why does the score check robots.txt declaration? A robots.txt declaration is a broadly discoverable public entry point. Its absence does not invalidate XML, but removes a useful discovery channel.