Build a valid XML sitemap by hand — add pages, set a priority (0.1–1.0) and change frequency for each, add a last-modified date, and generate standards-compliant sitemap.xml output ready to copy or download.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-08-21</lastmod>
<changefreq>monthly</changefreq>
<priority>1.0</priority>
</url>
</urlset>The XML sitemap format used by every major search engine follows a single, shared open standard published at sitemaps.org, originally introduced by Google in 2005 and quickly adopted industry-wide. A sitemap is a plain XML document with a root <urlset> element containing one <url> block per page, each with a required <loc> (the page's full URL) and optional <lastmod>, <changefreq>, and <priority> fields. Because it's a shared, standardized format, a correctly generated sitemap works identically whether you submit it to Google Search Console, Bing Webmaster Tools, or any other standards-compliant crawler — this tool generates output that validates cleanly against that exact specification.
The one field search engines reliably act on is <loc> — the actual URL, which tells them a page exists and where to find it. <lastmod>, when it's trustworthy (consistently accurate rather than blanket-set to 'today' on every page), can genuinely help a search engine prioritize re-crawling recently changed content sooner. <changefreq> and <priority>, by contrast, are explicitly documented by Google as hints it largely disregards in practice, since search engines have found they can more reliably infer both signals from their own crawl history and page-quality analysis than from self-reported values that site owners have an incentive to inflate. Including them is still good practice and fully valid — they don't hurt — but don't over-invest time fine-tuning priority values expecting a direct ranking benefit.
Sitemaps provide the most practical value in a few specific situations: large sites with thousands of pages that would be slow or unreliable to discover through internal links alone; new sites that don't yet have much external linking pointing crawlers toward their content; sites with pages that are poorly interlinked internally (orphaned pages with few or no internal links pointing to them); and sites with rich media (images, video) or frequently updated content where prompt re-crawling matters. A small, well-linked five-page brochure site gets comparatively little practical benefit from a sitemap, since search engines can trivially discover all five pages by simply following the site's own navigation — but it's still good, low-cost practice to include one.
This tool is built for hand-curating a focused, intentional sitemap — ideal for smaller sites, or for building an initial sitemap before wiring up automated generation. For larger or frequently changing sites (blogs with dozens of posts, e-commerce catalogs, documentation sites), most content management systems, static site generators, and frameworks (including this site's own Next.js setup, via next-sitemap) can generate a sitemap automatically from your actual page routes, which is far more reliable at scale than manually maintaining a list. Use a hand-built sitemap like this one for a small, stable site, or as a way to quickly validate what correct sitemap XML should look like before wiring up automated generation elsewhere.
Once you've uploaded sitemap.xml to your site's root directory, there are two complementary ways to make sure search engines find it: reference it in your robots.txt file with a line like Sitemap: https://yourdomain.com/sitemap.xml (crawlers check robots.txt as a standard first step and will pick up the reference automatically), and separately submit it directly through Google Search Console's Sitemaps report and Bing Webmaster Tools' Sitemaps section, which also lets you monitor how many of your submitted URLs actually got indexed and surfaces any errors the engine encountered while processing your file.
A few mistakes come up repeatedly and are worth checking for directly: including URLs that redirect or return an error instead of the final destination URL (list the page you actually want indexed, not an intermediate redirect); including pages blocked by robots.txt or marked noindex (a contradictory signal that wastes crawl attention); setting every single page's priority to 1.0 (this defeats the purpose of a relative signal — if everything is highest priority, nothing is); and setting lastmod to the current date on every page regardless of whether it actually changed, which search engines have been documented to notice and start discounting. A smaller, accurate, honestly-labeled sitemap is more useful than a larger one padded with inflated or incorrect metadata.
Sitemap Generator pairs naturally with these other SEO tools.