You’re looking for a specific page on a news site, but the main menu only has five or six sections. The articles you read yesterday seem to have disappeared beneath the stream of new posts. Most regular readers of online media run into this problem, and the sitemap is the tool that solves it.
XML sitemap and HTML sitemap: two mechanisms not to confuse
The term “sitemap” covers two distinct things. Understanding the difference explains why only one of them helps you navigate directly.
The XML sitemap is a file intended for search engines, not visitors. It lists URLs in a format that Google, Bing, and other crawlers can read to discover and index pages. You’ll never see it while browsing a site: it has no visual interface.
An HTML sitemap, on the other hand, is a page accessible from the footer or menu. It displays the site’s complete structure as clickable links, organized by section. It’s a table of contents that any visitor can browse.
These two formats often coexist on a news site. Browsing the Les News sitemap gives you direct access to all the sections and published content, clearly organized. The XML sitemap for the same site works behind the scenes to help Google index recent articles.

News sitemaps: the freshness requirement few readers know about
News sites handle a volume of publishing that corporate websites never reach. A news outlet may publish dozens of articles a day, which gives its sitemap a particular role.
For search engines: a two-day window
Google asks publishers to include only articles created within the past two days in their news sitemap. After that, the URLs must be removed from the file or have their “news” metadata removed. The date that counts is the original publication date, not the date of any subsequent update.
This rule has a direct consequence: an article corrected or expanded after its initial publication does not become “recent” again in the eyes of the news sitemap. Publishers must update the same file as new articles are published, rather than creating a new one for each cycle.
For readers: the HTML sitemap as the site’s memory
What the XML sitemap removes after two days, the HTML sitemap preserves. It’s where readers can find an article published the previous week, even if it disappeared from the homepage long ago.
For a news site, the HTML sitemap serves as a navigable archive once the editorial feed has pushed the information out of view. Without it, the only option is the site’s internal search engine, which requires remembering a specific keyword.
Keyboard navigation and screen readers: the sitemap as an accessibility shortcut
Have you ever tried navigating a site using only the Tab key? You have to move through every interactive element (link, button, field) one by one. On a content-rich news site, that can mean dozens of steps before you reach the section you want.
A sitemap reduces that journey to a single page. Screen reader users get a complete overview of the site’s structure without having to explore each section separately. Keyboard users can go straight to the section they’re interested in.
A well-built sitemap meets three requirements to be truly accessible:
- Every link uses descriptive text (not “click here” or a raw URL), so screen readers can announce it clearly
- The visual hierarchy reflects the site’s structure: main sections, then subsections, then individual pages
- Dynamic content (recent articles, latest videos) is included, not just static pages

Building a sitemap that stays useful as the number of pages grows
A sitemap with ten pages is easy to manage by hand. One with three thousand articles isn’t. Every online news outlet quickly faces the challenge of scaling up.
Automatic or manual generation
Most CMS platforms (WordPress, Drupal, or equivalents) offer plugins that automatically generate the sitemap whenever a new article is published. This approach ensures that every published article appears in the sitemap without human intervention.
Manual creation is useful in one specific case: when a publisher wants to exclude certain pages (legal notices, test pages, duplicates) or organize the visible structure differently from the site’s technical structure.
What to include and what to leave out
A sitemap isn’t a raw inventory of every URL on a site. To keep it easy to use, it should follow a few principles:
- Include main sections, subsections, and editorial content pages (articles, features, videos)
- Exclude utility pages with no navigational value: search results, login pages, and settings pages
- Update links to deleted or merged content to avoid 404 errors
- Group articles by topic rather than date alone, so visitors can find a subject without knowing when it was published
A sitemap that mixes technical pages and editorial content without distinction loses its value as a navigation tool. Separating what helps readers from what clutters the page makes all the difference between a useful tool and an unusable list.
On a news site, the sitemap remains one of the few pages that doesn’t age with the publishing cycle. When the homepage has already changed three times in a day, it’s the sitemap that helps you find what you’re looking for.



