Loading page
About this tool
Create standard XML sitemaps containing page URLs, update frequency, priority levels, and modification dates to optimize crawling.
The Sitemap Generator builds a valid XML sitemap against the sitemaps.org 0.9 schema, writing a <url> block for each page with its <loc>, <lastmod> date, <changefreq> and <priority>. You add URLs one at a time — the protocol is filled in as https:// if you leave it off — watch the XML update live, then copy it or download it as sitemap.xml to drop at your site root. It suits small and mid-sized sites and hand-built pages where no CMS is emitting a sitemap for you.
Open Sitemap Generator on AltFTool — it loads instantly in your browser.
Paste your code or data sample into the workspace.
Pick the format, conversion, or analysis you need.
Copy the polished result straight back into your project.
The namespace, element order and nesting are written for you, so the common failures — a missing xmlns, tags in the wrong order — cannot happen.
Every field you change is reflected in the output pane immediately, so you can see exactly what a lastmod or priority change does to the file.
Priority is offered on the 0.1 to 1.0 scale with sensible labels and changefreq as the seven values the protocol actually permits, instead of free text a parser will reject.
50,000 URLs, or 50 MB uncompressed, whichever comes first — that is the sitemaps.org protocol limit. Larger sites split into multiple sitemap files referenced by a sitemap index file.
Put it at your site root, for example https://example.com/sitemap.xml, then either submit it in Google Search Console or add a `Sitemap:` line pointing to it in your robots.txt. A sitemap only has to cover URLs at or below its own directory level.
No. Google has stated it ignores both — priority does not raise a page's ranking and changefreq does not control crawl frequency. They remain part of the schema and some other crawlers read them, which is why the fields are here, but lastmod is the value worth keeping accurate.
W3C Datetime — YYYY-MM-DD is the usual form, optionally with a time and timezone. Set it to the date the page's content genuinely changed; a lastmod that updates on every deploy while the content is unchanged teaches crawlers to stop trusting it.