Generate XML sitemaps to help search engines crawl and index your pages. Add URLs with priority and change frequency for better SEO control.
<?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> </urlset>
A sitemap doesn't get pages indexed. Google decides what gets indexed. A sitemap just tells it where to look. That distinction trips up almost everyone the first time they read about XML sitemaps, and it keeps tripping people up years later when they wonder why a freshly submitted sitemap didn't move the needle. The job of this file is narrow: list canonical URLs you actually want crawled, and signal when they changed. That's it. If a URL is thin, duplicate, or blocked, no sitemap entry will save it.
This tool generates a clean XML sitemap that follows the sitemaps.org protocol — the same spec Google, Bing, and Yandex have agreed on since 2006. You paste in URLs or let it parse a list, set a lastmod date if you have one, and download a file you can drop at /sitemap.xml. Nothing more. No fake authority scores, no padded changefreq values pretending to influence crawl priority. Google publicly stopped trusting changefreq and priority years ago. We include the fields because the spec allows them, but treat lastmod as the only one that actually matters.
Where this matters most is large or fragmented sites. The protocol caps each file at 50,000 URLs or 50MB uncompressed, so anything bigger needs a sitemap index — a parent file that points to multiple child sitemaps. Most CMSes get this wrong by listing every paginated archive, every tag page, every author archive that nobody asked for. Your sitemap should contain the URLs you would defend in a meeting. If a URL doesn't earn a spot in the sitemap, ask why it exists at all.
The other thing people miss: a sitemap is a discovery aid, not a ranking signal. Submitting it in Search Console helps Google find new or updated URLs faster, especially on sites with weak internal linking. It does not boost rankings. It does not override noindex. It does not unblock a robots.txt Disallow. If your indexing problem is content quality or duplication, a sitemap is the wrong tool. If it's discovery — a new section, a stranded URL set, a site relaunch — a sitemap is exactly the right tool.
One last thing to internalize before you generate the file: keep your sitemap honest. If a URL 404s, returns a 301, or has a canonical pointing elsewhere, take it out. Google has said for years that a sitemap full of non-canonical or broken URLs lowers its trust in the whole file. Treat the sitemap as a curated list of your best, live, canonical pages. That's the version that earns crawl attention.
Fresh URLs with few inbound links can sit undiscovered for weeks. A sitemap submitted in Search Console shortens that window dramatically. Use it the day you launch, not three months later when you notice nothing's ranking.
After a migration, you want Google to re-crawl the new canonical URLs fast and stop wasting budget on the old ones. Generate a sitemap of the new URLs only, submit it, and pair it with proper 301s on the old paths.
If pages live three or four clicks deep with no contextual links pointing to them, Googlebot may never reach them through normal crawling. A sitemap is the cheapest fix while you work on the actual linking problem.
News sites, large blogs, and e-commerce catalogs benefit from accurate lastmod values that tell Google which URLs changed since the last crawl. Update the sitemap on publish, not on some unrelated cron job.
You've hit the spec limit. Split into multiple sitemaps grouped by section (products, articles, categories) and reference them all from a sitemap index file. This also makes it easier to diagnose which segment has indexing problems.
Build a valid sitemap.xml for your website.
The crawler walks internal links to discover pages.
Tune changefreq and priority per URL group before exporting.
Upload sitemap.xml to your domain root and submit it in Google Search Console.
Tag archives, paginated /page/47/, author pages, internal search results, faceted filter URLs — most of these don't deserve to be crawled, let alone indexed. A bloated sitemap signals to Google that you don't know your own site. Curate.
Every broken or non-canonical entry lowers the trust Google places in the file. Run a quick check before submission and remove anything that doesn't return a clean 200 with a self-referencing canonical.
Setting priority=1.0 on every URL is the SEO equivalent of writing "URGENT" on every email. Google ignores both fields. Keep them out or leave them at defaults, and put your effort into lastmod.
If lastmod is wrong or static, Google eventually stops trusting it and falls back to its own crawl heuristics. Either keep lastmod accurate or leave it off entirely — a missing field is better than a lying one.
Treat your sitemap like a guest list, not an inventory. The URLs you include should be the ones you actually want crawled, indexed, and ranked. Everything else is noise that lowers Google's confidence in the whole file. Generate it, keep it clean, update it when things actually change, and stop expecting it to do work that belongs to your content.
