A sitemap lists the pages you want crawled and gives search engines a direct route to them. It helps most on large sites, new sites, and sites still building their internal structure, and the indexing report it produces in Search Console is one of the more useful diagnostics available to a small business.
What it does
- Aids discovery. Crawlers find pages primarily by following links. A sitemap offers a direct list, which matters where a site is large, new, or has pages that are poorly linked internally.
- Communicates modification dates. The last-modified value can help crawlers prioritise recently changed pages, provided it is accurate.
- Provides a reference point. Submitting one in Search Console gives you a report of how many submitted pages are actually indexed, which is genuinely useful diagnostic information.
What it does not do
This is where expectations go wrong.
- It does not guarantee indexing. Inclusion is a request. Pages judged low value are declined regardless of what your sitemap says.
- It is not a ranking factor. Nothing about a sitemap improves position.
- It does not replace internal linking. A page reachable only from a sitemap is a page nothing on your site considered worth mentioning, which is itself a signal. Fix the linking, as argued in internal linking.
- Priority and change frequency values are largely ignored. Google has indicated it does not use them meaningfully. They are harmless and not worth agonising over.
Where it helps most
Large sites
Where a crawler might not reach everything through links alone, a sitemap has real value.
New sites with few external links
Discovery is harder when nothing points at you, so an explicit list helps.
Sites with poor internal structure
A genuine benefit, and worth pairing with the linking work described in internal linking so the structure improves alongside it.
Sites with content that changes often
Accurate modification dates help crawlers spend their attention where something actually changed.
Even a well-linked small site benefits from the reporting, since the gap between submitted and indexed pages is a quality signal you get for free and cannot obtain any other way.
What to include and exclude
The principle: a sitemap should list the pages you want indexed, and only those.
Exclude anything that returns an error, anything redirecting, anything blocked from crawling, anything carrying a noindex directive, and any page canonicalised to a different address. Each of these sends contradictory signals, effectively asking for something you have separately declined.
Contradictions of this kind are common in automatically generated sitemaps, which frequently list every address a system knows about rather than every address you want indexed.
Practical points
- Reference it in your robots file. The standard way to point crawlers at it.
- Submit it in Search Console, which is where the useful reporting comes from.
- Keep it current. A sitemap listing pages removed a year ago suggests nothing is maintained.
- Split very large sitemaps using an index file, which also lets you see which sections index well.
- Use accurate modification dates or omit them. A file claiming every page changed today is ignored rather than believed.
Reading the report
The most valuable thing a sitemap produces is the gap between submitted and indexed.
A large gap is informative. It usually means pages are thin, duplicative, or considered not worth indexing, which is a content question rather than a technical one. Chasing indexation through repeated resubmission does not address it, and the appropriate response is frequently the consolidation described in when deleting content improves rankings.
That gap tells you which pages need attention, which is precisely the input a content programme needs to prioritise properly.
Frequently asked questions
Do I need an XML sitemap?
It is worth having and rarely transformative. Sitemaps genuinely help discovery on large sites, new sites with few external links, and sites with poor internal linking, while a well-linked twenty-page business site gains very little beyond the indexing report.
Does a sitemap improve rankings?
No. A sitemap aids discovery of pages but is not a ranking factor, and inclusion in one does not guarantee a page will be indexed. Pages judged low value are declined regardless of whether they appear in a sitemap.
What should be excluded from a sitemap?
Anything returning an error, anything that redirects, anything blocked from crawling, anything carrying a noindex directive, and any page canonicalised to a different address. Including these sends contradictory signals about what you actually want indexed.
Do priority and change frequency values matter?
Not meaningfully. Google has indicated it does not use these values in any significant way. They are harmless to include and not worth spending time adjusting.
Can a sitemap replace internal linking?
No. A page reachable only through a sitemap is a page that nothing on your own site considered worth linking to, which is itself a signal. The sitemap treats the symptom while the linking structure remains the underlying issue.
What does it mean if submitted pages are not indexed?
Usually that those pages are thin, duplicative, or judged not worth indexing, which is a content question rather than a technical one. Repeated resubmission does not address it, and consolidation is frequently the appropriate response.
West Coast Media Solutions Inc. builds and maintains websites for businesses across Canada. Technical behaviour described here reflects how search engines and browsers currently work; specifics change, and your own configuration is what determines the outcome on your site.
Something technical not behaving?
We build and maintain websites for businesses across Canada, and we sort out this kind of thing without the drama.
Start a Conversation