Create valid XML sitemaps with priority, change frequency, and last modified dates.
Enter the URLs of all pages to include in the sitemap.
Assign priority and change frequency for each URL.
Click generate to create the XML sitemap file.
Save the sitemap.xml for upload to your web server.
A sitemap.xml is the message you leave at your site's front door telling search engine crawlers which pages exist and when each one last changed. This tool builds that file from a list you supply: one URL per line, with optional last modified dates, change frequencies, and priority weights, and it hands back XML that is ready to upload. The thing most people get wrong is treating priority and change frequency as ranking controls. They are hints. Google has said it ignores both, and it trusts lastmod only when the dates are consistently accurate.
A concrete input and expected output from the current implementation.
Input
One URL per line, with optional lastmod, changefreq, and priority after a tab: https://example.com/ 2026-08-10 monthly 0.8 https://example.com/about 2026-07-02 weekly 0.6
Expected output
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-08-10</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/about</loc>
<lastmod>2026-07-02</lastmod>
<changefreq>weekly</changefreq>
<priority>0.6</priority>
</url>
</urlset> Each input line became one <url> block containing the required loc and the three optional attributes, in the order sitemaps.org uses in its examples: loc, lastmod, changefreq, priority. The urlset root declares the 0.9 namespace, which is what tells a crawler this document is a sitemap rather than arbitrary XML.
You enter URLs one per line and, for any entry, can add three optional values: a last modified date, a change frequency, and a priority. Each entry becomes a <url> block inside the <urlset> root, which carries the sitemaps.org namespace so parsers recognize the document. Every loc is emitted as an absolute URL with reserved characters escaped, and attributes you leave blank are omitted entirely, which the protocol permits.
Validity has hard boundaries the generator watches: one file may hold at most 50,000 URLs and stay under 50 MB, change frequency must be one of the seven defined values (always, hourly, daily, weekly, monthly, yearly, never), and priority must fall between 0.0 and 1.0, with 0.5 the implicit default. The finished document is UTF-8 XML you copy or download, upload to your site, and submit.
No. Google states it ignores priority and changefreq, so they have no effect on its rankings. Other engines may read them as hints, but none guarantees them weight. What moves rankings is content, relevance, and links; a sitemap only improves discovery and crawl behavior.
Split the list into several sitemap files, each under the 50,000-URL and 50 MB caps, then publish a sitemap index: a <sitemapindex> document whose <sitemap> entries point at each file, and submit the index instead. Large sites often split by section, one file per category or archive year.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Convert between bytes, KB, MB, GB, and TB with precise binary and decimal calculations.
Open, view, and edit CSV files in a spreadsheet-style table with sorting and filtering.
Visualize JSON data as a collapsible tree with syntax highlighting and search.
Generate Code 128, EAN, UPC, and other barcode formats with customizable size and labels.
Convert images to Base64 data URLs and decode Base64 strings back to images.
Generate Apache .htaccess redirect rules for 301, 302, and rewrite configurations.