An XML sitemap is a structured file, typically named sitemap.xml, that lives in your website's root directory and lists all the URLs you want search engines to index. It includes metadata like last modification date, update frequency, and relative priority of each page. Think of it as a blueprint that helps Google, Bing, and other crawlers understand your site's structure without having to discover every page through internal links. The sitemap doesn't guarantee indexing or rankings, but it speeds up discovery, especially for new pages, deep pages with few internal links, or sites with poor navigation architecture. For a 50-page brochure site, you might not see much impact. For a 5,000-page ecommerce site or a news platform publishing 20 articles daily, XML sitemaps become critical infrastructure. A proper XML sitemap excludes pages you don't want indexed: duplicate content, staging URLs, thank-you pages, paginated archives beyond page two, and anything blocked by robots.txt or noindex tags. Including junk dilutes the crawl budget signal. At Ottawa SEO, we typically cap sitemaps at 50,000 URLs and 50MB per file, then split larger sites into multiple sitemaps referenced in a sitemap index file. Most CMS platforms generate XML sitemaps automatically through plugins like Yoast or RankMath for WordPress, or built-in features in Shopify and Wix. You submit the sitemap through Google Search Console and Bing Webmaster Tools, then monitor the coverage reports to catch indexing issues early. Common mistakes include listing canonicalized URLs instead of the canonical version itself, including redirected pages, or forgetting to update the sitemap when launching new sections. If your sitemap shows 800 URLs submitted but only 200 indexed, you've likely got quality issues, duplicate content, or thin pages Google doesn't value. The sitemap alone won't fix that, but it makes the problem visible so you can address the root cause.