The fastest way to find an XML sitemap is typing the domain followed by /sitemap.xml directly into your browser. For example, ottawaseo.com/sitemap.xml. About 70% of WordPress sites using Yoast or RankMath will respond at that URL. If that returns a 404, try /sitemap_index.xml, /wp-sitemap.xml, or /sitemap1.xml since different plugins and platforms use different conventions. The second method is checking the robots.txt file at domain.com/robots.txt. Most properly configured sites declare their sitemap location with a Sitemap: directive at the bottom of that file. This is actually more reliable than guessing URLs because custom sitemap paths show up here. For sites you own or manage, Google Search Console gives the definitive answer. Navigate to Sitemaps under Indexing in the left sidebar. This shows which sitemaps Google knows about, how many URLs were submitted versus indexed, and any errors. It's the only place where you see Google's actual processing status, not just whether a file exists. Third-party tools like Screaming Frog can auto-detect sitemaps during a crawl by reading robots.txt and following sitemap index structures. Useful when auditing competitor sites or handling large portfolios, though you're still just accessing publicly available files. At Ottawa SEO, we verify sitemaps on every technical audit because misconfiguration is common. We see sites with sitemaps that include noindexed pages (wastes crawl budget), list URLs returning 404s (confuses Google), or contain tens of thousands of tag archives nobody should index. A sitemap isn't just a file you generate and forget; it's a directive telling Google what matters on your site. Watch out for sitemap index files that reference other sitemaps. Large sites often split sitemaps by post type or date. If you only check the index, you're not seeing the actual URLs. Open one of the child sitemaps to verify the structure makes sense and priorities are set correctly. Also confirm the sitemap is referenced in GSC and not blocked by robots.txt, which happens more than you'd think after site migrations.