How to use it
- 1
Paste a sitemap.xml address or any site page — WebDiag will try /sitemap.xml for that domain.
- 2
Optionally enter the target URL that should be listed in the sitemap.
- 3
Review status, XML type, URL count, and sample loc addresses.
What the tool can do
- Safe sitemap fetching through the backend with SSRF protection and response size limits.
- Detects urlset and sitemapindex, showing URL count or child sitemap count.
- Checks whether a selected target URL is present in the loc entries.
Common use cases
- Verify that a sitemap is published after a release, migration, or CMS change.
- Check whether an important commercial page is included for sitemap discovery.
- Find obvious XML errors before submitting a sitemap to search engines.
How it works inside
If the input is not an XML file, WebDiag builds /sitemap.xml from the input URL origin.
Target URL comparison normalizes host casing, default ports, and trailing slash.
Questions and answers
Should I enter sitemap.xml or a site page?
Both work. If you enter a site page, WebDiag checks /sitemap.xml on that domain. If you enter a sitemap XML directly, that exact URL is checked.
Does it check every child sitemap in a sitemap index?
No. The MVP shows the sitemap index and child loc entries. Recursive checking of every child file should be a separate stage with limits.