What is a sitemap, and do I need one?
The short answer
A file listing every page on your site, so search engines do not have to discover them by following links. Most modern platforms generate one automatically. You need it most when your site is new, large, or has pages that nothing links to — and submitting it in Google Search Console takes about ten minutes and is worth doing regardless.
On this page
What it is
A sitemap is a file — usually at yoursite.com/sitemap.xml — listing the pages on your site that you want found. It can also record when each page was last changed.
It is written for machines, not people. Nobody visits it, and it does not appear in your navigation.
What it actually does
Search engines find pages by following links. That works well for a well-linked site and poorly in three specific cases.
A sitemap replaces discovery with a list. It says: here is everything, in one place. It does not guarantee indexing — it removes the excuse of not knowing the page exists.
When it matters most
A new site. Nothing links to you yet, so there is little to follow. This is the case where it helps most.
A large site. Dozens or hundreds of pages, where crawling everything by link takes time.
Pages nothing links to. A landing page, a seasonal page, something not in your navigation. Without a link or a sitemap entry, these are effectively invisible.
After a redesign or migration, when a lot of URLs changed at once.
For a small, well-linked, established site the practical benefit is smaller — but it is still worth having, because it costs nothing and removes a variable.
You probably already have one
Most platforms generate one automatically. Check before building anything: visit yoursite.com/sitemap.xml.
If you see a list of your pages, it exists. If you get a 404, your platform either does not generate one or uses a different location — worth asking whoever built the site.
Submit it, which is the part people skip
Having a sitemap and telling Google about it are different things.
In Google Search Console, add your site, then submit the sitemap URL. Ten minutes, free, and it also gives you the reporting that tells you whether indexing is actually working — which is more valuable than the sitemap itself.
Reference it in robots.txt as well, with a single line. Some crawlers look there first.
What to keep out of it
A sitemap should list pages you want found:
- Not pages that redirect elsewhere
- Not pages that return errors
- Not pages marked noindex — listing a page you have told search engines to ignore is a contradictory signal
- Not duplicates or near-duplicates
Most auto-generated sitemaps handle this correctly. If yours was hand-made and is now out of date, that is worth an audit.
The two-minute check
- Visit
yoursite.com/sitemap.xml— does it exist? - Are your important pages in it?
- Is it submitted in Search Console?
- Does Search Console report errors against it?
If all four are fine, this is done and you will not need to think about it again. If it is missing entirely and your site is new, this is one of the quickest useful things available to you today.
When this is handled for you
The four-point check is worth running on any site you own. On a managed platform it should come back clean without you doing anything — which is a fair thing to verify rather than assume.
Helm generates the sitemap automatically and keeps it current as pages are added, which is the part that usually rots: a sitemap built once at launch and never regenerated is worse than none at all, because it confidently lists pages that no longer exist. Search Console connects from the SEO module, so the submission step this article calls the one people skip is part of setup rather than a task left waiting for someone to remember it.