Google News sitemap includes old articles? Fix the window
Keep a news sitemap aligned with original publication times. Check the two-day window, timezone handling, article limits, and the ordinary sitemap separately.
By Crawlito · 5 min read
In short
- Google's news sitemap guidance limits news entries to articles created within the last two days.
- A general archive can remain in the ordinary sitemap after its news metadata expires.
- Refreshing a file or correcting an article does not create a new original publication date.
On this page
- Identify the timestamp the generator actually uses
- Test the recent-news boundary deliberately
- Preserve the ordinary archive
- Validate publication identity and entry limits
- Compare the generated file with the public response
- Check a delayed publication from the editor's queue
- Frequently asked questions
- Check a recent article
If your Google News sitemap keeps old stories or drops recent ones, compare its inclusion rule with each article's original publication timestamp and timezone. Google asks publishers to include news articles from the last two days, then remove the older URL or its news-specific metadata. Keep ordinary archive discovery intact through the site's general sitemap. Google’s news sitemap guidance
Identify the timestamp the generator actually uses
Choose a recent article, an article near the edge of the inclusion window, and an older article that was corrected today. Record original publication, modification, scheduled publication, and the time the sitemap was generated. A CMS might expose all four values with similar labels, and a generator can easily select the last-modified field by mistake.
Read the published byline and the news metadata together. The news publication date describes the original article publication. A site rebuild or minor edit should not make a month-old story appear newly published in the news sitemap. The article date guide explains how to keep these meanings separate across visible and structured fields.
Inspect the data source in the release process. A database timestamp stored without an offset can be interpreted differently by the CMS, build server, and sitemap service. Write down the intended timezone and convert test values explicitly. A local calendar day displayed to editors and an absolute timestamp used by the generator can both be valid when their relationship is well defined.
Test the recent-news boundary deliberately
Use a fixed generation time in a development fixture and create articles just inside and just outside the intended two-day window. Include one scheduled for the future and one published near local midnight. Record the expected inclusion for each before running the generator. A repeatable fixture is easier to interpret than testing while the real cutoff moves.
| Fixture | What to verify |
|---|---|
| Recently published story | Included with its original publication date |
| Story leaving the window | News metadata removed or URL omitted as intended |
| Old story corrected today | Original publication preserved |
| Future scheduled story | Excluded until actually published |
| Quiet publishing period | Empty news output handled intentionally |
Google notes that a news sitemap can become empty when no recent articles qualify, and that an empty-sitemap warning in that situation does not itself cause a Search problem. Do not keep outdated stories in the file solely to avoid that expected condition. Give the operations team a way to distinguish an intentionally quiet period from a broken query.
Inspect the boundary result in the raw XML. A timezone formatter can output the right-looking date in the page while serializing the wrong instant in the sitemap. Compare the values after parsing, with the intended offset or UTC representation. Keep the fixture independent of the machine's default timezone.
Preserve the ordinary archive
An article leaving the news window can remain a useful public page. Check its ordinary sitemap entry, category links, and archive navigation. Removing news metadata should not unpublish the article or remove it from every discovery source. A generator that shares one “recent” filter across all sitemap types can unintentionally hide the rest of the publication.
If the publisher combines standard and news entries in one XML file, inspect whether older URLs remain with their general sitemap information after the news:news element is removed. If it uses a dedicated news sitemap, confirm the ordinary sitemap still covers the intended archive. The general sitemap guide explains the role of those maintained canonical URLs.
Check a quiet period explicitly. With no qualifying news, the archive should still work, the latest publication should still have a public URL, and a new article should enter the next generated news set when it becomes public. This test catches code that treats an empty query as a reason to stop generating future updates.
Validate publication identity and entry limits
Review the publication name, language, original date, title, and URL in a few entries. They should match the article and the publication's documented identity. A syndicated or translated article may require particular editorial handling; use the actual publication record rather than deriving every field from a global setting that fits only one edition.
Google limits a news sitemap to 1,000 news entries. If the recent window contains more, split the output using the documented sitemap approach. Count qualifying news elements, not only the number of files or top-level sitemap entries. A filename indicating a daily batch can still contain too many records after an unusually busy publication day.
Check escaping and namespaces with an XML parser. An article title containing an ampersand or quote can expose a serialization bug that plain-text examples miss. Save one real title with punctuation in your acceptance fixture. The sitemap partition guide describes how to verify multiple files without losing records at their boundaries.
Compare the generated file with the public response
After deployment, fetch the live news sitemap through the public hostname and parse it. Confirm the recent, boundary, and corrected examples appear or disappear as expected. An old cached file can keep yesterday's entry set even when the generator's local output is correct. Record generation time and public retrieval time separately.
Follow an included article URL and verify the intended page, canonical address, visible date, and readable body. A news entry pointing to an editor preview or an unpublished route is a separate publishing defect. Test the same URL without cookies so the result reflects what a fresh reader can retrieve.
Retain the final entry count and a few representative identifiers with the release logs. Monitor the behavior across the next normal publication and the next quiet period. Those two states exercise the generator's ongoing operation, while a one-time successful export establishes only that it worked for that particular input.
Check a delayed publication from the editor's queue
Imagine an article created in the CMS on Monday but held for publication until Thursday. If the sitemap uses record creation time, it may consider the story too old before readers can first open it. Compare creation, scheduled release, and actual publication fields for one such article. Confirm which field the editorial system maintains as the original public publication time.
Test a scheduled story that is postponed again before launch. It should remain outside the live news output until publication, and its eventual entry should describe the actual published article. Use the same fixture to verify a previously published story that is temporarily withdrawn and restored. Ask the editorial owner which historical date remains authoritative for that case, and preserve it consistently across the byline and sitemap.
Frequently asked questions
Should I give a corrected old story today's publication date?
Preserve its original publication date and represent the correction accurately. A changed article and a newly published article are different editorial events.
Does a news sitemap guarantee inclusion in Google News?
It supplies discovery information for eligible content. Google makes its own decisions about crawling and presentation.
Should I create a new sitemap file for every story?
Use the publisher's maintained sitemap workflow and Google's current guidance. Verify that the live file updates reliably as the qualifying set changes.
Check a recent article
Run the free page check on a story currently included in the news sitemap. Compare its public content and dates with the XML entry you verified.
Filed under Structure and schema. Topics: sitemaps, google, publishing