What should I set for priority?

0.0–1.0. Most search engines (including Google) ignore priority entirely — it's a relative hint within your own sitemap, not an absolute ranking signal. Set 1.0 for your homepage, 0.8 for important sections, 0.5 for default. Or just leave it out.

Does lastmod actually matter?

Yes — Google uses lastmod as a real freshness signal. Set it to an accurate ISO 8601 timestamp of when the page content last changed. Don't set it to 'now' on every crawl; that's spammy and Google ignores it.

What about sitemap index files for very large sites?

For >50,000 URLs or >50 MB, split into multiple sitemap files and reference them from a sitemap index file. The tool supports both — toggle the 'sitemap index' mode for large catalogs.

Is anything sent to a server?

No — generated locally. Your URL list stays in your browser.

sitemap · xml · seo · live

Generate a sitemap.xml from URLs

Paste a URL list, pick changefreq + priority, and get a sitemaps.org-compliant XML file ready to drop at the site root.

Sitemap Generator

URLs

entries

changefreq

weekly

hint

priority

0.8

weight

Bytes

577

xml

input · urls (one per line)

output · sitemap.xml

<?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-09-26</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://example.com/about</loc>
    <lastmod>2026-09-26</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://example.com/contact</loc>
    <lastmod>2026-09-26</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Quick Start

How to build a sitemap.xml

A sitemap lists every URL you want search engines to know about, with hints about freshness and priority.

01
List URLs
One absolute URL per line. https:// required.
Lookups reference the IANA registries (MIME, HTTP status, TLDs) bundled at build time — no live network calls, no rate limits, no leaked queries.
inputIANAregistryofflinelive
input · queryurls · IANA
```
https://example.com/
```
loaded · IANA bundlespec · ready
02
Pick freshness
changefreq is a hint — always, hourly, daily, weekly, monthly, yearly, never.
Builders emit canonical syntax per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs) so the output passes spec-compliant parsers.
freqRFC 9110canonicalspec-compliantlive
freq · optionsweekly · live
```
changefreq
```
options applied · livecanonical
03
Set priority
0.0 to 1.0 — relative importance compared to other URLs on your site.
Validation flags common pitfalls — uppercase header names, smart quotes inside Content-Type, missing ;charset=utf-8 — before they bite production.
priorityvalidationlintpitfallslive
priority · looked up0.8 · ready
```
priority
```
result · livevalidated
04
Deploy
Save as /sitemap.xml on your site, then list it in robots.txt.
Copy writes the snippet directly into your clipboard; downloads emit the right extension and MIME so curl/httpie pick them up correctly.
deployclipboardMIME-correctblobcurl-ready
ok · copiedready · done
```
/sitemap.xml
```
shipped · ready to shipsuccess

Pro tips

Web-spec details that bite later

Idempotency saves retries

POST/PUT/DELETE should be safely retried. Use idempotency keys and return the same response on duplicate requests.

Match RFC 9110 status codes

Don’t invent codes. 422 for validation errors, 409 for conflicts, 429 for rate limits. Standard codes work with off-the-shelf clients.

Set <code>Cache-Control</code> deliberately

Default browser caching is conservative. Use max-age + stale-while-revalidate for hot endpoints.

Validate Open Graph in dev

OG tags break silently. Use a previewer like OG Generator + Facebook’s debugger before launch.

CORS is a server concern

The browser sends the preflight; the server decides. Wildcard origins disable credentials — be explicit.

MIME drives behaviour

Servers must send the right Content-Type. Browsers sniff but the spec says they shouldn’t — be explicit to avoid surprises.

Use Cases

When to ship a sitemap

New sites, large catalogs, migration, multilingual.

New site launch

Help search engines discover everything on day one. Bundled from IANA registries at build time — no live network call, no rate limit, no leaked queries. The MIME, TLD, and status-code tables are baked in so the tool works offline once loaded.

spec-compliant

Large catalogs

Tens of thousands of URLs need a sitemap (or sitemap index). Output is canonical per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs), so spec-compliant parsers accept it as-is. Cross-browser and cross-library behaviour stays consistent.

offline

Deep pages

Pages buried behind many clicks may otherwise go unfound. Pairs with the curl-to-fetch converter for end-to-end test stubs — copy the curl from DevTools, paste, get an idiomatic fetch() body. Drop into Playwright/Vitest fixtures without manual translation.

IANA-backed

Frequent updates

Signal changefreq so bots return more often. Catches common pitfalls (uppercase header names, smart quotes inside Content-Type, missing ;charset=utf-8) before they bite production. Validation flags rather than auto-corrects so you stay in control.

RFC-aligned

Migrations

Speed up rediscovery after a URL structure change. Validation runs as you type — copy only when the output is shaped correctly. The output drops directly into nginx, Apache, or CDN configs without re-formatting or re-quoting.

production-grade

Multilingual

Combine with hreflang in the sitemap for language variants. Same input plus same options always produces identical canonical output, so the tool is safe to embed in CI scripts that diff against expected configs.

i18n

FAQ

Frequently asked questions

What's the URL limit?

50,000 URLs and 50 MB uncompressed per sitemap file. Larger sites split into multiple files referenced by a sitemap index.

How important is priority?

Google has said they largely ignore priority and changefreq — they're hints, not commands. Still, they're harmless to include.

Where do I put it?

Typically /sitemap.xml on the site root, then declare it in robots.txt with Sitemap: <url>.

Can I include URLs from other domains?

No. All URLs in one sitemap must be on the same host.

Does it run locally?

Yes. The XML is generated entirely in your browser.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!