Static Site XML Sitemap Builder

About XML Sitemaps

An XML sitemap is a machine-readable roadmap for the important URLs on a website. It gives search crawlers a structured list of pages rather than asking them to discover every route through links alone. This is especially useful for static sites where there may be no WordPress plugin, database, or content management dashboard generating a sitemap automatically. A plain sitemap.xml file can live beside your HTML files on Netlify, Vercel, Replit, GitHub Pages, or a traditional host.

The sitemap format describes each URL with a <loc> element and can also include a last-modified date, change frequency, and priority hint. These fields help communicate your preferred maintenance pattern, but they are hints rather than commands. Search engines still decide when to crawl and whether a page is useful enough to index. Accurate, canonical URLs and strong internal links matter more than adding inflated priority values to every page.

A sitemap can help newly published pages get discovered faster, particularly when a site has few external links or a deep structure. It also gives you a convenient audit list: if an important page is missing, has the wrong hostname, or uses a tracking query string, the sitemap review can expose the problem before deployment.

Key Use Cases

How to Use This Builder

1. Gather the absolute, preferred URLs for indexable pages. Use HTTPS and the exact canonical hostname, and place one URL on each line.
2. Choose a default priority and change frequency. Treat these as planning hints; do not mark every page as the homepage or as constantly changing.
3. Decide whether the file should include today’s ISO-formatted last-modified date, then inspect the generated XML for duplicates and accidental whitespace.
4. Copy the XML or download sitemap.xml, upload it to the domain root, confirm it loads publicly, and submit the URL in Google Search Console.

Real-World Technical Example

A small static publisher with a homepage, an about page, and a weekly article section might create this structure:

<?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-02</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://example.com/about.html</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.5</priority>
  </url>
</urlset>

The <urlset> wraps the document, each <url> represents one page, and <loc> is required. Last-modified dates should describe meaningful page updates rather than changing on every server build.

Frequently Asked Questions

Review Before Publishing

Remove login pages, duplicate query variants, temporary previews, and URLs that return errors. Confirm that every address uses the same HTTPS and hostname convention as your canonical tags. The tool does not fetch or validate the URLs, which is intentional for privacy and speed, so you remain responsible for checking status codes and page content. Keep the sitemap discoverable from robots.txt and update it whenever the site’s indexable URL set changes.

For a growing static project, treat the sitemap as part of the release checklist. Compare the file with the navigation directory, check that deleted pages are not still listed, and verify that a renamed page has a redirect or an updated canonical reference. If your host serves extensionless routes, list the public route that actually returns the page rather than an internal source filename. When search tools report a parsing warning, validate the XML declaration, namespace, escaped characters, and URL format before changing priorities or frequencies.