When you publish a new article on your blog, you assume that Google will find it. In practice, some pages remain invisible for weeks because the search engine simply hasn’t discovered them. The sitemap is the file that solves this problem: it lists your URLs so that crawling bots know exactly what to explore.
Clean your XML sitemap before trying to enrich it
Most guides start with creating the file. The real starting point is cleaning up. A sitemap that contains redirects, noindex pages, or URLs returning a 404 error sends a mixed signal to search engines.
Only canonical, indexable URLs that return a 200 status code deserve to be included. Specifically, open your sitemap.xml file and check that each address corresponds to an active, accessible page that you actually want to see appear in search results.
Parameter variations (filters, sorting, pagination) and duplicates created by your CMS clutter the file. Remove them. A streamlined sitemap allows Google to allocate its crawl budget to the pages that matter, such as your in-depth articles or main categories. To see a concrete example of a well-structured sitemap on a blog, you can check the sitemap page of LES BABILLAGES DE BABINETTE, which illustrates this sorting logic.
Lastmod and priority tags in a sitemap: what Google really uses
You may have noticed that your SEO plugin automatically fills in the priority and changefreq tags in the XML file. These two fields are no longer useful. Google now ignores them.
The only temporal tag still taken into account is lastmod. It indicates the date of the last modification of a page. Google can use it to decide to re-crawl an updated article.
But be careful: this tag only works if it reflects a real editorial change. Rewriting a paragraph, adding a section, updating outdated information—these are changes that justify a new date. However, if your CMS updates lastmod with every cache regeneration without any content change, Google eventually ignores this date, deeming it artificial. It’s better to omit the tag than to send a misleading signal.
How to check if lastmod is reliable on your blog
Open your sitemap in a browser. Compare the date displayed for an article with the date of its last real modification in your editor. If the two match, all is well. If the sitemap date advances automatically without any editorial reason, disable this automatic update in your plugin settings.
Segment the sitemap by content type to manage indexing
A blog that publishes regularly accumulates dozens, sometimes hundreds of URLs. Putting everything in a single XML file is like packing clothes, dishes, and tools in the same box: technically possible, but hard to use.
Separating URLs by page type transforms the sitemap into a diagnostic tool. The idea is to create a sitemap index that points to several distinct files:
- A file for blog articles, which represents the main editorial content and changes most often.
- A file for static pages (about, contact, legal notices), rarely modified but necessary for indexing.
- A file for category or tag pages, whose SEO utility varies according to your internal linking strategy.
In Google Search Console, you can then submit each file separately. The indexing coverage report will show, for each sitemap, the number of submitted URLs versus the number of URLs actually indexed. A marked discrepancy on a specific content type reveals a targeted problem: insufficient quality, canonical errors, or weak internal linking.
HTML sitemap and XML sitemap: two distinct roles for your blog
The XML file is for bots. The HTML sitemap is for visitors. Confusing the two means optimizing for only one audience while both exist.
The HTML sitemap is a page on your site that lists your content in a readable way. On a blog, it often takes the form of a summary organized by themes or publication dates. Its value is twofold: it facilitates navigation for a reader looking for a specific topic, and it creates internal links to articles that might otherwise be buried in your archives.
When the HTML sitemap becomes truly useful
On a new blog with a handful of articles, this page doesn’t add much. Your menu and categories are sufficient. However, as soon as your blog exceeds fifty articles, a sitemap page allows visitors (and search engines) to browse all your publications without relying solely on internal search.
Some criteria for keeping an HTML sitemap effective:
- Organize links by category or theme, not just by date. A chronological listing loses its usefulness as the list grows.
- Limit the page to indexable content. No need to include legal notice or cookie policy pages.
- Update this page with each new publication. Most WordPress plugins do this automatically, but check that new articles are indeed appearing.
A clean XML sitemap combined with a well-organized HTML sitemap covers both sides of navigation: that of crawling bots and that of your readers. The XML ensures the technical discovery of your pages. The HTML provides an alternative reading path when the main menu is no longer sufficient.
The next time you publish an article, take thirty seconds to check that it appears in your XML sitemap and on your sitemap page. This simple reflex prevents content you’ve spent hours on from remaining invisible.
