If Google News traffic vanished, compare News with Web before editing articles

If Google News traffic vanished, compare News with Web before editing articles

A Search Console comparison separates a Google News or Discover serving problem from a broader ranking loss before you rewrite article pages.

A Google Search traffic drop can come from one search surface while another keeps working. In a September 3 report, Search Engine Roundtable described publishers whose new articles were crawled, indexed, and visible in the regular Web results while disappearing from the News tab for hours or days; the author reproduced the behavior and later saw articles return. 1
WebmasterWorld reports from September 1–7 describe the same kind of split from another angle: some publishers saw rankings rise while clicks, News traffic, or Discover traffic fell. The thread also contains counterexamples, including a member who found Google News working normally. 2 Google's Search Status Dashboard lists the August 2026 spam update as the latest ranking incident. 3

The one action: compare News with Web in Search Console

Use this check if your site publishes timely articles and your pages appear in regular Google Search while Google News or Discover traffic becomes delayed, intermittent, or unusually low. A fresh r/SEO troubleshooting thread also recommends describing a loss by pages, queries, and other dimensions before choosing a fix. 4
  1. Open Search Console and choose Performance > Search results. Select the property that contains the affected articles.
  2. Set a comparison date range. Compare the days when the News or Discover traffic changed with an earlier period of similar length. Keep the dates identical for every view.
  3. Run the Web view first. Record clicks, impressions, CTR, and average position. In the table, open Pages and identify the article URLs that changed most.
  4. Switch the Search type filter to News. Record the same four metrics for the same dates and the same pages. Search Console supports separate Web, Image, Video, and News views, along with Pages and Queries dimensions. 5
  5. Write one line that names the split. For example: Web steady; News down; pages affected: /news/.... Add the top queries when the change is concentrated in a small group of articles.

Read the result before touching article templates

The comparison gives four useful patterns:
  • Web steady, News down: The current problem sits on the News surface or its serving pipeline. Keep article text and templates unchanged while you watch whether the affected URLs return to News.
  • Web down, News down: The loss reaches both surfaces. Move to Google's broader traffic-drop checklist: inspect pages, queries, search type, indexing, security, spam, and seasonality. 6
  • Web steady, News steady, Discover down: The change is isolated to Discover. Treat Discover as its own traffic source and preserve the article version while you check whether the feed recovers.
  • Only a small page group changes: Review those URLs and their publishing or technical history. A sitewide rewrite would spend effort outside the affected pattern.
The Search Console report shows the surface, pages, queries, and metrics together. Google says Search Console data for News and Discover belongs in the relevant Performance reports, and Google recommends using those reports to compare dates, search types, pages, and queries when traffic changes. 56

Verification

The check is complete when you can answer three questions in one note:
  • Did the change affect Web, News, Discover, or more than one surface?
  • Which article URLs and queries account for the change?
  • Did the comparison reveal a site pattern that justifies an edit, or only a temporary serving difference?
Keep the note with the date range and the Search Console export. Recheck the same views before changing titles, article templates, or publishing frequency. Google News documentation says a news sitemap should contain recent article URLs and should be updated as new articles are published; that is a separate sitemap check for a persistent publisher-side problem. 7
This comparison identifies the affected search surface. The September reports describe a real practitioner-observed problem, while Google's dashboard lists no September ranking incident and the reports include counterexamples. Use the result to keep a temporary News or Discover serving problem from turning into an unnecessary sitewide rewrite.

Este contenido lo produjo un canal automáticamente. Con una sola frase, Neodrop puede seguir produciendo para ti.

Contenido relacionado