Related Tools
How to Use
- 1Enter your website's base URL in the domain field (e.g., https://example.com). This base URL is prepended to any relative paths you add. Make sure to use the canonical version of your domain (with or without www, and always HTTPS if your site supports it).
- 2Add your page paths or full URLs, one per line. You can paste relative paths like /about, /blog/my-post, /products/widget, or full URLs. The tool normalizes entries to ensure consistent, valid URL formatting in the final sitemap output.
- 3Set the change frequency (changefreq) for each URL to indicate how often the page content is likely to change. Options include always, hourly, daily, weekly, monthly, yearly, and never. This is a hint to search engines, not a directive — Google has stated it largely ignores changefreq, but Bing and other engines may use it for crawl scheduling.
- 4Assign a priority value between 0.0 and 1.0 to indicate the relative importance of each URL within your site. The default is 0.5. Use higher values (0.8-1.0) for your most important pages like the homepage and key landing pages, and lower values (0.1-0.3) for less critical pages like privacy policies or archived content.
- 5Optionally set a last modified date (lastmod) for each URL. This should reflect the date the page content was last meaningfully updated. Accurate lastmod dates help search engines prioritize recrawling recently changed pages. Avoid setting all dates to today — this reduces the signal's usefulness.
- 6Click Generate to create your XML sitemap, then copy the output to your clipboard or download it as a sitemap.xml file. Upload the file to your website's root directory and reference it in your robots.txt file with a Sitemap directive. Submit it through Google Search Console for fastest discovery.
About XML Sitemap Generator
The XML Sitemap Generator creates standards-compliant sitemap files following the Sitemaps Protocol (sitemaps.org), the open standard supported by Google, Bing, Yahoo, and other major search engines. A properly formatted and submitted sitemap helps search engines discover your pages more efficiently, understand your site structure, and prioritize crawling of your most important and recently updated content.
XML sitemaps are especially critical for specific types of websites. New websites with few external backlinks benefit because search engines may not discover all pages through link crawling alone. Large e-commerce sites with thousands of product pages need sitemaps to ensure deep catalog pages are found. Sites with complex JavaScript rendering benefit because sitemaps provide a direct URL list that does not depend on the crawler executing client-side code. And any site that publishes content frequently benefits from lastmod dates that signal which pages have been recently updated.
The sitemap protocol supports several metadata fields for each URL entry. The <loc> element contains the full URL and is the only required field. The <lastmod> element provides the last modification date in W3C Datetime format (YYYY-MM-DD), which Google uses as a signal for recrawl priority. The <changefreq> element hints at how often the page changes, though Google has publicly stated it largely ignores this field. The <priority> element indicates relative importance within your site on a 0.0 to 1.0 scale, helping crawlers allocate budget across your pages.
Google's Search Central documentation emphasizes that sitemaps are a discovery mechanism, not an indexing guarantee. Including a URL in your sitemap tells Google the page exists and provides metadata about it, but Google still evaluates each page independently for content quality, uniqueness, and relevance before deciding whether to index it. Pages blocked by robots.txt, marked with noindex, or deemed low-quality may not be indexed even if they appear in your sitemap. Conversely, Google will discover and index pages not in your sitemap if they are linked from other crawled pages.
Best practices for sitemap management include keeping your sitemap updated automatically when pages are added, changed, or removed. Include only canonical URLs — never list duplicate pages, paginated results, or URLs that redirect. Keep individual sitemaps under 50,000 URLs and 50MB uncompressed (the protocol's limits), and use a sitemap index file to reference multiple sitemaps if your site exceeds these limits. Reference your sitemap in robots.txt with the Sitemap directive so all crawlers can discover it automatically without relying on manual submission.
This tool generates the complete XML structure including the proper XML declaration, urlset namespace, and individual url entries with all supported metadata fields. The output is ready to save as sitemap.xml and upload to your server's root directory. For sites built with frameworks like Next.js, WordPress, or Django, consider using the framework's built-in sitemap generation instead, as these can automatically update when content changes. All processing runs locally in your browser — your URLs and site structure are never transmitted to any external server.
Frequently Asked Questions
What is an XML sitemap and why do I need one?
An XML sitemap is a structured file that lists your website's URLs along with optional metadata including last modification date, change frequency, and relative priority. Search engines like Google and Bing read this file to discover and understand your site's pages more efficiently than relying solely on link crawling. While not strictly required for small, well-linked sites, a sitemap is considered an SEO best practice for all websites because it provides a direct communication channel with search engine crawlers about your site's content.
Where should I place my sitemap.xml file?
Place your sitemap at the root of your domain so it is accessible at https://yourdomain.com/sitemap.xml. This is the standard location where search engines look first. Additionally, add a Sitemap directive in your robots.txt file (e.g., Sitemap: https://yourdomain.com/sitemap.xml) so all crawlers can discover it automatically. You can also submit the URL directly through Google Search Console and Bing Webmaster Tools for immediate processing.
Should I include every page of my website in the sitemap?
No. Include only pages you want search engines to index — your canonical, high-quality content pages. Exclude duplicate content, paginated archive pages, admin interfaces, search result pages, URLs blocked by robots.txt, and pages with noindex meta tags. Including non-indexable URLs wastes crawl budget and sends confusing signals. A focused sitemap containing only your best content helps search engines prioritize crawling the pages that matter most for your SEO.
How do I submit my sitemap to Google?
The most reliable method is through Google Search Console. Navigate to the Sitemaps section under Indexing, enter your sitemap URL, and click Submit. Google will confirm receipt and report any errors found during processing. You should also add a Sitemap directive in your robots.txt file for automatic discovery by all crawlers. Google also discovers sitemaps through links on your site and through sitemap index files. After submission, monitor the Coverage report in Search Console to see how many URLs were discovered and indexed.
Does having a sitemap guarantee my pages will be indexed?
No. A sitemap is a discovery hint that tells search engines your pages exist, but it does not guarantee indexing. Google independently evaluates every page for content quality, uniqueness, relevance, and compliance with webmaster guidelines before deciding whether to include it in the search index. Low-quality pages, thin content, and duplicate pages may be discovered through your sitemap but still not indexed. Think of a sitemap as a request for attention, not a guarantee of inclusion.
What is the maximum size for an XML sitemap?
The Sitemaps Protocol specifies a maximum of 50,000 URLs per sitemap file and a maximum uncompressed file size of 50MB. If your site exceeds either limit, split your URLs across multiple sitemap files and create a sitemap index file that references each individual sitemap. The index file itself follows a similar XML format using the sitemapindex element. You can also gzip-compress your sitemaps to reduce file size and bandwidth — search engines support compressed sitemaps and the Sitemap directive can point to a .xml.gz file.
Does Google use the priority and changefreq values?
Google has publicly stated that it largely ignores the changefreq and priority values in sitemaps. Google relies on its own crawl signals and algorithms to determine how frequently to recrawl pages and how important they are. However, the lastmod date is a genuinely useful signal — Google uses accurate lastmod values to prioritize recrawling recently updated content. Bing and other search engines may use changefreq and priority more actively, so including them is not harmful and may benefit your visibility on non-Google search engines.
How often should I update my sitemap?
Your sitemap should be updated whenever you add, remove, or significantly change pages on your website. For dynamic sites with frequent content updates, use automated sitemap generation that rebuilds the file on each deployment or content change. For static sites, regenerate the sitemap whenever you publish new pages. The lastmod dates should accurately reflect real content changes — avoid updating all dates simultaneously, as this dilutes the signal and may cause search engines to distrust your lastmod values. Frameworks like Next.js and WordPress can generate sitemaps automatically during the build process.