A news site sometimes publishes dozens of articles per week, divided among thematic sections, briefs, and in-depth reports. Finding specific content within this flow requires knowledge of the site’s architecture, or at least having a readable map of it. The sitemap serves exactly this purpose: it exposes the structure of a site in the form of a hierarchical index, accessible to both visitors and search engines.
HTML Sitemap and XML Sitemap: two files, two distinct functions
The confusion between HTML sitemap and XML sitemap often arises. Both share the same name, but they target different audiences and serve different technical roles.
| Criterion | HTML Sitemap | XML Sitemap |
|---|---|---|
| Main Recipient | Human visitor | Crawling bot (Googlebot, Bingbot) |
| Format | Web page navigable with clickable links | File structured in XML tags |
| Access | Standard site URL (e.g., /sitemap/) | Declared in the robots.txt file or submitted via Search Console |
| Typical Content | Sections, categories, main pages | All indexable URLs, with modification date |
| Size Limit | No technical limit imposed | Maximum 50,000 URLs per file |
For a news media, the XML sitemap primarily serves to signal recent content to search engines. Google also limits the inclusion in news sitemaps to content published in the last 2 days, with a cap of 1,000 URLs. The HTML sitemap, on the other hand, provides a permanent panoramic view of all sections.
When consulting the Atlantic News sitemap, it is this HTML version that appears: a navigation page designed to help a reader quickly locate a section or article without relying on the internal search engine.
Navigation on a news site: what the sitemap resolves
The navigation menus of an information site prioritize the main sections (politics, economy, culture, sports). Older articles or specialized subcategories quickly disappear from the homepage.
The HTML sitemap acts as a comprehensive directory of the site’s sections. It allows users to find content that no longer appears in the visible editorial flows but remains online and accessible.
Three concrete situations where this page becomes useful:
- Finding a thematic section missing from the main menu, such as a seasonal report or a series of archived investigations
- Checking which categories actually exist on the site before launching a keyword search in the internal engine
- Identifying the depth of the hierarchy, meaning how many levels separate the homepage from a specific article
On a site that publishes at a steady pace, the internal search engine sometimes returns poorly ranked or overly numerous results. The sitemap offers a structured alternative, organized by editorial logic rather than algorithmic relevance.
Sitemap and SEO: the link between structure and crawling
For search engines, a well-constructed sitemap facilitates site crawling. Google discovers new pages either by following internal links or by reading the XML sitemap. When the internal architecture of the site contains orphan pages (no other page points to them), the sitemap remains the only access path for the bots.
This dimension takes on particular significance since the June 2026 update of Google Search Console. A “Generative AI Performance” report now allows measuring the visibility of pages in responses generated by Google’s AI. The cross-analysis between the sitemap hierarchy and presence in these AI responses opens up an optimization field that publishers are beginning to explore.
At the same time, publishers have had since that period a tool to block the reuse of their content in AI responses, mandated by the UK CMA, without impacting organic ranking. For a news site, the organization of the sitemap (distinction between sections open to AI and protected sections) becomes a full-fledged editorial management lever.
Headless Architecture and Sitemap: a technical challenge for media
Recent feedback on the redesign of institutional sites shows that adopting a headless architecture improves the automatic generation of the sitemap. With a headless CMS, content is stored independently of the display layer. The sitemap can then be generated dynamically with each publication, without relying on a plugin or manual update.
For a media outlet that publishes daily, this automation ensures that each new article appears in the XML sitemap within minutes, without human intervention. The HTML sitemap, in turn, reflects the structure of the sections as defined in the editorial back-office.
The consistency between these two files is not trivial. An XML sitemap that lists URLs absent from the HTML sitemap (or vice versa) can signal inconsistencies in the hierarchy to the crawling bots. These discrepancies complicate the indexing work and dilute the crawl budget allocated by Google to the site.
Criteria for a useful sitemap for a news site
A sitemap does not just need to exist. Its value depends on a few measurable characteristics:
- Automatic updates with each publication or deletion of an article, to avoid broken links
- Clear separation between the global sitemap (all pages) and the news sitemap limited to recent publications
- Readable hierarchy that reproduces the site’s editorial organization, not a simple alphabetical listing of URLs
- Correct declaration in the robots.txt file so that search engines can find it unambiguously
A well-structured HTML sitemap reflects the editorial choices of the media. By consulting it, one understands which themes are covered, how they are articulated, and what depth of content each section offers. This structural transparency benefits both the regular reader and the occasional visitor looking for a specific topic.
The next time the classic navigation of a news site is insufficient, the sitemap remains the most direct tool to map what actually exists on the site, without algorithmic filtering or editorial highlighting.