XML Sitemap Generator

Generate a production-ready XML sitemap for websites, blogs, ecommerce catalogs and multilingual pages. Paste one URL per line, attach lastmod, changefreq, priority, images and hreflang alternates, and get crawl coverage stats.

Free to useNo sign-up requiredUpdated Mar 2026

XML Sitemap GeneratorTry it now — free ▼

⌘ Quick examples

Load a ready-made preset for a marketing site, an ecommerce catalog with images, or a multilingual documentation hub. Each example fills the full form so you can see how sitemap rows, image entries, and hreflang alternates fit together.

Base

Define the canonical host and page list

Site URL Used to resolve relative paths like /blog/ into absolute sitemap URLs.

Default changefreq A light hint for crawlers. Leave blank if your team does not manage this field.

Default priority Optional hint between 0.0 and 1.0. Keep it realistic rather than maxing every page.

Fallback lastmod date Applied to rows that do not already include a YYYY-MM-DD date.

Sitemap URL rows

/
/blog/
/blog/technical-seo-checklist|2026-03-05|weekly|0.8
/contact/|monthly|0.5

Use one row per page. Supported format: /page-url|2026-03-09|weekly|0.8. You can also paste just the URL by itself.

Cleanup

Set canonicalization rules before export

Include lastmod Add a lastmod element when a row has a date or when the fallback date is available. Strip query strings Removes tracking or filter parameters such as ?utm_source= or ?sort=. Strip fragments Removes #section anchors, which are not valid canonical sitemap targets.

Optional

Enrich pages with image and hreflang metadata

Image sitemap rows Format: /page-url|https://cdn.example.com/image-1.jpg|https://cdn.example.com/image-2.jpg.

hreflang alternate rows Format: /en/page|en:https://example.com/en/page|fr:https://example.com/fr/page|x-default:https://example.com/page.

Guide

What a strong sitemap usually gets right

A good XML sitemap is not just a list of URLs. It is a machine-readable index of canonical pages that search engines can actually crawl, render, and index. The strongest files remove tracking noise, stay on the verified host, and mirror the real information architecture of the site.

Keep only indexable, canonical URLs that return HTTP 200.
Use relative paths for speed when the whole sitemap belongs to one host.
Attach image entries for important landing or product pages, not for every decorative asset.
Use hreflang rows only when alternate URLs are equivalent pages, not loosely related content.

Canonical URLs Image namespace hreflang Search Console

The result below is rendered server-side so the final XML, diagnostics, and publish checklist match the exact file you will copy.

Embed XML Sitemap Generator Widget

About XML Sitemap Generator

An XML sitemap is a structured inventory of the URLs you want search engines to discover, prioritize, and revisit. It matters most when a site is large, frequently updated, image-heavy, multilingual, or difficult to crawl through normal internal links alone. A useful sitemap does not try to list every possible URL. It focuses on canonical pages that should actually rank or be eligible for indexing, including the preferred host, protocol, path, and language version for each document.

How to Use

Enter the canonical site URL and sitemap rows. Paste the public site URL first, then add one URL row per line in the main sitemap field. A row can be just a path like /pricing/, or a richer format like /pricing/|2026-03-09|weekly|0.8.
Choose how URLs should be normalized. Decide whether query strings and fragments should be stripped, because production sitemaps usually point only to clean canonical URLs.
Add optional image or hreflang data. Include image rows for important media pages and hreflang rows only when the listed pages are true language or regional equivalents.
Generate, review, and publish carefully. Build the XML output, read the diagnostics, and publish only after confirming that every URL is canonical, indexable, and aligned with the version you submit to webmaster tools.

What Belongs in a Sitemap and What Usually Does Not

Include	Avoid	Why It Matters
Canonical page URLs that return HTTP 200	Redirects, 404 pages, or soft 404 endpoints	Crawlers treat the sitemap as a trust signal. Low-quality or invalid entries weaken that signal.
Primary article, product, category, landing, or documentation pages	Duplicate parameter URLs such as filtered or sorted variants	Canonical coverage should reinforce the page version you want indexed, not multiply crawl paths.
Equivalent language variants with consistent hreflang mapping	Loosely related translations or market pages that are not true equivalents	hreflang works best when each alternate is a real counterpart, not a different content object.
Important media pages with image references	Decorative, blocked, or temporary asset URLs	Image sitemap entries are most useful when the asset is crawlable and tied to a ranking page.

Practical Tips for Better Crawl Coverage

For small brochure sites, one sitemap file is often enough, and the biggest win is simply making sure the file points to clean canonical URLs. For ecommerce sites, it is common to split sitemaps by content type, such as products, categories, blog content, or image-heavy landing pages. For publishers or SaaS documentation sites, lastmod becomes more useful because content freshness changes crawl behavior more often than on static marketing pages.

If a site grows quickly, do not wait until the sitemap breaks. Once you approach the 50,000-URL or 50 MB uncompressed limit, move to multiple sitemap files and a sitemap index. That makes crawling more predictable and gives teams cleaner ownership boundaries, for example one sitemap for docs, one for marketing pages, and one for product catalog URLs.

Common Mistakes That Hurt Sitemap Quality

A frequent mistake is exporting every URL known to the CMS, even if some pages redirect, are canonicalized elsewhere, or were intentionally marked noindex. Another is leaving marketing parameters, internal search queries, or fragment identifiers in the file. Multilingual teams also commonly overstate hreflang coverage by listing alternates that are only partially translated or structurally different pages. In all of these cases, the sitemap becomes less reliable as a source of crawl guidance.

The goal is not completeness at any cost. The goal is clarity. Search engines already discover a large amount of URL noise on their own. Your sitemap should help them ignore that noise and focus on the URLs that deserve crawl budget and index attention.

FAQ

What URLs should go into an XML sitemap?

Use canonical, indexable URLs that return HTTP 200 and represent the preferred public version of each page. That usually means the final HTTPS URL, with the right hostname, without redirect hops, duplicate tracking parameters, or alternate variants that should not compete for indexing.

Do I need lastmod, changefreq, and priority in my sitemap?

Only loc is required, so the file is still valid without the other fields. In practice, lastmod is the most useful optional signal because it helps crawlers understand freshness. changefreq and priority are weaker hints and should be used as honest operational metadata, not as an SEO ranking shortcut.

Can a sitemap include hreflang and image entries?

Yes. Image entries are useful when an important page depends on strong image discovery, such as product detail pages, recipes, or gallery content. hreflang alternates help when the same page exists in multiple language or region variants and you want crawlers to connect those equivalents more clearly.

When should I split a sitemap into multiple files?

Split the file once you approach the standard single-file limits, or sooner if your site has distinct content systems that are easier to manage separately. A sitemap index is common for enterprise content libraries, ecommerce catalogs, marketplaces, and multilingual sites with several content families.

Reference this content, page, or tool as:

"XML Sitemap Generator" at https://MiniWebtool.com/xml-sitemap-generator/ from MiniWebtool, https://MiniWebtool.com/

by miniwebtool team. Updated: 2026-03-09

Developer API available: Run this tool from your app, automation, or agent with one JSON HTTP request. View API docs