

Sitemaps are very useful tools to influence the crawling and indexing process of our website. In this post we will learn how to configure them, how to make the most of them, and some advanced tips if you want to take them a bit further beyond their usual functions.
We can define sitemaps as files created with information about the pages contained in a website, as well as their relationships. Search engines like Google or Bing use them to crawl websites more efficiently: instead of browsing our site by following internal links, they consult the list where we are supposed to include the pages intended to be indexed. In English we call it a sitemap, but be careful not to confuse it with an HTML page usually linked from the footer, designed to help users navigate large websites (nowadays rarely used).
Some of the following may sound obvious, yet it’s surprising how many sitemaps fail to meet these principles. Essentially, we must include in our sitemaps the URLs we want to rank—those we consider valuable. We should ensure that all these pages are accessible and not considered thin content or duplicate content.
In addition to providing a list of URLs, it is recommended to include optional elements such as:
Although at first glance it might seem that the sole purpose of sitemaps is to send URLs for indexing, SEOs use them for several important tasks. These are the main ones:
TIP: to create sitemaps manually, Screaming Frog is a great tool.
Google’s documentation is clear and generous. It accepts and processes sitemaps in three formats:
So don’t complicate things—use XML unless your project’s legacy system makes it impossible.
Here is a list of key requirements for a first-class sitemap:
Generally, it is advisable not to have a single sitemap but several, depending on the project’s structure, SEO priorities and desired segmentation:
Here we share something quite personal, although no secret: the Latevaweb sitemap.
We have chosen to use three sitemap indexes, one per language. The default ES version is at: https://www.latevaweb.com/sitemap.xml
The Catalan and English versions are at: https://www.latevaweb.com/ca/sitemap.xml https://www.latevaweb.com/en/sitemap.xml
Inside each index, you’ll find sitemaps by page type:

And each sitemap includes the Lastmod attribute to indicate the last content update date:

Below is a checklist with all the elements you should review before submitting a sitemap to Google. Internalizing these points is part of what distinguishes an experienced SEO from a beginner:

No. The order is irrelevant. What matters are creation and modification dates, not the ordering.
A standard HTML sitemap usually references the main image of each URL, but you can include up to 1,000 images per URL. If image SEO is important, take advantage of this.
Not necessarily. Small websites with good internal linking and proper canonicals shouldn’t have issues with Google discovering their important URLs. For large websites, however, it is essential to optimize crawl budget.
Still, having a sitemap is generally recommended for any site. It is especially useful for new websites or those containing many non-HTML files.
When submitting a sitemap to Search Console, Google indicates whether it has been accessed and processed. Screaming Frog also helps check detected vs sitemap URLs, non-indexable sitemap URLs, and indexable URLs missing from the sitemap. Online tools such as Validate XML Sitemap are also useful.
You can indicate them using priority and frequency, but Google no longer uses these parameters and will ignore them.
There is no guarantee. Google will crawl the sitemap, but indexing depends on content quality and originality. Sitemaps are a suggestion, not a directive. Google may also index URLs not included in the sitemap if it can access them. To avoid this, you must block them via robots or use noindex.

Hello! drop us a line
In this post we will learn how to set up sitemaps, how to make the most of them, and some advanced tips.