Developer

XML Sitemap Generator

Generate XML sitemap files from URL lists with optional metadata defaults.

Loading interactive tool…

Embed this tool on your site

About this tool

An XML sitemap is one of the simplest signals you can give a search engine: a structured list of every URL on your site, annotated with how recently it changed, how often it updates, and its relative importance. Without one, crawlers rely entirely on link discovery, which means new or isolated pages can go unindexed for weeks. Sitemap Generator lets you paste a list of URLs and produce a sitemaps.org XML sitemap with lastmod dates, changefreq hints, and priority values — no server, no CMS plugin, and no configuration file required. Each line can be a plain URL or a URL followed by | lastmod | changefreq | priority, and default lastmod and changefreq values fill in any line that leaves them out. Invalid lines are skipped and counted. Whether you are relaunching a site, migrating a blog, or just auditing what is indexed, this tool gets a clean sitemap into your hands in seconds so you can save it as sitemap.xml, submit it to Search Console, or drop it at the site root.

Why use it

  • Instant sitemaps.org Output: Generates a urlset in the sitemaps.org 0.9 namespace with an XML declaration and UTF-8 encoding, the format accepted by Google and Bing.

  • Per-URL Metadata Control: Set lastmod, changefreq, and priority on individual lines rather than accepting CMS defaults — useful for sites where some sections update daily and others never change.

  • No Plugin or CMS Required: Works for any site regardless of platform — static HTML sites, JAMstack builds, legacy PHP apps, or landing pages that have no CMS at all.

  • Runs Entirely in the Browser: Your URL list is never sent to a server — the XML is assembled client-side and handed directly to you, keeping proprietary URL structures private.

  • Bulk URL Handling: Paste hundreds of URLs at once and receive a complete sitemap in under a second, eliminating tedious manual XML editing for large page catalogs.

  • Invalid Lines Reported: Lines that are not valid http:// or https:// URLs are skipped and counted in the status message, so you can spot typos before submitting.

How to use

  1. Paste your list of URLs into the input area — one URL per line, absolute URLs including the https:// scheme.
  2. Optionally add | lastmod | changefreq | priority after a URL, for example https://example.com/blog | 2026-05-01 | weekly | 0.8.
  3. Set a Default lastmod date and a Default changefreq (None, daily, weekly, monthly or yearly) for lines that do not set their own.
  4. Click Generate XML and check the message, which reports how many URL entries were generated and how many invalid lines were skipped.
  5. Click Copy, paste the XML into a file named sitemap.xml, upload it to your site root and submit the URL to Google Search Console.

When it helps

  • When launching a new site that does not yet have a sitemap and you need one before the first Search Console submission.
  • When migrating a site to a new domain and you need to rebuild the sitemap from the redirected URL list.
  • When your CMS-generated sitemap is bloated with tag pages, author archives, or pagination URLs you want to exclude.
  • When working on a static site or JAMstack build with no built-in sitemap plugin.
  • When a client hands you a flat list of page URLs and you need to deliver a sitemap as part of an SEO audit deliverable.
  • When resubmitting a sitemap after a major content restructure to force Google to re-crawl updated priority pages.

Examples

Two URLs with per-line metadata

Input
https://example.com/ | 2026-05-01 | monthly | 1.0
https://example.com/about | 2026-05-01 | monthly | 0.8
Expected result · Scroll for more
<?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-05-01</lastmod>
    <changefreq>monthly</changefreq>
    <priority>1</priority>
  </url>
  <url>
    <loc>https://example.com/about</loc>
    <lastmod>2026-05-01</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Blog posts using default lastmod and changefreq

Input
https://blog.example.com/post-1 | | | 0.6
https://blog.example.com/post-2 | | | 0.6
Default lastmod: 2026-04-15 | Default changefreq: weekly
Expected result · Scroll for more
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://blog.example.com/post-1</loc>
    <lastmod>2026-04-15</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>https://blog.example.com/post-2</loc>
    <lastmod>2026-04-15</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.6</priority>
  </url>
</urlset>

Ampersand escaped in a URL

Input
https://example.com/a&b=1 | 2026-05-07 | never | 0.3
Expected result
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/a&amp;b=1</loc>
    <lastmod>2026-05-07</lastmod>
    <changefreq>never</changefreq>
    <priority>0.3</priority>
  </url>
</urlset>

Tips

  • Submit your sitemap URL in both Google Search Console and Bing Webmaster Tools — the two indexes operate independently, so a submission to one does not notify the other.
  • Declare the sitemap in your robots.txt file with a 'Sitemap:' directive so any crawler that reads robots.txt can discover it automatically, even before you submit it manually.
  • Regenerate and resubmit your sitemap whenever you add more than five new pages or significantly change URL structure — stale sitemaps slow re-crawl of updated content.
  • Use a lastmod date that reflects the date of the most recent meaningful content change, not the date of the last server deployment or template update, for accurate freshness signaling.
  • Prioritize canonical URLs in your sitemap — if a page is accessible via both www and non-www, only list the canonical version to avoid confusing crawlers about which version to index.

Frequently Asked Questions

What is an XML sitemap and why does my site need one?
An XML sitemap is a file that lists all the URLs on your site you want search engines to index, along with optional metadata like last-modified date and update frequency. Search engines use it to discover pages they might miss through link crawling alone — especially important for large sites, new domains, or pages with few inbound links.
How many URLs can I include in a sitemap?
The sitemaps.org protocol allows up to 50,000 URLs and a maximum uncompressed file size of 50 MB per sitemap file. If your site exceeds this, you need a sitemap index file that references multiple child sitemaps. This tool is best suited for sites under that limit.
How do I set priority for my URLs?
Add it as the fourth field on each line, for example https://example.com/ | | | 1.0. Values are rounded to one decimal, so 1.0 is written as 1. Lines without their own priority are currently written with priority 0 rather than the Default priority value, so set it per line if you want to include it. Google has said it largely ignores priority anyway.
What changefreq value should I use?
Use 'daily' for news or heavily updated pages, 'weekly' for blogs and product pages, 'monthly' for evergreen content, and 'yearly' or 'never' for archived or static pages. The default dropdown offers daily, weekly, monthly and yearly; per-line values also accept always, hourly and never. This is a hint to the crawler, not a command.
Does the tool validate URLs before adding them to the sitemap?
The tool checks that each line parses as an http:// or https:// URL and discards blank lines, then reports how many invalid lines it skipped. It does not make network requests to confirm pages are live, so you should audit your URL list before generating to avoid submitting 404 URLs to Search Console.
Where should I place the sitemap file on my server?
Place sitemap.xml at your site root (e.g. https://example.com/sitemap.xml). Then declare it in your robots.txt as 'Sitemap: https://example.com/sitemap.xml' and submit the URL directly in Google Search Console and Bing Webmaster Tools.
Should I include every URL on my site in the sitemap?
No — only include URLs you want indexed. Exclude paginated archives, filtered search result pages, duplicate content, staging or internal-tool URLs, and any page with a noindex meta tag. A leaner sitemap helps crawlers focus budget on your most valuable pages.
Can I use this tool to generate a sitemap index file?
This tool generates a single sitemap file, not a sitemap index. For sites over 50,000 URLs, you would need to generate multiple child sitemaps and manually author a sitemap index XML file that references them — or use a server-side script.

Explore the category

Glossary

XML Sitemap
A structured file in Extensible Markup Language that lists URLs on a website for crawler discovery, conforming to the sitemaps.org protocol.
lastmod
An optional sitemap attribute specifying the date a URL was last meaningfully modified, in YYYY-MM-DD or full ISO 8601 format, used by crawlers to prioritize re-crawl.
changefreq
A hint in the sitemap protocol indicating how often a page's content is likely to change. Valid values: always, hourly, daily, weekly, monthly, yearly, never.
priority
A numeric value between 0.0 and 1.0 indicating a URL's relative importance within your own site. Default is 0.5; does not affect ranking compared to other sites.
Sitemap Index
A parent XML file that references multiple individual sitemap files, used when a site exceeds the 50,000-URL or 50 MB per-file limits.
Crawl Budget
The number of pages a search engine crawler will fetch from a site within a given timeframe. A well-structured sitemap helps allocate this budget toward high-value pages.
A LITTLE HELP. A LOT DONE.
Good tools.
Great flow.

Your shortcut to the everyday. Create, convert, calculate,
and get back to what you love.

✓ Free to use✓ No sign-up✓ 500+ possibilities