Browsers block JavaScript from reading pages on other domains (CORS), making automatic crawling impossible in-browser. Export a URL list from your CMS, use "find" on a static site, or pull URLs from Google Search Console instead.
Turn a list of URLs into a valid, correctly-split sitemap.xml — or validate one you already have against Google's actual limits and the sitemap protocol, entirely in your browser.
find command, or pulled from your existing sitemap — and builds valid sitemap
XML, automatically splitting into multiple files with a sitemap index if you're over the
limits. The Validator tab checks an existing sitemap against the same rules.
One per line — full URLs or paths, from any source.
Change frequency, priority, and last-modified date.
Get valid sitemap.xml, split and indexed if needed.
| Rule | Limit |
|---|---|
| Max URLs per sitemap file | 50,000 |
| Max uncompressed file size | 50 MB |
| Over the limit? | Split into multiple files, referenced by a sitemap index file |
| changefreq | Advisory only — search engines may ignore it based on observed actual update frequency |
| priority | Relative to other pages on your own site only — has no effect on ranking against other sites |
Browsers block JavaScript from reading pages on other domains (CORS), making automatic crawling impossible in-browser. Export a URL list from your CMS, use "find" on a static site, or pull URLs from Google Search Console instead.
Only past 50,000 URLs or 50MB per file. Most sites never need one — this tool creates an index automatically only when necessary.
No. Google largely ignores changefreq and treats priority as only a relative hint within your own site — neither is a ranking factor.
No. Both generation and validation happen entirely in your browser. Nothing is sent to any server.
Our support team is here to assist you around the clock. Get Expert Help, Anytime.