How to Create a News Sitemap

Part of the SiteMap Series

In the previous lesson, you saw how video sitemaps work for self-hosted video content. News sitemaps follow the same namespace-extension pattern (add xmlns:news to the urlset declaration, then add specialised elements inside each url block) but apply to a much narrower audience: publishers that have been approved for Google News.

If you run a news publication, a journalism site, or a content operation that publishes time-sensitive editorial content, a news sitemap accelerates discovery for the first 48 hours after publication, which is the window where news content has the most search value. If you run a blog, a marketing site, or any other type of content operation, a news sitemap is not the right tool, and adding one will not get your content into Google News.

This lesson covers who actually needs a news sitemap, what the simplified current XML elements look like (Google deprecated several optional fields over the past few years), how to create one through the main implementation paths, the strict limits that make news sitemaps different from regular sitemaps, common gotchas, and how to submit and validate.

Who actually needs a news sitemap

A news sitemap is only useful if your site is approved for Google News. That approval is a separate process from regular Google indexing, handled through Google Publisher Center, with editorial and technical requirements that go beyond what regular sites need to meet.

Three things need to be true before a news sitemap helps you.

Your site is approved for Google News. Approval requires applying through Google Publisher Center, demonstrating original journalistic content, providing clear author bylines and publication dates, meeting technical accessibility standards, and following Google’s News content policies. Approval is not automatic, and many sites that produce useful content do not qualify.

You publish time-sensitive editorial content. News sitemaps are designed for the news cycle: articles where the value is concentrated in the first 24-48 hours after publication. Evergreen content, opinion pieces with no time pressure, and reference material do not benefit from a news sitemap, and may not even be eligible.

You publish frequently enough for the sitemap to do work. A news sitemap that gets updated once a week has limited value because most entries will already be outside the 48-hour window by the time the next update arrives. Publishers updating multiple times per day see the most benefit.

If those three conditions do not apply, time spent building a news sitemap is better spent on standard sitemaps and the other Module 2 fundamentals.

For approved publishers, the AI Search era adds urgency to the news sitemap question. Multimodal AI assistants and AI-augmented search surfaces increasingly pull from news content for queries about current events, ongoing situations, and recent developments. Fast indexation through news sitemap submission helps your content appear in those AI-surfaced answers while the topic is still relevant.

What news sitemap elements look like

The news sitemap protocol has been substantially simplified over the past several years. Google deprecated several optional fields (genres, keywords, stock_tickers) that were originally part of the spec but are no longer used. The current required spec is short.

A complete news sitemap entry looks like this:

<url>
  <loc>https://example.com/news/election-results-2026/</loc>
  <news:news>
    <news:publication>
      <news:name>Example News</news:name>
      <news:language>en</news:language>
    </news:publication>
    <news:publication_date>2026-06-04T08:00:00+00:00</news:publication_date>
    <news:title>Election Results Confirmed in Three Key Districts</news:title>
  </news:news>
</url>

Three required elements.

news:publication. A container for two sub-elements: news:name (the name of your publication as it appears in Google News) and news:language (ISO 639-1 language code, like en, fr, or es). The name should match exactly what is registered in Google Publisher Center.

news:publication_date. When the article was published, in W3C datetime format (2026-06-04T08:00:00+00:00). This date must be accurate. Articles published more than 48 hours ago should not appear in the news sitemap.

news:title. The article headline, plain text, matching what appears as the article title on the page.

That is the entire required spec. The deprecated optional elements (genres, keywords, stock_tickers) no longer affect indexing and can be removed from existing sitemaps without consequence.

How to create a news sitemap

Three implementation paths, with news-specific notes for each.

1. Using a WordPress plugin

WordPress has stronger plugin support for news sitemaps than for video, because the news publishing market is significant and several plugins target it specifically.

Yoast News SEO is a paid add-on to Yoast SEO. It generates news sitemaps automatically, handles the 48-hour window (articles drop out of the sitemap once they exceed the window), and integrates with Yoast’s article schema for richer Google News signals. Settings live under SEO > News.

Rank Math News SEO is part of the Pro tier. It includes news sitemap generation, automatic 48-hour pruning, and editorial date handling. Settings live under Rank Math > Sitemap Settings > News Sitemap.

All in One SEO News Sitemap is available in the Pro tier. Same automatic generation and pruning logic. Settings under All in One SEO > Sitemaps > News Sitemap.

For all three, the plugin needs to know which post types qualify as news articles (typically just post, but news sites often have a custom article or news_article post type), which categories or sections to include, and the publication name and language to use in the metadata.

2. Using a news-specific platform

News publishers running on dedicated platforms typically get news sitemap generation built into the platform itself, often with better handling of editorial workflows than generic WordPress plugins.

WordPress VIP includes news sitemap support through configuration rather than plugins. The platform handles the 48-hour pruning at the infrastructure level.

Newspack (the WordPress.com platform aimed at small and mid-sized news publishers) includes news sitemap generation by default, alongside other Google News integration features.

Custom news CMS platforms (Arc XP, Brightspot, others used by larger publishers) typically generate news sitemaps as part of their core publishing pipeline. Configuration usually happens through admin settings rather than code.

For publishers on these platforms, the implementation question is less “which plugin” and more “which settings to configure”. The generation logic is already wired in.

3. Manually with XML

For smaller publishers who want full control, the manual approach is workable but maintenance-intensive because of the 48-hour pruning requirement.

Start with the standard URL sitemap structure from Lesson 5 of Module 2: How to Build a Website Sitemap Manually with XML. Add the news namespace declaration to the opening <urlset> tag:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">

Then add <news:news> blocks inside each <url> for articles within the 48-hour window.

The maintenance burden is the catch. Manual news sitemaps need to be regenerated frequently (ideally on every publish, and at least daily) to add new articles and remove articles that have exceeded the 48-hour window. A cron job or scheduled task is the realistic minimum; doing it by hand is not sustainable for active publishers.

News sitemap limits and rules to know about

News sitemaps have stricter limits than regular sitemaps.

Maximum 1,000 URLs per news sitemap. This is far lower than the 50,000 URL limit for regular sitemaps. For active news publishers, this means a single news sitemap typically holds 1-3 days of articles at most.

Articles must be less than 48 hours old. Articles older than 48 hours should be removed from the news sitemap. They can still appear in the regular sitemap (and should, for ongoing indexing), but the news sitemap is strictly for fresh content.

Publication name must match Google Publisher Center. The <news:name> value should match exactly what is registered for your publication. Mismatches can cause the articles to be ignored.

Language codes must be valid ISO 639-1. Use the two-letter code (en, fr, es, de, pt) for most languages. Chinese is the exception, using zh-cn for Simplified and zh-tw for Traditional.

Standard sitemap limits still apply. The 50MB uncompressed file size limit still applies, though for news sitemaps you will hit the 1,000 URL limit long before the file size limit.

One news sitemap per language section is recommended. If your publication produces content in multiple languages, separate news sitemaps for each language give the engines cleaner signals than one mixed-language sitemap.

Common gotchas to avoid

Five issues come up regularly with news sitemaps.

1. Submitting a news sitemap before being approved for Google News

A news sitemap without Google News approval does nothing. The engines will not treat the URLs as news articles, and the publisher will not appear in Google News results. The fix is to apply through Google Publisher Center first, get approved, then build the news sitemap. Many publishers do this in the wrong order and then wonder why the sitemap is not producing results.

2. Articles older than 48 hours staying in the news sitemap

Articles that exceed the 48-hour window should be removed from the news sitemap. Leaving them in does not directly harm indexing, but it dilutes the signal and suggests the sitemap is not being actively maintained. The fix is automatic pruning, either through a plugin that handles it or through a regenerated sitemap on a regular schedule.

3. Publication name mismatch with Google Publisher Center

The <news:name> element must match the publication name registered in Google Publisher Center. “Example News” and “ExampleNews” and “Example News Daily” are treated as different publications. The fix is to copy the name verbatim from Publisher Center into the sitemap configuration.

4. Non-news content included in the news sitemap

Marketing pages, evergreen tutorials, opinion pieces with no time pressure, and other non-news content should not appear in the news sitemap. Including them sends mixed signals about what counts as news on your site and can hurt the credibility of the actually-news content. The fix is to filter the sitemap by content type or category, ensuring only news articles are included.

5. Date format errors causing entries to be ignored

The <news:publication_date> element must be in W3C datetime format with a timezone (2026-06-04T08:00:00+00:00). Dates in other formats (June 4, 2026, 2026/06/04, 06-04-2026) cause the entry to be ignored. The fix is to use a generator (plugin or script) that emits the correct format consistently rather than constructing dates manually.

How to submit and validate your news sitemap

Submission goes through Search Console like other sitemaps. The submission process from Lesson 7 of Module 2: How to Submit Your Website Sitemap to Google Search Console applies here too, just with the news sitemap URL instead of the regular sitemap URL.

Google News also surfaces news sitemap activity in Google Publisher Center, where approved publishers can see how their content is being indexed for the News surfaces specifically. This is different information from the Search Console Sitemaps report and worth checking alongside it.

Validation has three news-specific checks beyond the standard sitemap validation from Module 2.

First, confirm the news namespace is declared (xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"). Without it, the engines treat the news elements as invalid XML.

Second, check that all articles in the sitemap are within the 48-hour window. A simple way to verify: open the sitemap, look at the publication_date values, and confirm none are older than 48 hours.

Third, monitor the News tab in Search Console Performance reports once the sitemap has been processed. After indexing, you should see impressions and clicks specifically for the Google News surface. If your articles appear in regular search but not in the News tab, that signals an indexing problem specific to the news content.

Where this leaves us

You can now create a news sitemap for a Google News-approved publication, manage the 48-hour window appropriately, and understand why the narrower scope and stricter limits make news sitemaps a specialised tool rather than a general one. Combined with the image and video sitemap knowledge from the previous lessons, you have full coverage of the three namespace-extension sitemap types.

Hreflang in sitemaps comes next, and it works on a fundamentally different principle. Instead of adding namespace-specific metadata to describe content (an image, a video, a news article), hreflang in sitemaps uses xhtml:link elements to declare relationships between language and regional variants of the same content. The structure is different, the use case is different (international SEO rather than content discovery), and the audience is broader (any site with multi-language or multi-region content, not just publishers or video hosts).

Up next: How to Use Hreflang in Sitemaps for International SEO →

This is Module 3: Lesson 4 of The Sitemap Series, a technical SEO series on sitemaps from first principles, built for the AI Search era.