Publishers report Google News sitemap data stuck in Search Console

Publishers began reporting in early September 2026 that the indexed pages report for their Google News sitemap in Search Console had stopped updating, even though their articles were still being crawled, indexed and shown in Google News. It is a narrower problem than an indexing outage: the sitemap submission was working, the articles were live, and only the report describing that work was behind.

What publishers reported#

On WebmasterWorld, a publisher posting under the handle Micha described the indexed pages report for their news sitemap as stuck around August 28-29, 2026, despite newer articles continuing to get indexed and show up in Google News search results. The same post said the publisher’s Google News source page, the publisher-branded page inside Google News, was updating extremely slowly compared to normal, with new articles taking longer than usual to appear there. A further complication reported in the thread: some articles were showing up in regular search results and in Top Stories carousels while still missing from the dedicated Google News tab.

Reporting lag, not an indexing failure#

The distinction matters for how a publisher should react. If a sitemap is genuinely not being read, or articles are genuinely failing to index, the fix is a technical one: check the sitemap for malformed URLs, verify robots.txt is not blocking the news sitemap path, and confirm the article markup still meets Google News requirements. None of that applies here. The sitemap was being read, and the underlying articles were indexed and visible in Google News, which points to the indexed pages report itself lagging behind the real index state rather than the index being wrong. Chasing a technical fix for a dashboard that has not refreshed yet would be wasted effort.

Google has not issued a public statement acknowledging the report as of this writing. The reports described here come from publishers on WebmasterWorld, not from a Google status page or a Google representative, so this should be read as a community-observed pattern rather than a confirmed and scoped incident.

Why we care#

A frozen indexed pages report is easy to mistake for an indexing problem, and a publisher who reacts to a mistaken read can burn time re-submitting sitemaps or auditing article markup that was never broken. The useful check before doing either is the one the WebmasterWorld reports point to: search for a specific recent article directly in Google News and in regular search. If it shows up there, the sitemap and indexing pipeline are working and the report is simply behind. Watch the Google News source page and the indexed pages count over the following days rather than treating a stale number as evidence of a new outage.