Google ran two updates this spring — the first-ever Discover core update in February, then a broad core update in March. Both are finished, and the pattern is clear enough to act on. There's a side of this story the panic posts missed: local businesses came out of it unusually well placed.
Google's first-ever Discover core update ran February 5–27, 2026. The March 2026 broad core update followed, rolling out March 27 and completing April 8. Both rewarded original, experience-backed content and demoted thin, undifferentiated pages. For local businesses with well-maintained sites, that direction is an opening rather than a threat. Here's what each update targeted and what to do about it.
The two updates that reshaped spring 2026 are often discussed as if they were one event. They were not, and the order matters.
February 5–27: the first-ever Discover core update. Google announced a broad update to the systems that surface articles in Discover — the content feed on Android home screens and in the Google app. It is the first Discover-only update Google has ever shipped. Google's own description of the goal was unusually direct: reduce sensational content and clickbait, and highlight more in-depth, original, and timely content from sites with demonstrated expertise. It launched for English-language users in the U.S. first, with wider rollout to follow. It took about 22 days.
March 27 – April 8: the March 2026 broad core update. The first core update of the year, affecting Search itself. Google estimated up to two weeks; it finished in 12 days and change.
So these were sequential, not simultaneous — Discover wrapped a month before the core update began. If your traffic moved in February, that is a different story from traffic that moved in April, and conflating them will send you chasing the wrong fix.
A note on the numbers you have probably seen: various SEO blogs reported organic traffic drops in the 20–35% range. Those figures circulate widely, but we have not found a primary study behind them, and Google does not publish per-site impact data. Treat them as anecdote, not measurement. The honest version is that volatility was high and the distribution of winners and losers was wide.
Core updates are rarely about one thing, and Google deliberately does not publish a technical changelog. What follows is the pattern practitioners consistently observed, not something Google confirmed line by line — worth holding a little loosely.
Site-level quality appears to matter more than page-level. E-E-A-T — Experience, Expertise, Authoritativeness, Trustworthiness — has been a Google quality framework for years. The recurring observation after March was that a single strong page carried an otherwise thin site less far than it used to.
Generic, undifferentiated content lost ground faster. A site with 50 pages of AI-generated or lightly repurposed content fared differently from one where a real person with real experience is clearly behind the writing.
Topical depth beat scattered keyword targeting. A local accountant with a dozen genuinely useful articles on small business tax strategy in Tennessee did better than a site with one thin page per keyword.
For Discover, Google was explicit rather than mysterious: clickbait down, in-depth original work from demonstrated expertise up. Sites built purely to farm impressions were the intended losers. That is a rare case where you can read the goal from the source instead of inferring it from traffic graphs.
Every time a major Google update rolls out, coverage focuses almost entirely on who is losing. SEO forums fill with downward graphs. Agencies post "recovery" threads.
But core updates do not push traffic down — they redistribute it. For every site losing ground, another gained visibility in the same results.
And local businesses were unusually well placed.
Local search intent is different from informational intent. When someone searches "estate planning attorney Cleveland TN" or "custom cabinet maker near me," they are not looking for a summary. They want a real business, a real person, a real phone number. The signals Google uses to evaluate local relevance are precisely the ones a well-maintained local business site naturally produces.
An emphasis on demonstrated experience advantages businesses that show:
The local business that writes one thorough article about what to expect from a first consultation, specific to how they actually work, has something a national directory listing structurally cannot copy.
Thin service pages. "We offer [Service] in [City]" with 200 words and a contact form does not satisfy search intent or establish expertise.
Sites that haven't changed since launch. A site built in 2021 with the same content, same structure, same pages reads as stagnant next to actively maintained competitors.
Slow, unstable pages. Core Web Vitals — load speed, layout stability, and interaction responsiveness — remain part of Google's page experience signals. They will not rescue weak content, and they were never the headline of this update, but a site that feels sluggish on mobile is losing people before content quality gets a vote.
Duplicate and syndicated content. Copied source material, or the same content spread across near-identical keyword pages, saw significant drops. Originality is not optional.
Audit and consolidate thin pages. Instead of 15 city-targeted service pages at 200 words each, build 3 genuinely comprehensive pages that answer what searchers are actually asking.
Publish from real experience. Case studies, client outcomes (anonymized if needed), lessons from actual projects — specific guidance that can only come from someone who has done the work, not content any model could generate from a keyword list.
Keep your business information consistent. Services, hours, service areas, and content topics should tell the same story everywhere they appear. Inconsistency reads as a trust problem.
Fix Core Web Vitals issues. If your Largest Contentful Paint is above 2.5 seconds on mobile, that is addressable — and it compounds.
Maintain a real publishing cadence. Not volume for its own sake. One genuinely useful piece per month outperforms five thin posts per week.
The businesses that came out of spring 2026 ahead were not doing anything exotic. They were doing the things that make a website a business asset rather than a brochure: keeping it current, building content from real expertise, making it fast and reliable, and connecting it to a real business with a real track record.
That is not something you fix once and walk away from. It is the ongoing work of treating a website as infrastructure — something that needs attention and adaptation as the environment shifts.
Which is also why the most exposed businesses, to this update and every one after it, are the ones whose site was launched and then handed off with no plan for what comes next.
We have been saying this for a while, and spring 2026 made it harder to ignore: a website is not a finished product. It is infrastructure that has to stay current with the environment it operates in.
For local businesses, that environment is currently favorable. Google is moving toward exactly the signals that authentic, locally-rooted businesses naturally produce — genuine expertise, real community presence, actual client relationships. The algorithm is catching up to reality.
The businesses that capitalize on it are the ones with someone paying attention: adapting the site when the landscape shifts, building content from real experience, and connecting the online presence to the real-world business in ways that hold up to scrutiny.
That is a different relationship with your web presence than most agencies offer. It is what a growth partner actually does.
Every claim above that came from outside SitoraWeb is linked here. Check them.
If this article reflects the kind of problem you are solving, these are the most relevant next steps inside SitoraWeb.
Improve trust, search visibility, and lead quality with a custom website built around how buyers actually compare options.
Explore Website ServicesBuild secure portals, dashboards, internal tools, and customer-facing web apps that remove operational friction.
Explore Web App ServicesGet validation, workflow analysis, and a roadmap before you commit to the wrong build path.
Explore ConsultingThe rest of the blog covers search strategy, site architecture, analytics, automation, and common mistakes that slow down growth.