SitemapFixer for News Publishers
In news, minutes matter. A breaking article that takes two hours to hit Top Stories is an article that missed the window. The news sitemap protocol is strict, unforgiving, and easy to break with a CMS update. SitemapFixer audits your news sitemap against Google's exact specification so you catch freshness regressions before they cost you impressions.
The sitemap challenges news publishers face
- Strict Google News sitemap protocol - missing news_title, publication_date, or language tags break inclusion
- Freshness signals degrading when articles older than 48 hours linger in the news sitemap
- Hourly recrawl expectations - Google expects near real-time updates and will deprioritize stale feeds
- Articles silently missing from Top Stories because of sitemap structure, not content quality
- The 1,000-URL cap on news sitemaps forcing careful rotation of which articles are included
- CMS publishing pipelines producing malformed publication dates (timezone, ISO-8601 format)
How SitemapFixer helps
SitemapFixer validates your news sitemap against the exact Google News protocol, checking every required tag, every publication_date format, and every URL for compliance. When something breaks after a CMS release, you find out immediately - not after a week of missing Top Stories placements.
Freshness regressions are the most common hidden issue. The tool flags articles older than 48 hours that are still in the news sitemap, inconsistent lastmod timestamps that confuse Googlebot, and URLs that return 4xx or are behind a paywall without the appropriate tags.
For publishers running multiple verticals or brands, each news sitemap can be audited separately, so the sports desk and the politics desk can diagnose their own pipelines.
Key features for news publishers
- Full Google News sitemap protocol validation (news_title, publication_date, language, genres)
- Freshness window checks - flags articles older than 48 hours still sitting in the news sitemap
- Publication date format validation against ISO-8601 and timezone-correctness checks
- 1,000-URL cap monitoring so you know when to rotate older articles out
- 4xx and paywall-without-schema detection for articles that would never index
- Hourly recrawl readiness check - verifies lastmod signals that drive near real-time crawl
Real example
A regional news publisher saw a sharp drop in Top Stories appearances after a CMS migration. The content was fine, the articles were ranking in regular search, but Top Stories traffic had fallen off. SitemapFixer caught the cause in the first audit: publication_date tags were being written in the server timezone instead of UTC, and Google was interpreting every article as hours older than it actually was. A one-line fix in the CMS template restored Top Stories placements within two days.