An XML sitemap is a file that lists important URLs on your website so search engines can discover them more easily. It is useful, especially as a site grows, but it does not improve rankings simply because it exists.
A sitemap helps with discovery.
It does not turn weak pages into strong pages.
That is the key distinction.
What does a sitemap look like?
Most users never see it.
It usually lives at an address such as:
yourdomain.ie/sitemap.xml
Inside, it contains machine-readable information about the URLs on the site.
It may also include information about when a page was last modified.
Search engines can use that file as another way to find pages.
Does Google need a sitemap to find my site?
Not always.
Google crawls links across the web and can discover pages through ordinary navigation and internal links.
For a very small website with clear links, Google may find everything without needing a sitemap.
Google's own documentation says a sitemap is especially helpful for larger sites, new sites with few external links, sites with rich media or sites where pages are difficult to discover naturally.
That does not mean small sites should avoid one.
An XML sitemap is simple to provide and useful to keep accurate.
Worth knowing
A sitemap sounds technical, but for a normal small-business website it should be boring infrastructure. I do not think this is something a client should be upsold as a sophisticated SEO feature. If the site needs one, it should be created correctly, kept current and submitted as part of the basic search setup.
Why have one if Google can crawl links?
Because it gives search engines a clean list of the URLs you consider important.
Think of it as another discovery signal.
If you launch a new guide, add it to the sitemap.
If you remove a page permanently, the sitemap should eventually stop listing it.
The sitemap and the actual site structure should agree.
A sitemap is not a substitute for internal links
This is important for the Built by Gavin Guides system.
I do not want 100 articles that exist only because they are listed in sitemap.xml.
A reader should be able to move through the library logically.
A cost article should link to related cost articles.
The Guides hub should link to category pages.
Categories should link to the guides.
Important commercial pages should be reachable naturally.
Google's own SEO guidance emphasises links as a fundamental way pages are discovered.
So use the sitemap and a coherent internal-link structure.
Does submitting a sitemap guarantee indexing?
No.
Google is very explicit about this.
Submitting a sitemap is a hint about the URLs you want crawled.
It does not guarantee that every URL will be indexed.
Google still evaluates the pages.
That is why getting a website onto Google is broader than simply submitting one file.
Does a sitemap improve rankings?
Not directly.
There is no special ranking bonus for owning sitemap.xml.
Its value is helping search engines discover and process your content efficiently.
That can be important operationally.
But if somebody sells you a "sitemap package" as though it will push the site to page one, be sceptical.
What pages should go in the sitemap?
Generally, include the canonical pages you actually want search engines to consider.
That might include:
Home, Services, Work, About, Contact, important landing pages, category pages and published Guides.
Do not fill it with broken, redirected, duplicate or private URLs.
A clean sitemap reflects the site you actually want indexed.
What about tag and filter pages?
This connects to the tagging system in the Built by Gavin Guides library.
Tags can be useful internally for related content and filtering.
But I do not want every tag automatically becoming an indexable URL.
If a tag page is merely a thin list of articles, there may be no reason to put it in the sitemap.
If a topic eventually becomes a useful curated hub, that is different.
The rule is the same:
does this page deserve to exist as a search result?
How do I submit a sitemap to Google?
Google Search Console has a Sitemaps section where you can submit the sitemap URL.
Once submitted, Search Console can report whether Google was able to read it.
You do not need to resubmit it every time one page changes if the sitemap URL stays the same and the file updates normally.
I cover the wider tool in what Google Search Console does.
Should the sitemap be in robots.txt?
It is common to reference the sitemap from robots.txt using the full sitemap URL.
That provides another straightforward discovery path.
It is not a replacement for Search Console submission, but it is a sensible setup.
Gavin's take
I like technical SEO when it removes friction quietly. A sitemap is a good example: the business owner should not need to think about it every week. The developer should make sure it reflects the public site, avoids junk URLs and works with the internal linking rather than treating it as a magic ranking file.
Gavin’s perspective
What Built by Gavin does
I consider an XML sitemap part of normal technical website setup.
It should not be sold as a mysterious SEO add-on.
As the Guides library grows, the sitemap should update to include the canonical published articles and useful hubs.
At the same time, the internal-link graph remains the more human side of discovery.
Both should tell the same story about what matters on the site.
The bottom line
A sitemap helps search engines find important pages.
Most business websites should have one because it is simple, useful and easy to maintain.
But it is not a ranking trick.
A strong website still needs useful pages, sensible navigation and internal links.
Need the technical foundations handled properly?
See my website options or get in touch.
A sitemap is one of those things I would rather build in correctly than turn into a separate line item later.
---