Sitemap
A sitemap is a file that lists your site's important pages so search engines can find them faster. It's a hint, not a guarantee.
Start here
- Submit your sitemap in Google Search Console, then check for errors.
- Only include URLs you want indexed—no redirects, no blocked pages.
- Update your sitemap whenever you add or remove important pages.
- Reference your sitemap in robots.txt so search engines can find it.
- Don't treat it like a magic wand—it's a discovery tool, not a command.
I've made plenty of mistakes with sitemaps, so let me save you some time.
What I'd do first
- Generate an XML sitemap using your CMS or a tool like Screaming Frog.
- Submit it in Google Search Console under 'Sitemaps'.
- Check the report for errors—blocked URLs, redirects, 404s.
- Make sure your sitemap is referenced in robots.txt (just add
Sitemap: https://yoursite.com/sitemap.xml). - Update it whenever you publish or remove important pages.
Plain-English take
A sitemap is a file that tells search engines: 'Hey, here are the pages I care about.' It's not a guarantee they'll index them, but it helps them find stuff they might miss—especially if your site is new, large, or has pages buried deep in the navigation. Think of it as a polite nudge, not a command.
How it shows up
You'll see your sitemap in Google Search Console under the 'Sitemaps' section. It'll show you how many URLs were submitted, how many were indexed, and any errors. If you have multiple sitemaps (like one for blog posts, one for products), you'll see them listed there. You can also find it in your robots.txt file if you've added the reference.
Tradeoffs
I used to think a sitemap was a set-it-and-forget-it thing. Not quite. If you include low-value pages (like thin content or paginated archives), you're wasting crawl budget. But if you're too selective, you might miss pages that could rank. The balance: include only pages you want indexed, but don't be stingy with good content. Also, updating the sitemap manually is a pain—automate it if you can.
What I got wrong
Early on, I thought a sitemap was a magic bullet for indexing. I submitted one and expected all my pages to show up in Google instantly. They didn't. I also included a bunch of URLs that were blocked by robots.txt—Google just ignored them. And I never checked the Search Console report for errors. Now I know: submit, check, fix, repeat.
Next step
Quick answers
Do I need a sitemap for a small site?
Probably not. If you have fewer than 100 pages and they're all well-linked internally, Google will find them without a sitemap. But it doesn't hurt to have one.
Can I include multiple sitemaps?
Yes. For large sites, you can create separate sitemaps for different sections (e.g., blog, products) and then submit a sitemap index file that lists them all.
What should I do if my sitemap has errors?
Check Google Search Console for details. Common issues: URLs blocked by robots.txt, redirects, or 404s. Fix those, then resubmit.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central: What Is a Sitemap — Primary source for how Google uses sitemaps.
- Google Search Central: Sitemaps overview (localized version) — Confirms guidance on lastmod and alternate language URLs.
- Google Search Central: Sitemaps documentation — Additional Google documentation reinforcing the same core definition.
Notes from Callum Bennett.