XML Sitemap Generator
Builds a standards-compliant sitemap.xml from your list of addresses and assigns priority and change frequency values based on URL depth.
- Sign-in requiredMembership is free
- Open on the Pro plan100 runs a day
- Saved to your historyReachable from your account
What does this tool look at?
Anything that is easy to get wrong by hand, generated for you: meta tags, schema, robots.txt, sitemaps and redirect rules.
- Valid XML output, ready to copy and paste
- Priority assigned automatically by URL depth
- Duplicate and malformed addresses stripped out
- Up to 1,000 addresses
What this tool measures
A sitemap is the most direct way of telling Google which addresses exist on your site. For pages that navigation does not reach, that were published minutes ago or that carry few internal links, it cuts discovery time from days to hours.
The tool parses the list you paste: invalid lines are set aside, duplicates removed, the rest converted into standards-compliant XML. Priority and change frequency are derived from path depth. The root gets 1.0 and daily, first level 0.8 and weekly, second level 0.6 and monthly, anything deeper 0.4 and monthly.
Up to 1,000 lines per run. Leave the date empty and today is used; supply one and it must read 2026-08-30, any other format raises an error. If the file passes 50,000 URLs the audit flags it as a failure.
How to use it
- 1
Paste one address per line
Use full addresses. Lines without a protocol get https prepended. Invalid lines are dropped and the audit reports how many.
- 2
Include only pages you want indexed
Leave out anything carrying noindex, canonicalised elsewhere or blocked in robots.txt. Listing a page in the sitemap while blocking it sends Google two contradictory signals.
- 3
Make the date a real modification date
lastmod is written identically for every URL. Stamping today's date on every publish claims everything changed when nothing did, and search engines eventually stop trusting the field.
- 4
Publish the file
Placement and notification steps are below. After uploading, use the XML Sitemap Checker to confirm the file parses and the URLs respond.
- 5
Submit it in Search Console
Add the address under Sitemaps. A few days later the same screen shows how many URLs were discovered; a number far below your list means the pages have an access problem.
When to use it
- On a hand-built or static HTML site that generates no sitemap of its own.
- To shorten indexing time for a hundred pages you just launched.
- After a migration, to announce the new addresses in bulk.
- To add landing pages that the CMS sitemap leaves out, in a separate file.
Reading the result
Where the file goes
At the root as sitemap.xml, reachable at example.com/sitemap.xml. Add the line “Sitemap: https://example.com/sitemap.xml” to robots.txt; some search engines only learn about the file there.
In a Next.js project
For a static list, place the file at public/sitemap.xml. When the addresses come from a database, write app/sitemap.ts returning MetadataRoute.Sitemap instead: the list regenerates on every deploy and needs no manual upkeep.
In WordPress
WordPress and SEO plugins already publish a sitemap, usually /wp-sitemap.xml or /sitemap_index.xml. A hand-made second file adds to it rather than replacing it. When the two disagree, fix the plugin settings, not the new file.
Priority and frequency values
Google stopped using priority and changefreq for ranking long ago. They stay in the output because the standard defines them and other engines still read them. Do not spend time tuning those numbers.
The size limit
One file holds 50,000 URLs and 50 MB. Larger sites split the file and tie the parts together with a sitemap index. This tool produces a single file, so if you have outgrown it, solve the split on the CMS side.
Questions about the XML Sitemap Generator
No. It speeds up discovery, it does not change evaluation. Adding an already-indexed page to a sitemap gains that page nothing.
Only the ones you want indexed. Tag archives, paginated lists and filtered URLs usually belong outside. A sitemap is not a map of the site, it is the list of pages you care about.
Whenever pages are added or removed. If you generate by hand, refresh after each batch of content. If that becomes a monthly chore, move to automatic generation in the CMS.
This tool reads 1,000 lines per run. The standard allows 50,000 per file. Sites between those two numbers need the list split across several generated files.
Use it alongside these
The other tools in the same category. Run them together and you see the whole picture.
The tool found the problem. Now for the fix
We run technical SEO, content and AI visibility work end to end. Let us review your site and come back with a clear list of what to do.
Monday – Saturday 09:00 – 18:00