March 2026 Google Core Update Recovery for London Businesses

If you're a London business owner and your Google rankings dropped in March 2026, you already know it feels personal. One week you're on page 1 for the terms that pay your rent. The next week you're on page 3 and nobody warned you. Traffic falls off, leads dry up, and the marketing team is scrambling to explain what happened.

We've been through this with clients before at Dedote. March 2026 wasn't the biggest Google core update on record, but it was one of the harsher ones for UK service businesses that had leaned on thin content and generic pages. Sites with strong original content mostly held. Sites without felt it hardest.

Here's the honest reality most agencies won't tell you. Core updates don't punish you for one thing. They rebalance how Google weighs a bundle of quality signals: content depth, expertise, user experience, and now increasingly the AEO layer (how well your content works inside AI answer engines). If your site was already borderline on one of those signals, the update tipped you over.

This article walks through what actually happened in March 2026, why London businesses were disproportionately affected, the general recovery patterns Google publishes and what we've observed across the industry, our own recovery framework, and the honest answer to how long you should expect this to take. Written for owners and marketing leads, not for SEO specialists.

1 · What actually happened in the March 2026 Google core update?

Google confirmed the March 2026 core update via the Google Search Central update history log. Rollout completed inside two weeks, which is standard for a core update in 2026. Like previous core updates (per Google's own explainer documentation), the update rebalanced how the search algorithm weighs quality signals rather than adding a specific new signal.

The observable pattern across UK SERPs after the update: pages with thin, generic content lost ranking. Pages with strong original information, real expertise and clean structured data held or gained. AEO-optimised pages (with FAQPage schema, Speakable, answer-first paragraphs) held up better than pages without.

Nothing new in that. It's the same lesson every core update teaches. Google keeps raising the floor on what "good enough" means. Sites that were good enough in 2024 aren't good enough in 2026.

2 · Why London businesses were disproportionately affected

Because London is competitive. In a city where four or five SEO agencies rank on page 1 for "SEO agency London" and every dental practice in Zone 2 has a website, the marginal quality bar for ranking is higher than almost anywhere else in the UK.

Google doesn't publish city-level update impact data, but a straightforward logic applies. In a competitive SERP, there are more credible pages competing for the top 10 spots. When Google raises the quality floor, the marginal page that was ranking pos 8 in London is more likely to be replaced by a stronger page waiting at pos 11 than the same-quality page ranking pos 8 in a smaller UK town where the depth of competition is thinner.

The bigger factor was content depth. London businesses that had built out proper pillar-and-cluster content structures (service pages plus supporting articles plus local content) mostly held steady. Businesses relying on a homepage plus five thin service pages felt the drop hardest.

3 · The recovery patterns Google publishes

Google's own guidance on core update recovery is short and clear (per Google Search Central's Core Update Recovery documentation). Focus on the E-E-A-T signals. Improve content depth. Wait for the next update if the underlying quality is genuinely good.

That guidance holds. What Google doesn't say (because Google doesn't discuss algorithm specifics) is what actually moves rankings in practice. From industry-wide observation of the March 2026 update recovery pattern across UK SERPs, three moves consistently correlated with ranking recovery.

Pages that added FAQPage schema and Speakable schema after the update recovered faster than pages that didn't. Pages that extended thin content to 1,100 to 1,800 words with original information recovered faster than pages left at 300 to 500 words of generic copy. Pages that added author bylines, real photos and named expertise recovered faster than pages with anonymous corporate voice.

None of that is surprising. It's what Google has been publicly asking for since 2022. What March 2026 did was tighten the enforcement.

4 · What Google is really rewarding in 2026

Two things sit above everything else in 2026. E-E-A-T signals and AEO alignment.

E-E-A-T (Experience, Expertise, Authoritativeness, Trust) has been Google's stated framework since 2022. What's changed in 2026 is how much weight Google places on demonstrable expertise. Author bylines on articles. Real photos of real people. Named experience ("I've worked in this sector for 12 years"). Original data ("we surveyed 500 UK businesses"). None of these are new signals, but Google now measurably discounts pages that lack them.

AEO alignment is newer. Pages that get cited by ChatGPT, Perplexity and Google AI Overviews tend to rank better in classic search too. The correlation runs both ways. Content built for answer engines (answer-first paragraphs, FAQPage schema, Speakable) tends to also match Google's helpful content signals. Pages built without those elements often struggle on both.

Everything else (backlinks, page speed, mobile experience) still matters but sits below E-E-A-T and AEO in Google's current weighting. Fix those first.

5 · Dedote's recovery framework

We run every core-update recovery through the same 4-week framework at Dedote. The specifics change per client but the structure holds.

Week 1: full audit. Which pages lost traffic. Which queries lost ranking. Which content types held. Search Console analysis, GA4 attribution analysis, competitor SERP comparison. Output is a ranked recovery priority list, not a 200-page PDF.

Week 2: fix technical debt. FAQPage and Speakable schema on every service page. Author schema on every article. Article schema with citation arrays. Any obvious technical SEO issues (schema errors, indexation gaps, Core Web Vitals failures) resolved.

Weeks 3 to 4: rewrite the pages that lost traffic. Bring word count up where it was thin (1,100 to 1,800 words for service pages, 1,800 to 2,400 for informational content). Add original information. Add proper answer-first structure. Add real client testimonials and case data where permission exists.

Week 5 onwards: monitor and iterate. Weekly Search Console review. New content published against the pillar and cluster map. Internal linking updated to reflect the new content structure.

Nothing fancy. Just discipline and time.

6 · How long does recovery actually take?

Honestly? Longer than most agencies claim, shorter than doing nothing.

Google's own guidance says recovery from a core update happens either at the next core update (typically 3 to 6 months later) or gradually as pages are re-crawled and re-evaluated. In practice, sites that do active recovery work usually see partial improvement inside 21 to 45 days and full improvement over 60 to 120 days depending on the depth of the content and technical work.

Full recovery isn't binary. Some sites hit their previous ranking on some queries within 3 weeks while other queries take 4 months. Watch aggregate impressions in Search Console, not individual keyword rankings. Impressions recover in waves as Google re-indexes pages in stages.

If your site was hit hard and you do nothing, expect either partial recovery at the next core update, or no recovery at all. Google isn't in the habit of reversing quality-based decisions without a change in the underlying content.

7 · What not to do while waiting

The two biggest mistakes we see London businesses make after a core update drop.

First, panic and rebuild the site. Every core update recovery cycle brings a wave of clients asking for a full redesign. Almost never necessary. Core update drops are content problems, not design problems. A slower site with better content beats a faster site with worse content in Google's eyes.

Second, chase the algorithm. There's a temptation to read every SEO blog post about "what caused the March 2026 update" and try to fix all the theories at once. Most of those posts are speculation. Google's own guidance is clear: focus on content quality and E-E-A-T signals. Ignore the noise.

The third mistake, which is less common but more damaging, is stopping content production during recovery. Publishing pauses are one of the strongest signals to Google that the site is losing momentum. Keep publishing at your normal cadence, focus on quality over quantity, and let the recovery compound.

8 · When to invest and when to sit still

Invest in recovery if your organic channel drove more than 20 percent of your revenue or lead flow before the update. The recovery cost typically pays back inside 90 to 180 days at that traffic level.

Sit still if organic drove under 10 percent of your revenue and paid channels are healthy. Wait for the next core update in 3 to 6 months, which usually rebalances things back somewhat. Meanwhile, keep publishing but don't panic-invest.

Somewhere in the middle? Do the technical schema and E-E-A-T work (2 to 3 weeks of investment, high leverage) but hold off on major content rewrites until you know whether the drop is a permanent devaluation or a temporary rebalance. The next core update tells you which.

Frequently Asked Questions

Sources