Google News is dropping indexed content from the News tab, and no one has found the pattern

The report came from Barry Schwartz at Search Engine Roundtable on September 3, 2026: over the past few days, several publishers noticed that content properly crawled, indexed and served in web search simply does not appear in Google's News tab. Sometimes it disappears for a while and reappears much later. Schwartz managed to replicate the behavior, but with an uncomfortable caveat: it looks completely random.

The example he documented is straightforward. A Wall Street Journal page showed up in the "All" tab of the results, but not in the "News" tab. He repeated the test on large and small sites, found the same symptom, and even caught it on his own domain: present in web search, absent from the News tab, and back the next morning. In one case he kept monitoring, the article started visible in both tabs and then dropped out of the News tab. In his words:

We've seen Google News visibility and delivery issues before, but this one feels different.

>

-- Barry Schwartz, Search Engine Roundtable

Google had not responded to the question posted on Bluesky by publication time. In other words: there's no official cause, no identified pattern, and no fix timeline. This is a field report, not an announcement, and it should be treated as such.

Why the News Tab Is a Separate Index

The technical point that developers and content engineers need to hold onto is that being indexed in web search does not guarantee presence in the News tab. These are different eligibility layers. Web search decides whether your URL enters the general index; the News tab applies additional criteria around editorial eligibility, freshness, news-source signals, and journalistic content classification. A URL can pass the first and fail (or fluctuate) in the second without anything on your end having changed.

That's why the symptom described is so unsettling: the content is there, servable, it appears in the "All" tab, and yet the News layer intermittently ignores it. This points to a problem in the News tab's serving/delivery pipeline, not in crawling or indexing. The crawler did its job; it's the decision to display it in the News tab that's failing.

How to Check If Your Domain Is Affected

The test Schwartz ran is reproducible and costs nothing. It's worth setting up a manual monitoring routine before touching any configuration:

1. Publish or identify a recent article that's already indexed.
2. Search for a unique excerpt of the title in quotes in the All tab.
3. Repeat the same search by clicking the News tab.
4. If it appears in "All" and disappears in "News", log the time and URL.
5. Redo the check at intervals (1h, 3h, 6h) to see if it reappears.

To automate the timestamp collection, you can query the cache/index with a simple search operator and cross-reference it with your CMS log:

# manual check of what is indexed under the domain
site:seudominio.com.br "trecho exato do título"

# on the server side, confirm that Googlebot has visited
grep "Googlebot" /var/log/nginx/access.log | grep "/noticia-slug"

If the log shows Googlebot fetching the URL and the page appears in web search, the problem isn't yours: it's on the News tab's delivery side. That changes the business response. There's no point redoing the sitemap, touching indexing tags, or resubmitting the URL, because the bottleneck isn't where those actions have any effect.

What This Changes for Those Who Depend on Discovery in Brazil

For Brazilian publishers, the News tab and Google News historically carry a significant share of discovery traffic, especially for factual and breaking-news coverage, where the peak happens in the first few hours. If a URL drops out of the News tab exactly during that window and only comes back "much later," as Schwartz reports, the damage is asymmetric: you lose exactly the window when the story was worth a click. Reappearing the next day doesn't recover the traffic lost at the peak.

Some practical steps, with no magic promise:

• Don't rely on a single discovery channel. Publishers with newsletters, push notifications, social distribution, and consistent presence on aggregators feel less of a jolt when one channel wobbles.
• Document before you react. A screenshot with the timestamp, URL, and both tabs side by side is what backs up a useful report (and it's what Google asks for when it opens an investigation into this kind of bug).
• Measure before-and-after in GA4/Search Console by filtering traffic by Google News origin and by publication time. If the click curve in the first few hours dropped while indexing remains normal, you have evidence that the problem is serving, not SEO.

Where This Report Does NOT Justify Panic

Two honest limits. First: this is a report of intermittent replication, with no confirmation from Google and no measured scale. There's no number stating how many publishers or what percentage of URLs were affected. Second: the behavior itself includes the content coming back to the tab, which suggests a transient delivery issue rather than a structural deprioritization. Anyone who goes and changes content architecture, alters publishing strategy, or rewrites structured data because of this may be treating a symptom that resolves itself and, worse, introducing changes with no evidence that they help.

The sober path is the same as always with a platform incident you don't control: monitor, document, and diversify, without mistaking a serving fluctuation for a quality problem in your own content. The SEO/GEO work you control still matters; what disappeared from the News tab, for now, is a problem on the other end of the wire.