Find a sitemap folder scope warning before submission
Admin ·
A storefront sitemap lists both a product URL and a help page. The XML can be well formed even when the planned sitemap address puts one entry outside its directory scope. Check the structure and the deployment address together.
Compare the same XML at two sitemap addresses
Choose Load example and Validate sitemap. With Sitemap location set to https://catalog.example/store/sitemap.xml, the /help/ entry gets a directory warning. The /store/ URL is within scope.
Change Sitemap location to https://catalog.example/sitemap.xml and validate again. Both entries are within the new scope, and the report has zero warnings. The XML stays the same. The scope comparison assumes a standard single-origin deployment.
Sitemaps.org protocol and file location rulesGoogle Search Central, sitemap location and submission
Check XML escaping and calendar dates independently
In the first loc, change & to a raw & and validate. The report shows an XML parsing error. Restore & to preserve the query separator through XML parsing.
Change the lastmod value to 2026-02-29. The XML can still be read, but the date check fails because 2026 is not a leap year. Restore the correct modification date or omit lastmod when you do not know it.
Sitemaps.org protocol and file location rulesW3C Note, date and time formats
Keep a copy of what the check covered
Download the JSON report. It includes the recognized root, the URL count and the original line numbers for findings that identify an input field. It describes the saved input rather than fetching any listed URL.
If the file is a sitemap index, validate each child separately. Extension fields such as image and language annotations need their own checks. After deploying, confirm the server response and use your search provider’s owner tools for crawl and indexing results.
Sitemaps.org protocol and file location rulesGoogle Search Central, sitemap location and submission
Common questions
Can the checker read a prefixed sitemap namespace?
Yes. It compares the namespace URI on each core element and supports a bound prefix or the default namespace.
Why do two different lines count as duplicate URLs?
The checker compares the URLs after parsing them. Some spelling differences such as uppercase letters in the hostname serialize to the same address.
Sources
Put it into practice.
Related guides
- Build a Sitemap From a Known URL Inventory
- Find the robots.txt Rule That Controls a URL
- Read an XML well-formedness diagnostic
- Suggest Links From a Garden URL List
- Separate Zero Links From Missing Coverage
- Draft robots.txt Rules With a Public Exception
- How to Validate Hreflang Return Links
- Generate Hreflang for Every Alternate Page
- Trace a Canonical Conflict in Saved HTML
- Split a Catalogue Sitemap Into Parts
- Diagnose Duplicate Items in an RSS or Atom Feed