Sitemaps for Static Sites: GitHub Pages, Netlify, and Vercel

A plain HTML site, or a small static site generator setup, doesn't always come with a sitemap.xml out of the box. If your framework doesn't generate one automatically, search engines are left to discover your pages purely by following links — which works, but slower and less reliably than handing them a map directly.

Do you actually need one?

For a five-page site, probably not urgently. For anything with more than a handful of pages, a tool directory, a blog, a documentation set, yes — a sitemap is one of the cheapest SEO wins available, and it costs nothing to add.

GitHub Pages

GitHub Pages serves whatever static files sit in your repository, so a sitemap.xml just needs to exist at your site root alongside index.html. There's no build step involved — you generate it once, commit it, and update it whenever you add pages.

Netlify and Vercel

Both platforms serve static files the same way GitHub Pages does, so the same approach works: drop sitemap.xml in your publish directory. If you're using a framework with a build step, check whether it has a sitemap plugin — Next.js and most static site generators have one — but a hand-generated file works identically for smaller sites, and it's often simpler than configuring a plugin correctly.

After you have the file

Add a line to your robots.txt pointing to it (Sitemap: https://yoursite.com/sitemap.xml), then submit the URL in Google Search Console under Sitemaps. That's the entire process — no crawling delay to wait out on your end, submission is instant even if indexing takes longer.

Generate one now

FreeToolDev's sitemap generator turns a pasted list of URLs into a valid sitemap.xml instantly, and the RSS generator covers the other file most static blogs are missing.