An XML sitemap is a text file using the Extensible Markup Language format that catalogues every indexable page you want search engines to crawl. You submit it through Google Search Console or Bing Webmaster Tools, and crawlers reference it when deciding which URLs to visit and how often. The file includes each URL plus optional metadata: last modification date, change frequency estimates, and priority values from 0.0 to 1.0. While Google largely ignores the priority and change frequency tags now, the lastmod date can signal fresh content worth recrawling. For sites with 50+ pages, sitemaps make sure orphaned pages or deep content doesn't get missed during normal link-based crawling. XML sitemaps matter most when your internal linking is weak, you publish content frequently, or you run a large site where new pages might not get discovered quickly through navigation alone. They're also critical for news sites and e-commerce stores adding hundreds of SKUs monthly. A 10,000-page retail site without a sitemap might see new product pages sitting unindexed for weeks. Common mistakes: including noindexed URLs, redirect chains, or pages blocked by robots.txt. Your sitemap should only list canonical, indexable URLs that return 200 status codes. Split large sitemaps into multiple files if you exceed 50,000 URLs or 50MB uncompressed. Use a sitemap index file to reference them all. At Ottawa SEO, we generate sitemaps dynamically through CMS plugins or custom scripts so they update automatically when content changes. For our 500+ domain portfolio, we monitor Search Console for sitemap errors weekly—submitted URLs that 404 or return server errors are red flags for crawl budget waste. We also segment sitemaps by content type (blog posts, service pages, locations) to analyze indexing patterns and spot issues faster. Bottom line: an XML sitemap won't compensate for terrible site architecture, but it ensures Google has a complete list of what you want indexed and reduces the time between publishing and discovery.