🗺️ XML Sitemap Generator

Last updated: February 26, 2026

XML Sitemap Generator

Add URLs below, set priority and changefreq, then generate your sitemap.xml ready for Google Search Console.

Bulk Paste (one URL per line)
URL Priority Change Freq Last Modified 









The Complete XML Sitemap Checklist: Everything You Need Before You Submit



An XML sitemap is one of the most misunderstood assets in technical SEO. Most site owners either skip it entirely, generate it once and forget it, or stuff it with every URL the site has ever produced — including 404 pages, pagination duplicates, and filtered e-commerce URLs that Google was never meant to crawl. Getting your sitemap right is not glamorous work, but it has a direct and measurable impact on how fast new content gets discovered and indexed. Here is a practical checklist to follow every time you build or update a sitemap.



1. Confirm Your Sitemap Follows the Sitemaps Protocol Schema


The sitemap standard is defined at sitemaps.org and the XML namespace declaration must appear exactly as specified: xmlns="http://www.sitemaps.org/schemas/sitemap/0.9". Every entry lives inside a <url> tag, and the only truly required element inside it is <loc>. The optional elements — <lastmod>, <changefreq>, and <priority> — are hints, not directives. Google has openly stated it may ignore changefreq and priority when crawling, but they still help indicate relative importance and are worth including for Bing and other search engines that weight them differently.



2. Only Include Canonical, Indexable URLs


This is the single most impactful rule and the one most frequently broken. Your sitemap should only list URLs that return a 200 HTTP status, carry no noindex directive in their <head>, and point to themselves as their canonical URL. Check each of these conditions before adding a URL:


    
  
  • Does the URL return HTTP 200? (Not 301, 302, 404, or 410)
    • 
  
  • Is there a <meta name="robots" content="noindex"> tag on the page? If yes, exclude it.
    • 
  
  • Does the page have a <link rel="canonical"> tag pointing to a different URL? If so, include the canonical target, not this URL.
    • 
  
  • Is the URL behind a login wall or accessible only with authentication? Exclude it — crawlers cannot access it.
    • 



Including non-canonical or non-indexable URLs in your sitemap does not help those pages; it simply confuses Google about your site's structure and wastes crawl budget.



3. Set Priority Values Strategically, Not Uniformly


Priority values range from 0.1 to 1.0. The mistake most generators make is assigning 1.0 to every single URL. When everything is the highest priority, nothing is. Use a tiered approach:


    
  
  • 1.0 — Homepage only
    • 
  
  • 0.8–0.9 — Core product or service pages, main category pages
    • 
  
  • 0.6–0.7 — Blog posts, individual product pages, secondary landing pages
    • 
  
  • 0.4–0.5 — Tag pages, author archives, older content
    • 
  
  • 0.1–0.3 — Utility pages like privacy policy, terms of service, legal disclosures
    • 



This stratification helps search engines understand which pages deliver your core value proposition versus supporting content.



4. Use Real Dates in lastmod — Or Omit the Field Entirely


Google has been explicit about this: if you manipulate <lastmod> by setting it to today's date on every URL regardless of whether the content actually changed, you lose credibility for that signal entirely. Google learns to distrust your lastmod values and may stop using them to prioritize recrawls. The correct approach is to populate <lastmod> only when you know the actual date a page was last substantively modified — typically pulled from your CMS's updated-at timestamp. If you do not have reliable modification dates, omit the field. An absent <lastmod> is better than a dishonest one.



5. Respect the 50,000 URL and 50MB Limits


A single sitemap file cannot contain more than 50,000 URLs and must not exceed 50MB when uncompressed. If your site has more URLs than this, you need a sitemap index file — an XML file that references multiple individual sitemap files. The sitemap index uses a different schema with <sitemapindex> as the root element and <sitemap> entries pointing to each child file. Large e-commerce stores, news sites, and content platforms almost always need this structure.



6. Encode Special Characters Correctly


XML has five reserved characters that must be escaped if they appear in a URL: ampersand (& becomes &), less-than (< becomes &lt;), greater-than (> becomes &gt;), double quote (" becomes &quot;), and apostrophe (' becomes &apos;). URLs with query parameters are common culprits — a URL like ?color=red&size=L will break your sitemap XML if the ampersand is not escaped. Additionally, any non-ASCII characters in a URL should be percent-encoded per RFC 3986.



7. Verify the XML Is Well-Formed Before Submitting


A single malformed entry can cause the entire sitemap to be rejected or partially parsed. Before submitting to Google Search Console or Bing Webmaster Tools, validate your sitemap by pasting the XML into an XML validator or checking Google Search Console's coverage report after submission. Common validation errors include: unclosed tags, invalid characters, incorrect namespace declarations, and missing required elements.



8. Submit Through Google Search Console and Bing Webmaster Tools


Generating the file is only half the task. To actively trigger indexing, submit your sitemap URL through:


    
  
  • Google Search Console — Sitemaps section under Index
    • 
  
  • Bing Webmaster Tools — Sitemaps section in the left navigation
    • 
  
  • Your robots.txt file — Add Sitemap: https://yourdomain.com/sitemap.xml at the bottom so any crawler can discover it automatically
    • 



You can also ping Google directly by fetching https://www.google.com/ping?sitemap=https://yourdomain.com/sitemap.xml, though this is less reliable than Search Console submission for ongoing monitoring.



9. Keep Your Sitemap Current with an Update Schedule


A sitemap that was accurate six months ago may now include deleted pages and miss dozens of new ones. Establish a maintenance cadence based on your publishing frequency:


    
  
  • Daily publishers — Automate sitemap regeneration via CMS plugin or build pipeline on every publish event
    • 
  
  • Weekly publishers — Regenerate and resubmit weekly
    • 
  
  • Static/brochure sites — Regenerate every time a page is added, removed, or significantly updated
    • 



If you use WordPress, plugins like Yoast SEO or Rank Math handle this automatically. For custom or headless setups, build sitemap generation into your deployment pipeline so it never goes stale.



10. Cross-Check Your Sitemap Against Google's Index Coverage


After submitting, check Google Search Console's Index Coverage report over the following weeks. Look for URLs appearing in your sitemap that are flagged as "Excluded" — particularly those marked "Submitted URL not found (404)", "Submitted URL has crawl issue", or "Submitted URL blocked by robots.txt". These are actionable signals telling you exactly which URLs in your sitemap are problematic. Treat this report as a recurring audit task rather than a one-time check.



A clean, well-structured XML sitemap is not a guarantee of indexing — nothing is — but it removes friction from Google's discovery process and ensures the search engine is working from an accurate map of your site's canonical, indexable content. The time invested in getting it right compounds with every new page you publish.

        
FAQ

                

            
Do I need an XML sitemap if my site is already indexed by Google?

            
Yes, you should still maintain a sitemap even if Google has already indexed your site. A sitemap helps Google discover new pages faster, understand your content hierarchy, and recrawl updated pages more promptly. It is especially valuable for large sites, sites with deep internal linking, or any time you publish new content frequently. Without a sitemap, Google relies entirely on following links, which can mean delays of days or weeks before new pages are discovered.

        

                

            
What should the priority value be for my homepage versus blog posts?

            
Your homepage should typically have a priority of 1.0, representing the most important entry point. Core service or product pages should be in the 0.8–0.9 range. Individual blog posts and secondary content pages generally fall in the 0.5–0.7 range. Utility pages like privacy policy or terms of service can be set to 0.1–0.3. Avoid setting every URL to 1.0 — when everything is the highest priority, the signal loses meaning and search engines may disregard it.

        

                

            
Should I include noindex pages, redirects, and paginated pages in my sitemap?

            
No. Only include URLs that return HTTP 200, carry no noindex directive, and point to themselves as their own canonical URL. Pages with noindex tags, 301/302 redirects, canonical tags pointing elsewhere, 404 errors, or pages behind authentication should all be excluded. Including these types of URLs confuses crawlers about your site structure and wastes the crawl budget allocated to your domain.

        

                

            
How often should I update and resubmit my XML sitemap?

            
Update your sitemap whenever you add, remove, or significantly change a page. For active blogs or e-commerce stores that publish frequently, automate sitemap regeneration through your CMS or deployment pipeline so it updates on every publish event. For smaller, less frequently changed sites, updating manually once a week or month is sufficient. After updating, resubmit through Google Search Console so Google processes the changes promptly rather than waiting for its next scheduled fetch.

        

                

            
What is the difference between a sitemap and a sitemap index file?

            
A standard sitemap file lists individual URLs and has a 50,000 URL and 50MB size limit per file. A sitemap index file is a higher-level XML file that references multiple individual sitemap files, allowing you to organize and submit more than 50,000 URLs. The sitemap index uses a different root element (sitemapindex instead of urlset) and contains sitemap entries pointing to each child file. Large e-commerce sites, news portals, and platforms with tens of thousands of pages need this structure.

        

                

            
Does the changefreq value control how often Google crawls my pages?

            
No. The changefreq value is a hint to search engines, not an instruction. Google has stated publicly that it determines its own crawl schedule based on its signals about how often a page actually changes, the page's PageRank, and available crawl budget. That said, changefreq is still worth including because other search engines like Bing treat it with more weight, and it communicates your intent about content freshness even if Google ultimately makes its own decision.

        

            

            
Disclaimer: This article is for general informational and educational purposes only and does not constitute professional, financial, medical, or legal advice. Results from any tool are estimates based on the inputs provided. Always verify important details and consult a qualified professional before making decisions.
            

        
From the Blog