An article published three minutes ago that does not appear in Google News until the next day is a dead article. On a news site, the speed of indexing determines visibility. The dedicated news sitemap is the technical lever that accelerates this consideration by the bots.
We are not talking here about the classic sitemap displayed for visitors. The XML sitemap for news is a structured file, read by search engines, that signals in real-time the freshly published content. Its configuration differs radically from a standard sitemap, and it is precisely this difference that poses a problem for most online newsrooms.
48-hour window and 1,000 article limit: specific constraints for the news sitemap
When managing a news site, one quickly discovers that Google applies strict rules to the News sitemap. The file must only contain articles published in the last two days. Beyond that, the URLs have no place in this file (they remain in the site’s general sitemap).
The second constraint concerns volume: each file is limited to 1,000 news:news tags. For a newsroom that publishes massively, it is necessary to split the sitemap into several files and group them via an index. Ignoring this limit risks Google reading only part of the file, leaving recent articles off its radar.
For each URL, mandatory fields must be included in the XML: the exact name of the publication, the language, the date of first publication in W3C format, and the title of the article. The title must not contain the name of the media or the author. This last point is often misconfigured, leading to silent rejections in the Search Console.
To see how a news site concretely structures this hierarchy, one can consult the sitemap of La Gazette de Constantine and check how the URLs are organized by category and date.
News sitemap as a real-time feed: why automatic updates change everything
A static sitemap, regenerated once a day, is no longer sufficient for a news site. The trend observed among publishers in recent years is to treat the News sitemap as a dynamic feed, updated in the minutes following each publication.
Concretely, this means that the CMS (WordPress, Drupal, or custom system) must trigger the regeneration of the XML file as soon as an article is set to “published.” On WordPress, plugins like SEO Press or Yoast manage this automation. On a proprietary CMS, it is up to the developer to code this trigger.
A sitemap updated by the minute significantly reduces the indexing delay compared to daily regeneration. Feedback on this point varies depending on the crawl frequency granted by Google to the domain, but the principle remains the same: the fresher the file, the faster the bot crawls.
The pitfalls of automatic updates
Automating does not mean forgetting. Three errors frequently occur in newsrooms:
- Leaving articles in draft or “pre-publication” status appear in the sitemap, which sends Google URLs that return a 404 error or a protected page.
- Not removing articles older than 48 hours from the News sitemap, which violates the freshness constraint and can lead to a warning in the Search Console.
- Modifying the title of an article after publication without updating the
news:newstag in the XML, creating an inconsistency between the file and the actual page.
Mandatory XML tags for a Google News sitemap
The news sitemap uses a specific XML namespace that adds to the standard sitemap protocol. Without this namespace, Google simply ignores the news information and treats the file as an ordinary sitemap.
Here are the tags to include for each article:
news:publicationcontains two sub-tags:news:name(the exact name of the media as registered in Google News) andnews:language(ISO language code, e.g., “fr”).news:publication_dateindicates the date and time of first publication, in full W3C format (year-month-dayThour:minute:secondtimezone).news:titletakes the title of the article, without mentioning the media or the author. A poorly formatted title causes a silent rejection in the News index.
The publication name in the news:name tag must exactly match what is declared in the Google Publisher Center. An extra capital letter, a missing accent, and the link between the sitemap and the publisher account is broken.
Verification in the Search Console
After submitting the sitemap in Google Search Console (Sitemaps section, direct URL of the file), two indicators are monitored: the number of detected URLs and the number of indexed URLs. A significant gap between the two signals a formatting or content issue. The console also displays errors specific to news tags, allowing for quick correction of a faulty configuration.
HTML sitemap and XML sitemap: two distinct uses for a news site
The XML sitemap (intended for bots) and the HTML sitemap (intended for readers) are often confused. On a news site, both are useful, but they do not serve the same function.
The HTML sitemap is a navigation page accessible to visitors, listing sections, categories, and sometimes recent articles. It helps a lost reader find a section of the site. For SEO, it distributes internal linking to deep pages that the main navigation does not highlight.
The XML sitemap, on the other hand, is never seen by readers. It speaks exclusively to search engines. For a news site, multiple XML files are actually maintained: a general sitemap (all permanent pages), a news sitemap (articles from the last 48 hours), and possibly an images or videos sitemap if the site publishes them regularly.
Separating these files prevents fresh articles from being drowned in a mass of old URLs. Google assigns different crawl priorities depending on the type of sitemap, and this separation makes its job easier.
The technical point that often goes unnoticed: a sitemap index (file that lists all the sub-sitemaps) must be declared in the robots.txt file at the root of the site. Without this declaration, bots do not automatically discover the secondary files, even if they are correctly formatted.
