What the example is trying to make obvious.
A launch checklist has the final URL list, but the team still needs a clean XML sitemap draft quickly.
Public example
XML Sitemap Draft Example
Show the input and XML output in a linkable reference page.
This example demonstrates the sitemap job itself so launch docs and community threads can point to a concrete before-and-after output.
Useful for small-site launches, static-site docs, and technical onboarding.
Why this page exists instead of using a real user result.
It is a clear proof page for docs, GitHub readmes, and support threads that need a concrete sitemap example.
GoogleAI answersGitHubDeveloper forums
Use the live route for your real input.
XML Sitemap GeneratorUseful for static launches, content audits, migration prep, and small-site publishing workflows.Safe example input
https://example.com/
https://example.com/tools
https://example.com/contactShare-safe example output
<urlset><url><loc>https://example.com/</loc></url><url><loc>https://example.com/tools</loc></url><url><loc>https://example.com/contact</loc></url></urlset>Give communities a short explanation and a live route.
Use a reusable starting state when the job repeats.
FAQ
Short answers before someone shares the page onward.
Is this the final validated sitemap?
It is an example draft, not a guarantee of production validity.
Why not share a real sitemap?
The example page is safer and easier to reuse in documentation.