An XML sitemap is a structured file, usually named sitemap.xml, that lists the URLs you want search engines to crawl along with optional metadata like last modification date, change frequency, and priority. When you submit this file through Google Search Console or reference it in your robots.txt, you give crawlers a roadmap to pages they might otherwise miss through internal links alone—especially useful for new sites, deep pages, or large catalogues. Search engines discover sitemaps in three ways: direct submission via Search Console or Bing Webmaster Tools, a robots.txt entry (Sitemap: https://example.com/sitemap.xml), or automatic detection during a crawl. Once found, the crawler queues the URLs as candidates. Critically, inclusion in a sitemap is a hint, not a directive. Google's Page indexing report will show "Discovered – currently not indexed" or "Crawled – currently not indexed" for URLs that were seen but didn't meet quality, relevance, or crawl-budget thresholds. A sitemap also won't override canonical tags, noindex directives, or robots.txt blocks. Metadata fields like <priority> and <changefreq> carry little to no weight in modern crawl decisions; Google ignores them. The <lastmod> timestamp can help if accurate, signaling which pages changed recently, but many CMS plugins auto-update every page on every rebuild, rendering the field useless. For large sites exceeding 50,000 URLs or the 50 MB uncompressed limit, split into multiple sitemaps and use a sitemap index file. Dynamic sitemaps generated by your CMS are preferable to static XML files because they reflect real-time content changes. After submission, monitor the Page indexing report—submitted URLs that remain excluded signal content-quality issues, duplicate canonicals, or thin pages that need consolidation rather than sitemap tweaks. A sitemap accelerates discovery; it does not compel indexing. Review the sitemap against the site's canonical, indexable URL inventory after every material routing or publishing change. Sample entries for successful responses, correct canonicals, and truthful modification dates, then use the Page indexing report and crawl evidence to investigate differences. The objective is a clean discovery source and useful diagnostic segment, not a promise that submitted URLs will be crawled, indexed, or ranked.