How Often Should You Update Your News Sitemap? Set the Rule

A news sitemap is not a permanent index of your site.

It is a rolling list of very recent articles, and its value depends on how faithfully it reflects what you published in the last two days.

Google's guidance is explicit: update the sitemap as articles are published.

Keep only URLs created within the last two days, and remove older entries rather than letting them accumulate.

This article turns that guidance into a maintenance rule you can actually operate, including what to do when the sitemap goes empty and how to automate the cleanup.

The two-day rule, in plain terms

Google's news sitemap documentation says to include only recent URLs for articles created in the last two days.

Once an article is older than that, you should either remove its URL from the news sitemap or strip the news-specific metadata from the entry.

The article itself stays live on your site and can still rank in regular search; it simply no longer belongs in the news sitemap.

That two-day window is the core maintenance rule.

Everything else in this article follows from it: how often to touch the file, what to do on quiet days, and when automation is worth the setup effort.

How often should you actually update the file?

The practical answer depends on your publishing cadence.

But the rule is the same in every case: the sitemap should change whenever your set of articles from the last two days changes.

That means two distinct maintenance events, not one.

• On publication. Add the new article's URL with its news metadata as soon as it goes live. Google notes that news sitemaps are crawled as often as the rest of your site, so the same crawl behavior that reaches your pages also reaches the sitemap.
• On expiry. Remove entries as they cross the two-day mark. This is the step publishers most often miss, and it is the one that keeps the sitemap accurate.

If you publish several articles a day, you will touch the sitemap at least daily.

If you publish a few times a week, you may only need to update it on publishing days, because the two-day window will have already cleared older entries by the time you return.

The frequency of your edits should mirror the frequency of change in the underlying set, not an arbitrary calendar schedule.

Update the existing sitemap, don't create a new one

Google specifically advises updating your existing news sitemap with fresh articles rather than creating a new sitemap file with each update.

A rolling file with a stable URL is easier to monitor in Search Console.

You submit it once, and every update is just a change to the file's contents.

This also matters for tracking.

Google notes that a separate sitemap reserved for news articles can enable better tracking of news content in Search Console.

The sitemap report then reflects news URLs only.

If you mix news and evergreen URLs in one file, that separation blurs.

What to do when the sitemap goes empty

Here is the scenario that alarms publishers unnecessarily.

You remove URLs older than two days, you have not published anything in the last few days, and your news sitemap is now empty.

Search Console shows an Empty Sitemap warning.

Google's documentation addresses this directly: the warning exists to confirm the empty state was intentional on your part.

An empty news sitemap causes no problems with Google Search.

You do not need to pad the file with older articles to silence the warning.

Confirm it matches reality, and move on.

The mistake to avoid is the opposite one: keeping stale URLs in the sitemap to avoid an empty file.

That trades a harmless warning for a sitemap that misrepresents your recent coverage.

Removing URLs versus removing news metadata

Google offers two acceptable ways to age out entries, and the choice affects what your sitemap looks like over time.

• Remove the URL entirely. The sitemap shrinks and may become empty during quiet periods, which triggers the intentional-empty warning described above.
• Remove only the news:news metadata. The URL stays in the sitemap as a plain entry, but it no longer carries news-specific information. The file never appears empty, though it grows to include non-news entries.

If you choose the metadata-removal route, be aware that those retained URLs now belong to your general sitemap coverage rather than your news signal.

If you want the Search Console separation that a dedicated news sitemap provides, full URL removal keeps that boundary clean.

Automating the maintenance

Manual updates work while volume is low, but they fail predictably as publishing speeds up.

Someone forgets the expiry step, or a weekend publishing gap leaves the file stale on Monday.

Two automations cover the whole lifecycle.

• Add on publish. When a new article goes live, a workflow appends its URL and news metadata to the sitemap. The publication date in the metadata should be the original publication date, not the date it was added to the sitemap, per Google's tag guidance.
• Remove on expiry. A scheduled job runs daily, checks each entry's publication date against the two-day window, and removes or strips metadata for anything older.

With both in place, the sitemap maintains itself and the empty-sitemap case resolves itself too.

Quiet days produce an intentionally empty file, which is exactly what Google expects.

If weighing automation against manual upkeep, read how to automate content refreshes from performance data.

The same add-on-change, expire-on-schedule pattern applies there.

One caution on automation: a curated URL list or an automated pipeline does not by itself prove the output is correct.

Review the generated sitemap after setup and spot-check it after any CMS or template change, because a broken publication-date field will silently age entries wrong.

Getting the required tags right

Automation is only useful if each entry is valid.

Google requires a small set of tags for every news entry, and invalid required tags cause sitemap errors, so it is worth checking each one against the reference.

• news:news wraps each entry, and a sitemap may hold up to 1,000 of them. If you exceed that, split into multiple sitemaps.
• news:publication contains the publication name and language. The name must exactly match the name as it appears on your articles on news.google.com, omitting anything in parentheses.
• news:publication_date uses W3C format and must reflect the original publication date and time, not the sitemap addition time.
• news:title carries the article title.

When deciding which extensions to run, see the overview of which sitemap extensions to enable per content type.

It covers where the news extension fits alongside image and video tags.

Monitoring the sitemap after setup

Once the update rule is running, your remaining job is verification.

Submit the sitemap in Search Console and check the sitemap report after your first few automated cycles.

Look for three things: that new articles appear promptly, that entries disappear after two days, and that any Empty Sitemap warning coincides with a genuine publishing gap.

A recurring check makes sense here, and the cadence does not need to be aggressive.

The guidance on how often to check Google Search Console suggests a rhythm you can apply to sitemap health alongside your other monitoring.

The maintenance rule, summarized

Update the news sitemap whenever the set of articles published in the last two days changes: add on publication, remove on expiry, keep the same sitemap URL, and treat an empty file during a publishing gap as expected rather than broken.

That single sentence is the whole maintenance rule.

Everything else, including automation, tag validation and Search Console monitoring, exists to keep that rule running without manual effort.

If your workflow already touches a CMS and a marketing automation platform, wire the add and expire steps into that existing flow.

It is usually less work than adding a separate process, and it keeps the sitemap honest even when the newsroom is busy.

Source references: developers.google.com.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.