A blog that publishes regularly ends up accumulating dozens, sometimes hundreds of pages. Without a centralized mechanism to link them, some of this content becomes invisible, both to readers and to crawlers. The sitemap, whether in XML or HTML format, serves as this internal mapping role. Its implementation raises specific technical questions, often misunderstood.
XML Sitemap and HTML Sitemap: Two Distinct Logics for a Blog
The confusion between XML sitemap and HTML sitemap persists in most guides. Both files share the same name, but they target different audiences and serve different functions.
The XML sitemap is a quality control file, not a raw inventory. According to Google Search Central documentation, it should contain only canonical, accessible, indexable URLs that respond normally. Redirects, 404 errors, noindex marked pages, and duplicates have no place in it.
On a WordPress blog, most plugins generate this file automatically, but without filtering: archive pages, rarely used tags, and mistakenly published drafts often slip in.
The HTML sitemap, on the other hand, is a visible page intended for visitors. It lists sections and articles according to a readable hierarchy. For a blog organized into thematic categories, this page provides an alternative entry point to the main menu. Consulting the sitemap of AllBlogger Tips gives a concrete overview of what this approach produces on an active blog.
Treating these two formats as interchangeable leads to mistakes: an XML sitemap overloaded with unnecessary pages dilutes the crawl budget, while a poorly structured HTML sitemap adds nothing to navigation.
Crawl Budget and Indexing: What the Sitemap Alone Does Not Solve
A common misconception is that it is enough to submit a sitemap to Google for all pages to be indexed. The reality documented by Google is more nuanced: a sitemap does not guarantee either crawling or indexing. It signals to crawlers the URLs that the publisher considers important, without any obligation for processing.
For a modest-sized blog (a few dozen articles), the sitemap mainly serves as a signal. Crawlers discover the majority of pages through internal links. In contrast, on a blog that exceeds several hundred posts, the sitemap becomes a prioritization tool. The lastmod tag, for example, can guide crawlers towards recently updated articles.
The lastmod Tag: Reliable Only If Honest
Google’s documentation specifies that lastmod is only useful if it reflects a substantial change in the main content, structured data, or links. Modifying a cosmetic detail (a comma, a space) to refresh the date amounts to sending a false signal. Crawlers eventually ignore this tag on sites that abuse it.
On WordPress, some plugins update lastmod with every save, even without any real change. Checking this behavior in the plugin settings helps avoid discrediting the entire sitemap.
Internal Links and Hierarchy: The Complement That the Sitemap Does Not Replace
The XML sitemap facilitates the discovery of pages, but it is the internal linking that determines their relative weight. An orphaned article (without incoming links from other pages of the blog) is unlikely to be crawled as a priority, even if it appears in the sitemap.
Three complementary mechanisms deserve special attention:
- Contextual links between articles allow crawlers to understand the thematic relationships between contents, and help readers continue their reading
- Navigation through categories and subcategories structures the blog’s hierarchy, which helps search engines identify pillar pages
- The HTML sitemap provides a safety net: if an article is not linked to any active category, it remains accessible from this centralized page
A blog whose internal structure relies solely on the XML sitemap, without editorial linking, resembles a library where the books are cataloged but never shelved.
Submitting a Sitemap in 2024: What Has Changed on Google’s Side
The automatic sitemap notification mechanism (the “ping”) was deprecated by Google on June 26, 2023. Requests sent to the old endpoint now return a 404 error. For bloggers who used automatic submission tools, this change means revisiting their method.
Two channels remain operational:
- The declaration of the sitemap in the robots.txt file, via the Sitemap: directive followed by the full URL of the XML file
- Manual or scheduled submission via Google Search Console, which also allows checking the number of submitted, discovered, and indexed URLs
The Search Console remains the only tool that provides feedback on the actual state of indexing. A submitted sitemap without follow-up offers no visibility on ignored or erroneous pages.
Frequency of Sitemap Updates
On a blog that publishes several articles per week, the sitemap should regenerate automatically with each publication. Most modern CMSs manage this process natively. On a less active blog, a weekly regeneration is sufficient. The goal is for the sitemap to accurately reflect the actual state of the blog at all times, without ghost URLs or deleted pages.
The sitemap, whether XML or HTML, is not a miracle tool. It works as a complement to internal linking, content quality, and thoughtful hierarchy. Blogs that make the most of it are those that integrate it into a comprehensive maintenance routine, regularly checking the consistency between the sitemap, the pages actually online, and the data reported by the Search Console.
