XML Sitemap Generator

What is an XML sitemap?

An XML sitemap is a machine-readable list of URLs you want search engines to discover, crawl, and potentially index. It follows the widely supported sitemap 0.9 format: a root urlset with one url entry per location, often with lastmod, changefreq, and priority. You usually host the file at a stable path such as /sitemap.xml, reference it from robots.txt, and can submit it in search consoles. It is not a substitute for strong content and internal links, but it is a direct map of the URLs you care about. Crawlers also discover pages by following links, so a sitemap plus good navigation works best together.

This sitemap generator online runs in your browser: you paste URLs, we normalize (strip fragments, trim queries, de-duplicate, fix slashes) and output downloadable .xml for static hosts, CMS handoffs, or stakeholder reviews. For a longer form guide, read the XML sitemap guide on the blog.

Why developers and SEO teams publish XML sitemaps

Crawlers primarily discover URLs by following links, but an XML sitemap is a direct inventory of the locations you want indexed. That matters for new sites with thin internal linking, large programmatic catalogues, isolated landing pages, or recent migrations where historic links still point at retired hosts. A trustworthy sitemap generator free online workflow lets engineers hand marketing a valid sitemap.xml before deployment without spinning up a CMS job or brittle spreadsheet macros.

Search consoles read lastmod as a recrawl hint—not a ranking lever—but accurate timestamps still help teams coordinate releases and prove that refreshed documentation went live. Pairing machine-readable sitemaps with human-readable hubs (blog posts, changelog pages, developer tools) reinforces topical relevance: crawlers get a URL list while visitors get context. When you are shipping complementary utilities, cross-link from narrative pages to tools such as our regex tester, UUID generator, and Unix timestamp converter so discovery flows both through menus and through in-content links.

Operations teams also export static sitemaps for vendor audits, agency handoffs, and compliance archives. Generating the artifact locally keeps URL lists out of shared tickets when domains are sensitive, while still matching the same normalization rules you document in runbooks.

Real-world examples

Launching a marketing site on a static host

Staging might be a subdirectory or password-protected preview, but production is a bucket plus CDN. Paste the final canonical URLs (homepage, pricing, docs, legal) into the tool, pick a coordinated lastmod, and ship sitemap.xml beside robots.txt. Submit the URL in Google Search Console as part of the go-live checklist alongside HTTPS renewals and redirect tests.

Post-migration cutover

After DNS flips, publish a sitemap that lists only the destination URLs you expect to serve long term. Comparing indexed counts week over week catches orphaned routes you forgot to redirect or canonicalize—especially important when parameter-heavy legacy URLs collapse into cleaner paths.

Segmenting large properties

Enterprises often maintain separate sections (blog, support, product) with different owners. Even if each slice eventually graduates to its own dynamic sitemap route, this static generator remains useful for quarterly audits or when you need a JSON-free snapshot for executives reviewing domain coverage.

How to use this sitemap generator online

1. Paste one URL per line. Schemes are optional; we prepend https:// when missing. Lines starting with # are comments.
2. Review inline validation. Duplicates are skipped so the file stays compact.
3. Choose lastmod—auto (today) or a custom date for a coordinated release.
4. Click Generate sitemap. Use Pretty view for highlighted blocks or Raw XML for the full document, then copy or download sitemap.xml.
5. In Google Search Console, open Sitemaps, add your sitemap URL (for example https://example.com/sitemap.xml), and monitor coverage over time.

lastmod, when honest, can help systems prioritize recrawls; it does not guarantee ranking. For app routes that change often, you can also ship dynamic sitemaps (for example app/sitemap.ts in Next.js) and still use this page for ad-hoc exports.

Example

Generated output looks like the following (dates and priorities follow your options and the tool’s defaults):

<?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-04-23</lastmod>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://example.com/blog/guide</loc>
    <lastmod>2026-04-23</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.6</priority>
  </url>
</urlset>

Common errors

• Invalid or unreachable URLs—typo domains, wrong protocol, or non-200 pages. Consoles will flag them; keep the list aligned with what actually returns indexable content.
• Missing key pages—if a URL is not linked and not in the sitemap, discovery can lag, especially on new sites.
• Conflicting variants—http vs https, trailing slash drift, or query duplicates without a canonical plan. We normalize loc values, but you must match redirects and rel=canonical on the site.
• Expecting priority to rank—it is a relative hint, not a ranking lever. Avoid maxing it everywhere.
• Files that are too large—typical limits are on the order of 50,000 URLs and 50MB uncompressed; use a sitemap index when you outgrow a single file.
• Listing noindex or blocked URLs—keep the map aligned with what you want indexed.

Use cases

Sitemaps help when your site is new, deep, or has weak internal linking, so important URLs are less likely to sit undiscovered. They also help after migrations: one place to list canonical addresses. Combine a clean sitemap with hub pages that link to tools like our Base64 encoder, JWT decoder, and the all tools index so people and crawlers see how content clusters.

Ongoing: regenerate when you add or remove important routes or when you want a fresh lastmod for an audit. Pair the technical file with long-form help on the blog so visitors find explanations, not only URL lists. When you are ready, submit the sitemap in Search Console, review coverage issues, and iterate.

How the sitemap generator works (step by step)

You provide canonical URL strings. The tool normalizes scheme, removes fragments, deduplicates, and emitssitemap 0.9 XML with optional lastmod, changefreq, and priority per row. The output is a hint file, not a substitute for good internal links or quality content.

XML sitemap format reference

Root element is urlset in the sitemaps.org namespace. Each url has a loc (required), optionallastmod in W3C date or datetime format, and optionalchangefreq / priority as relative hints to crawlers.

How to submit a sitemap in Google Search Console

1. Host the file at a stable, crawlable URL (commonly /sitemap.xml).
2. Reference it from robots.txt with a Sitemap: line.
3. In Google Search Console → Sitemaps, add the sitemap URL and watch for errors or warnings on coverage.

Sitemap best practices for SEO

Include only 200-OK, indexable URLs that match rel=canonical. Keep files under 50,000 URLs and 50MB uncompressed, or split with a sitemap index. Do not use sitemaps to spam low-value or duplicate query URLs.

API and automation

Frameworks like Next.js can expose dynamic sitemap.ts routes. Use this page when you need a one-off export for a stakeholder or a static host without a build pipeline.