Plain definition
Definition of XML Sitemap
A machine-readable XML file listing the canonical URLs on your website that you want search engines to discover, crawl, and monitor for meaningful content updates.
Protocol ceiling per sitemap file: 50,000 URLs and 50 MB uncompressed (split via a sitemap index above either limit)Worked example
Say a made-up invoice generator called BillSprig launches with 45 public pages: a homepage, pricing, 12 free template pages, and 31 help docs. It publishes an XML file at https://billsprig.example/sitemap.xml containing each canonical URL inside a loc entry along with an accurate lastmod date recording when that page's content last changed. BillSprig references that file in robots.txt and submits it directly inside Google Search Console.
Under the Sitemaps protocol and Google's published guidelines, a single sitemap file holds at most 50,000 URLs and cannot exceed 50 MB uncompressed. If BillSprig later expands to 75,000 programmatic invoice examples, it cannot keep them in one flat file. Instead, it splits them into two child sitemaps and publishes a sitemap index file pointing to both. Notice also what BillSprig leaves out: Google explicitly ignores priority and changefreq tags, and only uses lastmod when those timestamps stay consistently accurate.
Why it matters when you launch
When your site is brand new and only has a handful of inbound links, search crawlers may take weeks to walk deep into your folder structure on their own. Submitting a clean XML sitemap gives Google and Bing an explicit inventory of every indexable URL right after deploy, while giving you a fast diagnostic view inside Search Console showing which pages were discovered, crawled, or skipped.
Generating the sitemap dynamically from your route list or database guarantees that newly published guides appear automatically and deleted or redirected URLs disappear without manual edits.
Common mistakes
- Listing URLs that return 404 errors, 301 redirects, non-canonical variants, or noindex directives inside your sitemap, which wastes crawl budget and triggers Search Console warnings.
- Stamping every lastmod field with today's build timestamp on each deployment even when the page text did not change, causing Google to stop trusting your lastmod dates.
- Spending engineering time tuning priority and changefreq scores even though Google Search officially ignores both fields.
- Forgetting to split a large generated sitemap into multiple files under a sitemap index once it crosses 50,000 URLs or 50 MB uncompressed.
Tools and guides that use it
Free tool
Robots.txt GeneratorWrite a robots.txt that lets AI search find you, and choose which AI crawlers can train on your site.Free tool
AI Search Readiness CheckerAudit your startup's visibility for Perplexity, ChatGPT Search, and Claude with an actionable 10-point GEO checklist.Founder guide
The Next.js Technical SEO Launch Checklist (2026)What to check before and after launch day: crawlability, metadata, canonical URLs, structured data, sitemaps, internal links, Core Web Vitals and AI crawlers.Founder guide
How to Set Up Google Search Console and Bing Webmaster Tools for a New Site (2026)Choose the right property, verify it, submit your sitemap, read the indexing and Performance reports, add Bing and IndexNow, and know what to check each week.Related glossary terms
Official sources
Pritam Ghosh runs Hauntboard and maintains this glossary.
Published · Updated
Building something real? Launch it in public.
A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.