Lizely SEO Analyst Observes DiscoverSnoop Data on Google Discover Core Update Reach Changes

Confirmation level and answer-first timeline

The Discover core update referenced here was announced by Google with the stated intent to show "more locally relevant content from websites based in their country," and the February rollout is still limited to English-language users in the United States, with expansion to more countries and languages planned but not scheduled. The data analyzed in this article comes from a single commercial tracker, DiscoverSnoop, as reported by Search Engine Journal, rather than from Google's own status documentation, and the report itself is based on DiscoverSnoop's own tracking data. Because the underlying finding rests on one third-party vendor plus one trade-press write-up, this is recorded here as a Verified Observation rather than an Official Change.

Two measurement windows are central. DiscoverSnoop compared article counts and audience scores for publishers in the week before the update began (January 26 to February 1) against the week after it completed (March 2 to March 8), a post-completion window that differs from NewzDash's earlier mid-rollout scorecard. Readers should hold both windows in mind, because a vendor measuring mid-rollout may show different results than one measuring post-completion, and that single fact drives most of the apparent conflict between trackers discussed below. The Lizely SEO Analyst Observes Google Release of February 2026 Discover Core Update note covers the announcement itself and is the natural precursor for what follows here.

Observed ranking distribution and scope

The headline movers in DiscoverSnoop's post-update window are losses, not gains. Yahoo lost nearly half its article placements and saw its audience score drop 62%, falling from third to ninth in DiscoverSnoop's rankings, and Yahoo's Discover decline began in September and the core update accelerated it. Fox News, Fox Business, and Fox Weather all saw visibility drop more than 40%. Forbes lost 21% of its article placements and 67% of its audience score. X/Twitter saw a 22% drop in article placements and a 32% audience decline. Both Fox and Forbes had been declining before the update, so the update amplified existing trajectories rather than reversing them.

The most distinctive signal sits in the local-publisher column. Syracuse.com lost 36% of its article placements and 80% of its audience score overall, but its New York audience held relatively steady, with losses concentrated in out-of-state feeds in Florida and California. cbs6albany.com showed the same pattern. Read against Google's stated intent, this looks less like a generic visibility loss and more like a redistribution: those publishers retained home-state reach and shed national reach. NewzDash's earlier data, found in the same trade-press write-up, showed New York-local domains appearing roughly five times more often in the New York feed than in the California feed, which fits the same redistribution shape from a different angle.

YouTube is the one notable first-party surface that grew in this dataset, with placements up 15% in the post-update window, from 16,283 to 18,803, and the DiscoverSnoop report notes that Google's own properties rarely suffer in core updates. Other named winners in DiscoverSnoop's data include Parade.com (article placements up 208%, audience scores up 1,300%), plus Axios, Fortune, Newsweek, and the Wall Street Journal. The winner list should be read with caution: when two commercial Discover trackers disagree on which sites gained the most, post-update data from any single source should be treated as directional rather than definitive.

Mechanisms, alternatives, and Public Action Brief

The mechanism implied by Google's stated intent is geographic reweighting: the update was meant to surface more locally relevant content, and DiscoverSnoop's state-level data suggests the update went further than adding local content to feeds. It appears to have reduced those publishers' visibility outside their home region. Syracuse.com kept its New York audience and lost out-of-state placements, and the same applied to cbs6albany.com, which is consistent with a feed-mixing change that elevates country-local and state-local sources inside each user's geographic distribution.

Several alternative explanations are real and should not be folded into the geographic story. First, Yahoo, Fox, and Forbes were already declining before the update; the core update accelerated existing trajectories rather than starting them, so any operator reading "lost 21% of placements" should also note that the trajectory predated February. Second, measurement windows disagree: NewzDash's mid-rollout data showed X.com posts from institutional accounts climbing in Discover's top 100, while DiscoverSnoop's post-completion window shows X/Twitter down 22% in placements and 32% in audience. The different measurement windows may account for the gap. Third, the Geediting.com case shows that even within the same vendor relationship, two tools can capture different aspects of Discover distribution. DiscoverSnoop names Geediting.com as one of the biggest reported winners in its post-update window, with article placements up 531% and an audience score up 900%, and more than 75% of Geediting's article titles begin with "Psychology says." NewzDash's mid-rollout data showed a Geediting listicle dropping from roughly #14 in the pre-update feed to roughly #153. The mid-rollout-to-post-completion path may have been a decline followed by a surge, or the two tools may be measuring distinct surfaces. Either way, the E-E-A-T profile Google described does not obviously fit that site, so a single-vendor winner list should not be treated as a template.

Operators also face a tracker-reliability boundary. When two commercial Discover trackers disagree on which sites gained the most, that reinforces what both vendors have acknowledged: post-update data from any single source should be treated as directional rather than definitive, and benchmarking against third-party reports requires checking which measurement window each vendor used. That is the operating rule this article applies to itself.

For the Google Discover core update release itself, see Lizely SEO Analyst Observes Google Release of February 2026 Discover Core Update. For traffic and tracking hygiene that becomes more important when third-party datasets disagree, the Generate UTM Links for Google Analytics Tracking guide is a direct fit, and the Troubleshooting guide observes common Search Console "no data" causes and operator fixes helps when Discover's own reporting is silent.

Knowledge Delta: new evidence, mechanism, decision, and falsifiable follow-up signal

The new evidence in this round is not the existence of the Discover core update, which Google announced, but the post-completion shape of its impact as captured by one commercial tracker. The single most useful finding is the state-level breakdown: Syracuse.com lost 36% of its article placements and 80% of its audience score overall, yet its New York audience held relatively steady, with losses concentrated in out-of-state feeds in Florida and California. cbs6albany.com showed the same pattern. That split is what lets an operator move from "Discover traffic fell" to "Discover traffic fell outside the home market," which is a more actionable framing.

The mechanism consistent with that evidence, and with Google's stated intent to show more locally relevant content from country-based websites, is feed-mixing change weighted by user geography. The update appears to have reduced those publishers' visibility outside their home region rather than reducing their overall reach uniformly. Alternative mechanisms (quality demotion, topical reweighting, E-E-A-T signal shifts) are not supported by the state-level breakdown and would not explain why a New York publisher's New York audience held while its Florida and California placements fell.

The decision this supports is a segmentation decision in measurement, not a content decision in publishing. Operators should expect that a national Discover traffic drop for a local publisher may not be a ranking drop at all; it may be a redistribution of feed surface toward the publisher's home region. Operators should not assume that a multi-state decline implies a content-quality problem, and operators should not assume that a winner named by one vendor (such as Geediting.com with article placements up 531% and an audience score up 900%) is a model worth copying, given that more than 75% of its titles begin with "Psychology says" and that the E-E-A-T profile Google described does not fit the site.

The falsifiable follow-up signal is whether a separate tracker, with a comparable post-completion window, confirms the geographic redistribution rather than just the headline percentage losses. If the pattern holds across a second independent dataset, the geographic-reweighting mechanism moves from hypothesis to verified observation. If the pattern collapses on replication, the simpler "national visibility broadly fell" reading returns. Either outcome is informative, and the review point is the next independently released post-completion Discover dataset.

Public Action Brief: action level, do now, do not change, measures, reversal evidence, and review date

ACTION LEVEL: Watch only HIGH IMPACT CHANGE: NO

OBSERVATION ORIGINS: this subject is a frozen trusted single-source observation, with exactly one official origin: DiscoverSnoop's report on its own Discover tracking data, as written up by Search Engine Journal. The observation rests on that single official source, and no second independent origin is added here.

LABEL: Verified Observation

WHAT TO DO NOW: segment Discover traffic by user geography before drawing conclusions. For local publishers that saw a post-update drop, check whether the drop is concentrated outside the home market, since the Syracuse.com pattern suggests some publishers didn't lose Discover visibility so much as they lost Discover visibility in states they weren't targeting. For benchmarking against third-party reports, check which measurement window each vendor used, because a tool measuring mid-rollout may show different results than one measuring post-completion. Tag Discover referrals with UTM segments that preserve region so the redistribution story is recoverable from first-party data. The Generate UTM Links for Google Analytics Tracking workflow supports that tagging.

WHAT NOT TO CHANGE YET: do not rewrite a local site into "national" coverage in response to this dataset, and do not copy the Geediting.com "Psychology says" title pattern. Do not treat DiscoverSnoop's named winners as a quality template, since the E-E-A-T profile Google described does not fit that site and NewzDash's mid-rollout data showed a Geediting listicle dropping from roughly #14 to roughly #153 before any reported surge. Do not assume Yahoo's 62% audience-score drop is restartable as a content strategy.

MEASUREMENT BASELINE: pre-update window of January 26 to February 1, drawn from the DiscoverSnoop comparison in the source article.

MEASUREMENT METRICS: article placements in the Discover feed and DiscoverSnoop's audience score, segmented by user state where the publisher's dataset allows. YouTube placements are reported in the source (16,283 pre-update, 18,803 post-update) as a first-party counterexample.

MEASUREMENT SEGMENTS: home-state versus out-of-state user geography for local publishers; named brand publishers (Yahoo, Fox properties, Forbes, X/Twitter) as a separate cohort; first-party surfaces (YouTube) as a counterexample segment.

OBSERVATION WINDOW: the post-completion window in this dataset is March 2 to March 8; mid-rollout windows from other vendors should not be substituted without restating the conclusion.

WHAT WOULD CHANGE THIS CONCLUSION: a second independent post-completion dataset that either confirms the state-level redistribution or shows that the national reach loss was uniform across local publishers regardless of home state. A direct Google statement on Discover's geographic reweighting would move this from Verified Observation toward Official Change.

WHEN TO REVIEW: on the next independently released post-completion Discover dataset, or on any direct Google communication about Discover feed composition.

APPLICABILITY: publishers with material Discover referral traffic, especially U.S. local and regional publishers; SEO teams benchmarking Discover performance against third-party trackers; newsrooms evaluating whether a Discover drop is a content problem or a geographic redistribution.

RISK BOUNDARY: this article is not officially confirmed, the underlying dataset is a single vendor's post-completion window, two commercial Discover trackers disagree on which sites gained the most, and Google's own properties (YouTube) are part of the same window. Treat every figure as directional.