Google News sitemap requirements mandate an XML file containing URLs for articles published in the last 48 hours. This specific file format assists Google in identifying content eligible for the News surface by highlighting metadata such as publication name, language, and the precise timestamp of the article. By adhering to these strict XML structures, publishers ensure that their content reaches the index with the necessary context for accurate display across search surfaces.
What are the specific technical requirements for a News sitemap?
A News sitemap must follow the standard Sitemap protocol while incorporating specific tags defined by Google. The file size is strictly limited to 1,000 URLs per individual sitemap to ensure efficient processing by the crawler. If a publication produces a higher volume of content, the system requires the creation of multiple sitemaps grouped under a single sitemap index file.
These technical files are not intended for archives or evergreen content. They serve as a temporary signal for breaking news. If the crawler encounters URLs older than two days within this specific feed, the system ignores them, which may trigger warnings in the Search Console interface regarding expired content entries.
For developers, this means building a dynamic script that prunes the XML list automatically. If a URL stays in the file beyond the 48-hour threshold, it becomes noise. High-frequency publishers must ensure their backend database triggers a removal event to keep the sitemap clean and compliant with Google’s freshness signals.
- Include only articles published in the last 48 hours.
- Use the tag for every URL entry.
- Specify the publication name and language settings accurately.
- Define the publication date using the W3C format (YYYY-MM-DDTHH:MM:SS+TZD).
- Keep the file size under 50MB and limit it to 1,000 URLs.
How do you structure the XML tags correctly?
The structure relies on the news namespace definition. Each URL entry must contain the mandatory publication object, which requires both the publication name and the ISO 639 language code. The title of the article is a required element, as is the publication date in the exact W3C format.
These specific tags provide the crawler with immediate context, allowing it to parse your content without needing to render the entire page layout. This is vital for high-frequency news sites where latency in rendering could delay the appearance of a story in the news feed. When you implement these tags, you reduce the workload on the crawler.
Consistency remains a key factor. Ensure the publication name matches exactly what appears in your Google Publisher Center settings. Any discrepancy between your metadata tags and your registered identity can lead to indexing friction. Audit your XML output frequently to ensure no encoding errors or broken characters disrupt the parser.
While you do not need to create a unique file for Discover, your general XML sitemap must be accurate and up to date.
Google Search Central
How Alien Road applies this technology
At Alien Road, we manage technical sitemap configurations by automating the entire generation process for our clients. We avoid manual file updates to prevent human error and ensure that every article is registered the moment it goes live. During a typical engagement, our engineering team audits the client’s CMS to ensure that the publication date and article title are pulled into the XML feed automatically.
We perform a validation check using standard XML validators to ensure the syntax matches the schema requirements perfectly. We then monitor Google Search Console to verify that the sitemap is processed without errors. For news publishers, we ensure that the sitemap index is submitted and that the coverage report shows no crawling issues, providing a clear path for content discovery.
In a typical client project, we integrate these XML feeds directly into the CI/CD pipeline. This ensures that when a developer pushes a new feature or layout, the sitemap generation logic remains intact. We document these processes so the client team can maintain transparency regarding how their content is being signaled to search engines.
Why is the 48-hour limit mandatory?
Google restricts the sitemap content to articles published within the last two days to maintain the freshness and relevance of the News index. After the 48-hour window, articles are automatically removed from the News sitemap, though they remain in the main Google index through regular crawling processes.
This distinction is vital for maintaining a clean technical profile and ensuring that the crawler spends its budget on fresh, breaking stories rather than stale data. If you attempt to keep articles in the News sitemap longer, the processing report in Search Console will likely flag these as invalid or redundant, which may decrease the overall trust signals for that specific file.
Stale content in a news feed provides a poor user experience. By strictly adhering to the 48-hour window, you signal to the search engine that your site is an active, current source of information. This discipline helps sustain high crawl priority for your domain, which is essential for breaking news cycles.
- Remove URLs from the News sitemap once they exceed 48 hours.
- Ensure article URLs remain accessible in the main XML sitemap for long-term indexing.
- Verify that your robots.txt file allows access to these files.
- Update the sitemap index file whenever a new sitemap is generated.
- Check your CMS cache settings to ensure the XML output does not serve cached, outdated versions.
What common errors should you avoid?
One frequent mistake involves including non-news pages in the dedicated News sitemap. Google expects only journalistic content in these files; including contact pages, category archives, or login portals causes errors in Search Console. Keep your News feed exclusively for articles.
Another issue is improper date formatting. If your CMS generates dates in a local timezone without offset, the crawler may misinterpret the publication time. Always force UTC or include the correct TZD offset in your W3C strings. Validating these strings against a schema validator will save significant time during the debugging phase.
Where to start this week
Check your current XML sitemap structure against the Google News requirements immediately. If you are a news publisher, verify that your CMS is outputting the required tags correctly. Start by testing your sitemap in a local development environment before deploying it to your live site to avoid indexing conflicts and to confirm that the W3C date formats are generated correctly. Monitor your Search Console coverage tab for at least 72 hours after deployment to ensure no new errors appear.