--- title: "One publisher's Google Discover traffic loss and recovery" url: https://seomadman.com/studies/discover-traffic-recovery-case section: studies published: 2026-08-09T00:00:00.000Z modified: 2026-08-09T00:00:00.000Z author: Adam Hafez topics: ["Content strategy"] --- # One publisher's Google Discover traffic loss and recovery ## The short answer An independent consultant's case study describes a client publisher's Google Discover traffic falling to zero impressions for about seven weeks after a core update. The consultant traced it to missing Discover-ready images, broken structured data, a schema bug crediting articles to the wrong site, and thin pages. Discover traffic returned the same day as Google's next core update. ## Key takeaways - One independent consultant's account of a client engagement describes Discover impressions falling to zero for about seven weeks after a Google core update. - The audit found articles without Discover-ready images, broken structured data, a schema bug crediting articles to a different site, missing bylines, and thin pages. - Recovery meant sizing images for Discover across nearly the whole catalogue, fixing the structured-data errors, and trimming the thinnest pages, then holding steady and waiting. - Every title in the client's network regained Discover visibility the same day, coinciding with a core update, and the flagship site posted its best Discover month on record. - This is one consultant's self-reported, unaudited account of a single client, with exact traffic numbers withheld at the client's request, not a formula to replicate. A consultant's Discover recovery story is a different kind of source than the algorithm-update coverage above: it is one person's account of one client, not a dataset or a Google announcement. Independent consultant Nerijus Masikonis published a case study describing a publisher client whose Google Discover impressions dropped to zero after a core update, stayed there for weeks, and then came back. We read the post directly. Here is what it actually says, in the consultant's own words, and why it should be read as a single anecdote rather than a repeatable playbook. ## What happened, in the consultant's own account The client's Discover traffic collapsed after a Google core update. Per the post, "the impressions went to zero and stayed there" for about seven weeks. Masikonis writes that his audit afterward found "articles without Discover-ready images, broken images and structured data, a schema bug crediting articles to a different site, missing authors and descriptions, and thin pages." That is a list of quality and technical signals, not a single named cause, and the post does not claim to know which item on that list mattered most to Google. ## What changed, and how Google responded The fixes described are concrete: Discover-sized images went out to "almost the whole catalogue," reaching 97% of articles by the consultant's own figure. The broken structured data and the schema bug misattributing articles to another site were corrected. Missing author bylines and descriptions were filled in. The thinnest, lowest-quality pages were removed rather than kept. After that, Masikonis writes that he "held the site steady and waited." Discover traffic did not return gradually, it came back "on the same day" as Google's next core update, across every title in the client's network, with the flagship site going on to post its best Discover month on record. ## Why this is one case, not a study Masikonis states outright that "traffic volumes are hidden at the client's request," so there is no absolute click or impression figure to check the recovery against, only the zero-impression period, the 97% image fix, and the relative claim of a record month. This is a single consultant's self-reported account of a single client engagement, published on his own site, not an audited tracker dataset or a Google statement. Nothing here establishes that the same fixes would recover Discover traffic for a different site, or that the timing next to a core update was cause rather than coincidence. ## Why we care The value of this case is the checklist, not the numbers. Discover-ready image sizing, clean structured data, correct site attribution, complete author and description metadata, and pruning thin pages are all things a publisher can audit today without waiting on Google. Treat the recovery timeline, the same-day return alongside a core update, as one data point worth watching for, not a mechanism this post proves. Read it alongside our coverage of the February 2026 Discover-only core update, which found that most of an article's Discover clicks land within a day of publishing, for the fuller picture of how fast this channel moves in both directions. ## Frequently asked questions ### Does this case study give exact traffic numbers? No. The consultant states plainly that traffic volumes are hidden at the client's request. The post gives directional detail instead, zero impressions for weeks, then a recovery to the site's best Discover month on record, and one hard figure, 97% of articles fitted with Discover-ready images. ### Is this independently verified data? No. It is one consultant's own, unaudited account of one client engagement, published on their own site. We read the source directly and report what it says, but nobody outside that engagement has confirmed the numbers or the cause. ### What actually caused the drop, according to the consultant? A Google core update, combined with site-wide quality issues the consultant's audit surfaced afterward, missing Discover-ready images, broken images and structured data, a schema bug attributing articles to a different site, missing author information and descriptions, and thin pages. ## Sources 1. [Google Discover recovery case study](https://masikonis.lt/case-studies/google-discover-recovery/) - Nerijus Masikonis (independent consultant) (primary)