On a news site, the daily volume of publication makes any content discovery through simple hierarchical navigation obsolete. The sitemap page, whether in HTML format for readers or XML for bots, structures this mass of URLs and directs each visitor to the information they are seeking. Its role goes far beyond SEO: it determines the site’s ability to remain navigable as the archives grow.
HTML Sitemap and XML Sitemap: Two Technical Layers for a News Site
Confusing the HTML sitemap with the sitemap XML file is a common mistake, even in digital newsrooms. The XML file is a structured document intended for crawlers from Google, Bing, or any other search engine. It contains the URLs, their last modified date, and, in the case of news, specific tags for the Google News namespace.
The HTML sitemap, on the other hand, is a standard web page that readers consult directly. It organizes content by sections, subsections, and sometimes by publication period. On a media site, the HTML sitemap serves as a backup pathway when internal search fails or when a reader explores a cross-topic without knowing the publication date.
One can observe how the sitemap page of Monde Libre illustrates this dual logic: a thematic classification readable by a human, backed by a declared XML file on the server side. One does not replace the other, and removing the HTML sitemap on the grounds that the XML is sufficient deprives the reader of direct access to archived content.
Google News Namespace and Specific Tags in the News Sitemap
A standard XML sitemap uses the protocol defined by sitemaps.org. For a site indexed in Google News, an additional layer is necessary: the news namespace, declared via the xmlns:news attribute. This namespace allows for the addition of metadata specific to editorial processing for each URL.
The news-specific tags include the publication name, language, publication date, and article title. This sitemap is radically different from a standard sitemap intended to cover the entire site, as it only targets the most recent articles.
This temporal constraint has a direct consequence on the technical architecture: the News sitemap must be automatically regenerated with each publication. A CMS that updates this file only once a day introduces a discovery delay incompatible with the pace of a media outlet.
Required Elements in Each Entry of the News Sitemap
- publication name and language: identify the source and language of the content for ranking in Google News
- publication_date: precise timestamp of the upload, in W3C DateTime format, which determines the freshness perceived by the engine
- title: the title of the article as it should appear in the results, distinct from the page’s title tag if necessary
Structuring the HTML Sitemap for Reader Navigation
A news site that publishes several dozen articles a day cannot list every URL on a single page. The HTML sitemap must offer two complementary navigation axes: thematic and chronological.
The classification by section (politics, economy, culture, sports) allows the reader to explore a topic without knowing the publication date. The classification by period (month, year) suits those who have a rough idea of when an event was covered. Offering these two pathways on the same page reduces reliance on the internal search engine, which is often underperforming on media sites.
Transforming this page into an exhaustive list of articles makes it unusable. It is better to group links by sections and subsections, limiting the number of visible URLs per section. Pagination or an accordion system by year preserves readability without sacrificing depth.
Broken Links and Migrations: The Archive Trap
After a redesign or CMS migration, URLs change. If the HTML sitemap retains the old addresses, each broken link sends the reader to a 404 page. On a media site with years of archives, the number of dead links can reach proportions that make the sitemap page counterproductive.
Regularly checking the links in the HTML sitemap is an editorial maintenance task, not just a technical one. Removing or redirecting obsolete URLs after each migration ensures that the page retains its navigational utility.
Accessibility of the Sitemap and Content Discovery by Engines
The XML sitemap file is declared in two places: in the robots.txt file (Sitemap: directive) and in Google Search Console. For a news site, we recommend declaring the main sitemap and the News sitemap separately, as their update cycles and URL scopes differ.
A sitemap index (sitemapindex) becomes necessary when the number of URLs exceeds the limit per file. Large media outlets split their sitemaps by section or by year, which also facilitates diagnosis in case of indexing issues on a specific section.
- The main sitemap covers all permanent URLs: section pages, in-depth articles, institutional pages
- The News sitemap contains only recent articles, regenerated with each publication
- The images or videos sitemap, optional, signals rich content associated with articles
- The sitemap index references all these files and serves as the single entry point declared in robots.txt
This segmentation is not an architectural luxury. It allows isolating a crawl issue on a type of content without questioning the entire site’s indexing.
The sitemap, whether intended for readers or bots, remains an active component of the site. It requires maintenance proportional to the publication pace. A media outlet that treats it as a static file generated once for all ends up accumulating dead URLs on the HTML side and outdated articles on the XML side, two situations that degrade both navigation and visibility in search engines.
