Why does Google require a separate News sitemap to index your articles?

What sets a standard sitemap apart from a News sitemap?

The News sitemap addresses specific constraints related to the lifecycle of a news article. Unlike the standard XML sitemap that lists all pages of a site without a temporal hierarchy, the News sitemap only includes content published within the last 48 hours. Google prioritizes crawling this flow to feed Google News in real time.

Mandatory tags include publication_date, title, and optionally access to indicate paid content (subscription, registration). This granularity allows Google to classify the article immediately without having to analyze the entire DOM, speeding up indexing in a context where every minute counts.

Why does Google emphasize this technical separation?

Let’s be honest: Google already crawls your site via the main sitemap. But for News, priority is given to freshness and speed. A standard sitemap often contains thousands of URLs with variable update frequencies, which dilutes the signal. The News sitemap isolates the hot flow and ensures that Googlebot News (which is distinct from the standard Googlebot) gets directly to the new content.

Another reason is the management of the paywall. Publishers who monetize their articles must explicitly signal restricted content via the <access> tag. Without a News sitemap, Google might interpret a paid article as cloaking or low-quality content if the bot only sees a snippet. The News sitemap removes any ambiguity upon discovery.

Does this recommendation apply to all news sites?

Technically, no. Only Google News approved sites have an interest in deploying a News sitemap. If you are not in the News index, this sitemap will be ignored. Google does not automatically validate all submitted News feeds: you must first meet editorial criteria (original content, publication frequency, expertise).

But be cautious: even for a validated News site, the sitemap does not guarantee appearance in top stories or in the News tab. It facilitates discovery, not ranking. Content must still maintain high editorial quality, with strong EAT signals.

• The News sitemap only lists articles less than 48 hours old, unlike the standard sitemap which may contain the entire catalog.
• Specific tags (publication_date, access, genres) enable immediate classification by Googlebot News without a complete page analysis.
• Speed of indexing is the main benefit: an article can appear in News within minutes if the sitemap is well designed.
• Without a News sitemap, Google may ignore your recent articles or discover them too late to have an impact on current events.
• The <access> tag is crucial for paywalls: it avoids cloaking penalties while allowing you to appear in News with a “subscription required” mention.

Is this statement consistent with observed practices in the field?

Yes, but with important nuances. Publishers who have implemented a well-structured News sitemap indeed notice a faster indexing of their articles. We’re talking about a few minutes versus several hours through the standard crawl. But this difference only holds for sites already validated in Google News. For others, the News sitemap is simply ignored. [To verify]: Google does not publicly share the exact criteria for validating a News feed, and many publishers face rejections without detailed explanations.

Specifically, I have seen sites with a flawless News sitemap that never appear in News because Google considers their editorial line insufficiently distinct or their publication frequency too low. The sitemap is necessary but not sufficient. It does not compensate for a lack of EAT signals or sector authority.

What common mistakes are made with News sitemaps?

The first mistake: including content older than 48 hours. Google silently rejects these URLs, which dilutes the quality of the feed. Some CMS generate the News sitemap automatically without strict temporal filtering, resulting in a file containing 200 URLs with 150 being expired. The result: Google downgrades the crawl priority of the entire sitemap.

The second mistake: neglecting the <publication_date> tag or filling it with inconsistent timestamps (misconfigured timezone, modification date instead of publication date). Google relies on this date to assess freshness. If it is incorrect, the article may be classified in the wrong time window and lose visibility. The third mistake: not declaring paywalls. A locked article without an <access> tag risks being viewed as misleading content.

In what cases is this technical lever insufficient?

The News sitemap does not resolve issues of editorial quality. If your articles are merely aggregations of AFP dispatches without added value, Google will not push them into News even with a perfect sitemap. The News algorithm favors original content, with distinct editorial angles and identified authors.

Another limit: competition. On a hot topic (elections, natural disasters), thousands of articles are released simultaneously. Having a News sitemap allows you to enter the race, but only sites with strong News authority (history of citations, backlinks from other media) will score the top stories. The sitemap facilitates discovery, while ranking remains an editorial and authority battle.

How to create and submit an effective News sitemap?

The first step: generate an XML file compliant with the Google News protocol. The format is stricter than the standard sitemap. Each URL must include a <news:news> block with at least <news:publication> (name and language), <news:publication_date> (ISO 8601 with timezone), and <news:title>. If your CMS does not do this natively (like WordPress with Yoast or RankMath, for example), you need to develop a script or use a specialized plugin.

Next, submit the sitemap via Google Search Console in the section dedicated to sitemaps. Google crawls this file several times an hour for active News sites. Ensure that the file is accessible over HTTPS, not blocked by robots.txt, and automatically updates with each new publication. A static News sitemap that does not evolve is a negative signal for Google.

What technical mistakes should you avoid at all costs?

Never list more than 1000 URLs in a News sitemap. Google recommends limiting it to a few hundred to maintain signal quality. If you publish more than 1000 articles in 48 hours, segment by theme or language. Also, avoid mixing editorial content (News articles) with evergreen content (guides, product pages): the News sitemap should remain strictly dedicated to current affairs.

Another pitfall is 301/302 redirects. If the URL in the News sitemap redirects, Google may ignore the entry. Always publish the final canonical URL. Watch for 404 and 5xx errors: a News sitemap with too many dead URLs loses credibility, and Google reduces the crawl frequency.

How to check if the News sitemap is working correctly?

Use Search Console > Sitemaps to track the number of discovered URLs vs submitted. If there's a large gap, Google is rejecting some entries (common reasons: publication date > 48 hours, invalid XML format, URLs in 404). Complement this with the URL inspection tool to verify that your latest articles are indexed quickly after publication.

Also test the effective presence in Google News. Search site:yourdomain.com in the News tab. If your recent articles do not appear while the sitemap is being crawled, it’s likely a problem with editorial validation or quality. The sitemap alone does not guarantee visibility; it simply opens the door.

• Generate a News sitemap compliant with the protocol (tags <news:news>, publication_date ISO 8601, access for paywalls)
• Limit the file to articles less than 48 hours old and a maximum of 1000 URLs
• Submit via Search Console and check for regular crawling (multiple times an hour for active sites)
• Exclude any evergreen or non-editorial content from the News sitemap
• Monitor for 404 errors, redirects, and invalid XML format in Search Console
• Test the effective presence of articles in Google's News tab to validate effectiveness beyond technical indexing