XML Sitemap Example, URL Location, and How to Validate One

The format is deliberately small. A urlset element, one url element per page, and a loc element carrying an absolute URL. Everything else is optional, and two of the optional elements are ignored outright by Google.

The example below is complete and valid. Anything more elaborate is either an hreflang annotation or an element that no longer influences anything.

Put the file at the root, as /sitemap.xml, and reference it from robots.txt. The location is not cosmetic: a sitemap may only list URLs at or below its own directory, so a file at /blog/sitemap.xml cannot legally list anything under /shop/. A root location removes the restriction entirely.

The robots.txt reference matters just as much. It is the only place a crawler is told where the sitemap is without guessing, and it is the first place any checker looks.

Past the size limit — or once you want per-segment reporting — the index format points at child sitemaps instead of listing URLs itself. Splitting by section, by locale, or by content type turns one opaque coverage number in Search Console into several readable ones, which is often reason enough to split well before hitting 50,000 URLs.

Finding a sitemap is a short search with a clear order of preference. The robots.txt pointer is authoritative; everything after it is convention and guesswork.

Validation has two halves, and most tools only cover the first. Syntax validity means the file parses and matches the schema. Content validity means the URLs inside it deserve to be there — and that is the half that decides whether the sitemap helps or hurts.

A sitemap can be perfectly well-formed and still be a liability if a third of its URLs redirect or return 404. Check both.

An online sitemap generator crawls your site once and hands back a static file. That is useful for a one-off audit or a site that rarely changes, but it produces a snapshot that starts drifting immediately, and its lastmod values reflect the crawl rather than the content.

Anything that publishes regularly should generate the sitemap from its own data instead, so the file is correct by construction and lastmod is genuinely the content's modification date. Most CMS platforms do this already; for a custom application it is usually a single route.

DomainLens checks whether a sitemap is declared in robots.txt, whether it is reachable, and whether it parses — the three failures that stop discovery before it starts. A sitemap cannot force indexing, so when URLs are discovered and then left alone, work through indexability debugging , check for index bloat and crawl discovery , and confirm the declaration itself against robots.txt best practices .