Reach's own numbers don't add up the way its press release wants them to

Reach's digital revenue fell almost 1% last year, to £128.9m. Its traffic from Google fell 46% over the same stretch. Those two numbers should be much closer together than they are, and the gap between them is the actual story here. Not "AI is taking jobs." That's the surface reading, the one every outlet covering this is going to run with today. The real thing happening is that Reach can see where the traffic line is headed before the revenue line catches up, and they're cutting now rather than waiting for the crash to actually land.

Reach announced 220 more editorial job cuts on Wednesday, on top of the 300+ it already cut in a September restructure that put 600 roles at risk. It's also closing three regional-only online brands (KentLive, AberdeenLive, GalwayBeo) because they weren't "dominant" in their patches. Chief content officer David Higgerson called it a "mammoth shift in how audiences want content and journalism," and pointed to Google's AI Mode and AI Overviews as the mechanism: readers get the summary, never click through, and a site built on volume traffic loses the thing it was built on.

Here's what doesn't fit the doom framing, though. Digital revenue barely moved. Traffic fell by nearly half and revenue fell by less than one percent. If AI summaries were already gutting Reach's business the way the headline implies, you'd expect the revenue line to be in freefall too. It isn't. Not yet. What that tells me is Reach isn't reacting to a business that's already collapsed, it's front-running a collapse it expects is coming, because the traffic curve is the leading indicator and the revenue curve is the lagging one. Cutting 220 jobs before the money actually disappears is either disciplined foresight or panic dressed as foresight. Probably some of both.

The other piece nobody's weighting enough: Reach isn't just fighting Google. Higgerson also named the BBC directly, saying its local coverage was "mirroring the local output of commercial publishers up to 70% of the time." That's a genuinely different threat than an AI summary. Google AI Overviews compresses Reach's own content into a box readers don't click past. The BBC, publicly funded and under no pressure to monetize page views, is producing competing local journalism for free. Reach is getting squeezed from two directions that don't require any coordination between them, and lumping it all under "AI is taking readers" flattens a story that's actually about two separate structural problems landing in the same year.

The steelman, and where it breaks

The fair version of Reach's plan: stop chasing story volume, which is what you optimize for when the traffic algorithm rewards volume, and build "distinctive brands" people pay for directly. That's not crazy. Subscriptions are immune to a Google traffic collapse in a way ad-supported pageviews never were. Reach already has 50,000 paid digital subscribers across six titles and wants 75,000 by the end of its financial year. About 60 new editorial roles are going into exactly that, plus longer-form video.

The math is the problem. Fifty to seventy-five thousand is a 50% jump in subscribers, funded by 60 new hires, while the 220 cuts come from the newsroom that currently produces the volume journalism paying most of the bills today. That's not a pivot with a runway under it. That's a pivot happening at the same time as the floor gets pulled, on the bet that the new floor gets built fast enough. Reach's share price is down 90% over five years. That's not a company with a lot of room to be wrong about the timing.

If you run a content site, or advise anyone who does, the thing worth checking this week isn't your headcount plan, it's your traffic composition. Pull Search Console and look specifically at how much of your organic traffic sits on query types Google's AI Overviews already answers directly (definitional, comparison, "how to" queries are the most exposed). That share is the part of your business that behaves like Reach's did. Whatever revenue you can move off ad-supported pageviews and onto something a reader pays for directly, on your terms, is revenue an AI summary box can't quietly take from you next quarter.

For builders

• Pull Google Search Console and segment queries by type — informational/definitional queries are the ones most likely to get answered inside an AI Overview instead of a click.
• If more than a third of your organic traffic sits on that kind of query, start building a direct-reader revenue line now, not after the traffic drop shows up in your analytics.
• Watch Reach's next earnings report (financial year ends early March) as a live test case for whether a subscription pivot can outrun an AI-driven traffic collapse.

Further reading

• The Guardian — Mirror publisher to cut 220 editorial jobs as readers turn to AI summaries — primary source for all figures cited above