Sitemap.xml Generator - Create XML Sitemap for SEO
What's included
Features
/blog/ against your base URL automatically0.0 to 1.0 for all entries& into valid sitemap XML entities<url> block before copying or downloadingsitemap.xml directlySitemap: directive to your crawl rulesAbout this tool
Need Google to Find Every Important URL on Your Site?
You have pages that matter for search - a new service page, a deep documentation article, a product category, or a landing page that is not linked from the homepage yet. Waiting for search engines to discover those URLs through normal internal links can take longer than you want, and crawler tools often pull in noisy URLs you would never want indexed. A clean sitemap.xml file gives Google, Bing, and other crawlers a direct list of the canonical pages you want discovered.
This XML Sitemap Generator creates a valid sitemap from the exact URLs you provide. Enter your base URL, paste one full URL or relative path per line, set the optional lastmod, changefreq, and priority fields, then copy or download a ready-to-upload sitemap.xml file. The tool resolves paths against your canonical domain and escapes XML characters automatically, so URLs containing query separators or special characters do not break the output.
The best sitemap is selective. Include public, canonical, indexable pages: homepage, pricing, services, products, categories, blog posts, docs, changelog pages, and evergreen landing pages. Leave out noindex pages, redirect URLs, staging links, login areas, checkout flows, internal search results, duplicate filters, and tracking URLs. If a page should not appear in Google results, it should usually not appear in your sitemap either.
After generating the XML, deploy it at https://yourdomain.com/sitemap.xml, submit it in Google Search Console, and reference it from robots.txt with a Sitemap: directive. Use Robots.txt Generator for crawl rules, Meta Tag Generator to align canonical URLs, and Schema Markup Generator when the pages in your sitemap also need structured data.
Step by step
How to Use
- 1Enter your canonical base URLType the preferred HTTPS version of your domain, such as
https://example.com, in the Base URL field. This matters when you paste relative paths because the tool turns/blog/into a complete<loc>URL. Use the same canonical domain you use in your Meta Tag Generator canonical tags so the sitemap, page metadata, and Search Console property all agree. - 2Paste one URL or path per lineAdd the homepage, category pages, important landing pages, product pages, documentation pages, and blog posts you want indexed. You can paste absolute URLs or short paths like
/pricing/; blank lines are ignored. Leave out URLs with tracking parameters, session IDs, redirects, noindex tags, checkout pages, internal search pages, and duplicate filter pages. - 3Use Sample or Clear to manage the listClick Sample if you want to see the expected one-per-line format before replacing it with your own URLs. Click Clear when you need a clean editor for a new sitemap.xml file. The URL counter in the header updates as you type, which helps you catch accidental blank lines or missing entries before downloading the XML.
- 4Set an accurate lastmod dateChoose the last meaningful content update date in
YYYY-MM-DDformat. For a new site launch, today is usually fine. For an existing website, use the real publish or update date for the pages you are listing; changing every URL to today when nothing changed can make search engines trust your lastmod signal less over time. - 5Choose changefreq and prioritySelect a change frequency that matches the content type: daily for frequently updated listings, weekly for active blogs, monthly for stable service pages, and yearly for evergreen pages. Set priority as a relative site-level hint, not a ranking lever. A homepage might use
1.0, main categories0.8, and individual posts or utility pages0.6to0.7. - 6Review the generated sitemap XMLRead the output panel before copying. Each
<url>block should include a valid absolute<loc>, and optional<lastmod>,<changefreq>, and<priority>fields should match the values you chose. Confirm there are no doubled domains, staging URLs, localhost URLs, or encoded tracking parameters that would confuse Google Search Console. - 7Copy or download sitemap.xmlUse Copy when you want to paste the XML into a CMS, code editor, or deployment file. Use Download to save a ready-to-upload
sitemap.xmlfile. For static frameworks such as Next.js export, Astro, Hugo, Eleventy, or plain HTML, deploy it at the site root or in the public folder that maps tohttps://yourdomain.com/sitemap.xml. - 8Submit and connect it to robots.txtAfter deployment, open the sitemap URL in a browser and confirm it loads as XML. Submit that URL in Google Search Console under Sitemaps, then reference it in robots.txt with
Sitemap: https://yourdomain.com/sitemap.xml. The Robots.txt Generator can create that companion file with the sitemap directive included.
Real-world uses
Common Use Cases
Got questions?
Frequently Asked Questions
List the canonical URLs you want search engines to discover, wrap each URL in the standard sitemap XML structure, and save the file as sitemap.xml at the root of your site. This generator handles the XML structure for you: paste one URL or path per line, add optional lastmod, changefreq, and priority values, then copy or download the file. After deployment, the file should be available at https://yourdomain.com/sitemap.xml.
Include only canonical, public, indexable pages: your homepage, service pages, product pages, category pages, blog posts, documentation pages, and important landing pages. Do not include noindex pages, redirected URLs, staging URLs, login pages, cart or checkout pages, internal search results, duplicate filter URLs, or URLs with tracking parameters like ?utm_source=. A sitemap should be a clean crawl list, not a dump of every URL your site can produce.
Yes. A URL-list sitemap generator is useful when you already know the pages that matter, especially for small business sites, static sites, portfolios, docs sites, and launch checklists. It also avoids the noise that crawler-based tools can collect from filters, query strings, redirects, and blocked paths. Paste the final canonical URLs here and the tool creates a simple XML sitemap without needing access to your server or CMS.
lastmod is the date a page was last meaningfully changed, using YYYY-MM-DD format. changefreq is a hint about how often the page usually changes, such as daily, weekly, monthly, or yearly. priority is a relative value from 0.0 to 1.0 that compares URLs within your own site; it does not improve search rankings. In practice, accurate lastmod dates are the most useful of the three because they help crawlers notice recently updated content.
No. A sitemap should contain the pages you want discovered and indexed, not every URL that exists. Excluding low-value, duplicate, private, or blocked pages makes the sitemap easier to audit and keeps crawl signals clean. If a page should not appear in Google results, it usually should not be in the sitemap. For large sites, split the sitemap by content type, such as posts, products, categories, or docs.
Upload sitemap.xml to the root of your domain so it loads at https://yourdomain.com/sitemap.xml. In a Next.js, Astro, Vite, or static export project, that usually means placing it in the public folder. In WordPress, most SEO plugins generate it automatically, but a manual file would go in the public web root. After upload, open the URL in a browser to confirm it returns XML instead of a 404, redirect loop, or HTML error page.
Open Google Search Console for the correct property, go to Sitemaps, enter the sitemap path or full URL, and click Submit. Google will show whether the file was fetched successfully and how many URLs were discovered. Submission does not guarantee indexing, but it gives Google a direct crawl source. If URLs are discovered but not indexed, check page quality, canonical tags, robots rules, noindex tags, redirects, and server response codes.
Yes. Add a line like Sitemap: https://yourdomain.com/sitemap.xml to robots.txt so compliant crawlers can discover the sitemap automatically. This line is separate from Allow and Disallow rules and can appear anywhere in the file. If you maintain multiple sitemap files, add one Sitemap line for each. Use the Robots.txt Generator if you want to create both the crawl rules and sitemap directive together.
A single sitemap can contain up to 50,000 URLs and must be no larger than 50 MB uncompressed. Small and medium sites usually fit comfortably in one sitemap.xml file. Large publishers, ecommerce stores, and documentation platforms often use multiple sitemap files plus a sitemap index. If your site is near the limit, split by content type or section so each file stays easier to generate, validate, and troubleshoot.
A sitemap helps Google discover URLs, but it does not force indexing. Google may skip pages because of thin content, duplicate content, weak internal links, canonical conflicts, noindex tags, blocked robots.txt paths, redirects, 404 errors, or server problems. Search Console coverage reports are the best place to diagnose the reason. Treat the sitemap as one part of technical SEO, alongside clean metadata, internal linking, schema markup, and crawlable page content.