On a regularly publishing blog, the number of pages increases quickly. Articles are categorized by date, by category, by tag: the structure becomes opaque for both visitors and indexing bots. The sitemap comes into play at this precise stage, listing all accessible URLs in a structured manner. Its role goes beyond mere navigation convenience, as it also affects how search engines discover and process content.
What the lastmod tag changes for an active blog
Most guides on XML sitemaps focus on submitting the file and quickly gloss over the internal tags. This is unfortunate because the lastmod tag is the most useful signal for a blog that updates its old articles.
Google has clarified its position: the priority and changefreq tags, still present in many sitemaps generated by plugins, are simply ignored by its crawler. Only the last modification date (lastmod) is taken into account, provided it reflects a real change in content.
For a blogger, this means that changing a comma and regenerating the sitemap with a new lastmod date is pointless. In contrast, rewriting an outdated paragraph or adding a section to an old article, then allowing the sitemap to reflect this update, sends a relevant signal to the engine. The Lordy’s sitemap illustrates this principle with a clear structure where each URL is associated with its effective modification date.
A blog that publishes several times a week has every interest in ensuring that its sitemap does not list hundreds of URLs with the same date. This pattern triggers the crawler’s distrust, which ultimately ends up ignoring the lastmod entirely for that domain.
End of sitemap ping: what blogs need to fix
Since June 2023, Google no longer supports the sitemap ping endpoint. Specifically, the URL /ping?sitemap= that allowed notifying Google of a new sitemap no longer has any effect. Many WordPress plugins and CMS continue to send this ping with every publication, without the blogger realizing it.
Two submission methods remain valid:
- Declare the sitemap in the robots.txt file with a
Sitemap:directive followed by the full URL of the XML file. This method is passive but reliable, as the crawler checks robots.txt on every pass. - Submit the sitemap via the dedicated report in Google Search Console, which also allows tracking crawl errors and the number of indexed pages compared to the number submitted.
- Combine both approaches, which remains the most common recommendation in Google’s technical documentation.
The risk for a blog that relies solely on the disabled ping is that new articles are discovered only through internal linking or external links, which can extend the indexing delay by several days.
XML Sitemap and HTML Sitemap Page: two distinct functions
A common confusion is treating the XML sitemap and the HTML sitemap page as the same tool. However, their audiences and functions have nothing in common.
The XML sitemap is a technical file intended for bots. It contains only URLs, dates, and sometimes metadata about images or videos. No human visitor consults it.
The HTML sitemap page is aimed at readers. It organizes articles by theme, by section, or chronologically, and allows a visitor arriving on a deep page to understand the overall architecture of the blog. On a blog with several hundred articles, this page becomes an alternative entry point to the main menu.
The two formats complement each other. The XML sitemap helps the crawler find orphan pages (those that receive no internal links). The HTML sitemap page reduces the number of clicks needed to reach any article, improving navigation depth.
When the HTML sitemap page becomes truly useful
On a blog with twenty articles, an HTML sitemap doesn’t add much. The menu and categories are sufficient. However, after reaching a hundred publications, old articles become almost invisible without a dedicated navigation path.
A visitor looking for a specific topic among large archives will use the internal search if it exists, or leave the site. The sitemap page offers a third option: browsing all the content organized by theme, without relying on the internal search engine (often poor on small blogs).
Internal linking and sitemap: one does not replace the other
Internal linking (contextual links between articles) is often presented as the universal solution for navigation and SEO. It indeed plays a central role, but it has a structural limit: an article can only point to the content that the writer deemed relevant at the time of writing.
Subsequent publications, unless there is a voluntary return to old texts, receive no links from articles already online. The XML sitemap compensates for this gap by ensuring that every published URL is known to the crawler, even if no internal link mentions it.
The HTML sitemap plays a similar role for the reader. It acts as a safety net: if the internal linking is incomplete (which almost always happens on a blog run by a single author), the sitemap page catches the omissions by listing everything.
Field reports vary on the measurable impact of an HTML sitemap on bounce rate or session duration. The available data does not allow for a systematic conclusion. However, the effect of the XML sitemap on indexing coverage is well documented in Search Console reports: blogs that submit an updated sitemap generally see a reduced gap between submitted pages and indexed pages.
A blog that relies solely on good internal linking without an XML sitemap risks leaving orphan pages out of the index. A blog with a perfect sitemap but no internal linking offers frustrating navigation for readers. The two mechanisms cover different blind spots, and the sitemap, in both its forms, remains the most direct tool to ensure this.