An XML sitemap serves as a roadmap for search engine crawlers, explicitly listing every page you want indexed. While crawlers can discover pages through internal links, a sitemap ensures nothing gets missed—especially new content, deep pages, or sites with weak internal linking. The core functions: First, it accelerates discovery. When you publish new content, submitting your updated sitemap through Google Search Console or Bing Webmaster Tools alerts crawlers immediately instead of waiting for them to stumble upon it. Second, it provides metadata like last modification dates and change frequency, helping crawlers prioritize what to recrawl. Third, it surfaces pages that might otherwise be orphaned or require many clicks from the homepage to reach. Sitemaps matter most for larger sites (500+ pages), sites with poor internal linking architecture, new websites with few backlinks, and sites that publish frequently. For a small 20-page brochure site with solid navigation, the impact is minimal—crawlers will find everything anyway. At Ottawa SEO, we generate sitemaps automatically for our portfolio domains using plugins like Yoast or RankMath for WordPress, or custom scripts for static sites. We exclude thin pages (tags, author archives, thank-you pages) and include only indexable content. A bloated sitemap listing 10,000 URLs when only 2,000 matter wastes crawl budget. Common mistakes: forgetting to update sitemaps after major content changes, including noindexed pages (creates conflicting signals), and submitting multiple overlapping sitemaps without a clear index structure. For large sites, we use sitemap index files that reference category-specific sitemaps—one for blog posts, one for service pages, one for locations. One clarification: a sitemap doesn't guarantee indexing or rankings. It's a suggestion, not a command. If a page has thin content or technical issues, Google may crawl it via the sitemap but still choose not to index it. The sitemap's job ends at discovery and providing crawl hints.