Free online sitemap generator. Enter a list of URLs and generate a standard XML sitemap with changefreq and priority options.
TL;DR: Free online sitemap generator. Paste a URL list to generate a standard XML sitemap in one click, with changefreq and priority options. Download and submit to search engines. Runs locally.
For local tools, open DevTools → Network and search your input — it should not appear in requests.
Next steps
Usage Guide
New sites, campaign pages, and docs need a sitemap.xml so search engines can discover URLs. Turn a list into protocol-compliant XML with changefreq/priority, download, and submit to Search Console — generated locally.
1. Generate a sitemap
URLs must be absolute (https://…). This emits a static map; add real lastmod per page when updates matter — here it is a single default.
- Paste one URL per line.
- Pick default changefreq (e.g. weekly) and priority (0.0–1.0).
- Download sitemap.xml, upload to the root, and submit to GSC/Bing.
2. Using priority / changefreq
Split into a sitemap index beyond 50k URLs or 50MB.
- Home ~1.0, core sections ~0.8, long-tail ~0.5.
- changefreq is a crawl hint, not a guarantee.
- Do not set everything to 1.0 — if all pages are top priority, none are.
3. Limits and next steps
Next: meta-tag-pixel-checker for SEO tags; open-graph-previewer for share cards.
- Multilingual sites need hreflang annotations (not generated here).
- Reference the sitemap in robots.txt so crawlers find it.
- Cross-check: robots.txt-generator can emit that reference.
4. lastmod honesty and index sitemaps
Search engines increasingly distrust lastmod stamps that change on every build regardless of content — a file that says everything changed daily teaches the crawler to ignore the field. Stamp lastmod only when page content materially changed, and let your generator derive it from the data source, not from build time. Past roughly 50,000 URLs, the spec wants a sitemap index file pointing at child sitemaps; most crawlers handle large single files, but the index structure also lets you split by update frequency so the hot section gets crawled on its own cadence. Verify with the search console before assuming ingestion — a sitemap that parses but is never crawled usually means the URLs redirect.
FAQ
No. Parsing the URL list and generating the XML both happen in your browser — the list is not sent anywhere.
Yes, it follows the Sitemaps 0.9 protocol and can be submitted straight to Google Search Console and Bing Webmaster Tools.
Yes. Apply changefreq and priority across your URLs, download the XML, and place it at a reachable path on your site.
Include only canonical absolute URLs — noindex pages don't belong in the map, and very large sites should split into sub-sitemaps for easier maintenance.
Not guaranteed. Crawling still depends on site accessibility and your robots rules — make sure pages are reachable and not disallowed before counting on indexing.
Related Tools
Related Articles
TOTP Two-Factor Authentication Guide: otpauth URI, Algorithms, and Local Debugging
How RFC 6238 TOTP works: algorithms, digits, period, otpauth URIs, countdown windows, and debugging 2FA with a browser-local generator.
Mock Data Generator Complete Guide: Generate Test Data Fast
Generate reproducible test rows with field types, locale samples, and seeds. Export JSON, CSV, TSV, YAML, or SQL for frontend mocks and local DB seeding.
Online JWT Generator/Decoder: JSON Web Token Tool
Learn JWT (JSON Web Token) structure, how it works, and use cases. Mint and decode JWTs with a local browser tool, plus practical signing hygiene.