Skip to main content
Search Solved

Google update recovery audit

What was hit, why, and how to get it back

Your traffic dropped after a Google update, or it's slid for months and you want it fixed before the next one. This is a fixed-fee audit that reads every page for quality and helpfulness, finds what pulled the site down, and gives you a prioritised plan to recover it — briefs and all, ready for your team to run.

  • Every page analysed for quality and helpfulness
  • A diagnosis of what was hit, and why — before anything's rewritten
  • A prioritised recovery plan, sequenced for a stretched team
  • Findings handed over as briefs your team can action
  • Fixed fee, from £4,500, agreed before work starts

No commitment. I reply personally within two working days.

From hit to recovery, step by step

A clear path from "what just happened" to "here's exactly what to do" — five deliverables your team can act on, then three optional extras if you'd rather not go it alone. Just been hit? Start at step one. Watching a slow decline instead? Step one becomes a short baseline read and the audit goes straight in.

Step 1 — when you've dropped

First, what actually happened

Guessing after an update is expensive. The audit opens by establishing what was hit, when, and why — before a single word is rewritten.

  • Your traffic mapped against the update's confirmed rollout and split by template, so the damage has a shape you can act on.
  • The pages that took your visibility, reviewed by hand — what they do that yours don't.
  • The other explanations — technical, seasonal, tracking — tested and ruled out in writing, so the plan treats the real cause.
See the real section from an audit
The decisive evidence

Two rivals sailed through the update. You and one other didn't.

Page-one coverage for you and three competitors, indexed so January = 100 — it's about the shape, not the size. A technical glitch or a random reshuffle wouldn't sort rivals by editorial quality. A site-level quality reassessment would, and that's the split on show here.

Page-one coverage through the 2026 Google updates, indexed to January = 100 Four lines. Two competitors stay flat near 100 through the updates. Your site and one rival both fall sharply from February; the rival recovers to about 88 by June after a content refresh, while your site stays down near 40. Page-one coverage through the 2026 updates Search terms ranking on page one, indexed so January = 100 120 80 40 0 Jan Feb Mar Apr May Jun update hits Mar core May core 39 88
You Rival C — recovered Rival A Rival B

Read the recovery, not just the crash. The February window halved how often Google served your pages; the March core then removed the rankings. At the May core, Google re-admitted only the pages that meet the new standard — so the small bounce is your single strongest page being let back in. Fix the rest to that same bar and more return.

The rival that recovered isn't luck. It scaled content the same way, crashed on the same dates, and has been actively rebuilding the affected pages — the ones with the same issues as yours. The two that never moved didn't have the problem. The split is editorial, and the fix is proven by a direct competitor.

Step 2 — the audit

Every page analysed, section by section

The core of the audit. Every page is evaluated for quality and helpfulness — the same close read across the whole site, not a sample of it. Each finding comes from five questions:

  • Does it deliver on its promise?
  • Is there real proof behind it — evidence, expertise, dates?
  • Is it useful to your buyer, or built to rank?
  • Does it say anything your other pages don't?
  • Is it current, and can a reader actually use it?
See the real section from an audit
Quick win · useful, one fix short

/connect/email-platform/

Promise vs delivery
The title promises reporting for a named email platform. The page delivers the site-wide boilerplate with the platform's name dropped in: the metrics list is the generic set, the screenshot is the same dashboard used on 30 other connector pages, and nothing shown is specific to this connector.
Evidence & specificity
No worked example of this connector's data in the product. The one named customer quote is real, but it appears word-for-word on 12 other pages, which spends its credibility. Two small defects too: a product name that changed in 2024, and a doubled heading.
Usefulness to the buyer
An agency deciding whether this connector covers their client work learns nothing page-specific — which metrics sync, how often, what a real report looks like. A visitor who finishes the page still has to open the product, or a rival's page, to answer their question.
Verdict & action
A quick win — this page can earn its slot. The connector has real depth to show (its metrics explorer covers 40+ fields). The brief: one worked example of this connector's data in a report, the current product name, and the sync details agencies ask about. If that proof can't be produced, the page folds into the email category page instead.

Step 3 — the plan

A recovery plan, in the order to do it

Every finding worked into one sequence, so a stretched team knows exactly where to start.

  • Grouped by fix: the template and site-section changes that lift dozens of pages at once — then the individual page fixes within each group.
  • Ordered by what's at stake: the pages buyers actually read, the size of the quality gap, and how many pages share the problem.
  • Effort decides only when a fix happens, never whether — the systems that manufacture weak pages get fixed before the pages themselves.
See the real section from an audit
The recovery plan

Every finding turned into one sequence — now, next, then

The quick wins ship regardless. For the bigger work, two short reads set the order — so the effort goes where it pays back, not just where there's the most to fix. Nothing here is locked: the sequence is a proposal to react to, with the calls that are yours flagged.

  1. Now

    Ship the quick wins, in parallel

    The find-and-replace corrections and the competitor-accuracy fixes — no dependencies, so the first pages read clean within days. The one long-lead request (the conversion data your revenue team owns) goes out first, even though its answer is needed later.

  2. Next

    The two reads that set the order

    A demand read (which searches actually bring buyers) and a value read (which pages drive pipeline, not just traffic). Together they decide which rebuilds go first, so the big work is ordered by payback rather than by how much there is to fix.

  3. Then

    The rebuilds, ordered by value

    The differentiation rewrites, the template fixes that lift dozens of pages at once, the thin-page calls and the FAQ sweep — each sequenced by what the value read says pays back first. The template and section fixes land before the individual pages inside them.

Ordered by what pays back, not what's loudest. Effort decides when a fix happens, never whether. The systems that manufacture weak pages get fixed before the pages themselves, so the same problem stops coming back.

Step 4 — the briefs

Fixes written to hand straight over

The plan becomes work your team can run without me:

  • Content and template briefs: what to change, on which pages, and what "done" looks like.
  • A quick-win find-and-replace list applied straight into the CMS — the first pages read clean within days.
  • No tickets to interpret — briefs your content team can pick up and run.
See the real section from an audit
Content brief · the big piece

Give the connector pages their own reason to exist

Quick wins clean the surface; they don't move rankings on their own. This is the brief for the piece that does — the biggest of the findings, written the way your team receives it, so the work can start without me. One page's brief, in full:

The problem this fixes
More than half the words on the connector pages could move between pages without anyone noticing. Swap the connector name in any two intros and both still make sense: the test a page fails when it was built to fill a template, not to help someone decide. It's the “made-for-search” pattern the helpful-content guidance names, and the heavy tail of interchangeable pages taxes the good pages around them.
What “done” looks like
Every page in scope answers one buyer question no sibling page answers, with a worked proof of it. Someone on the email-connector page learns something they couldn't get from the CRM-connector page. No shared passage survives the swap test.
Scope — 88 pages, sorted into three jobs
  • True integrations (~50): differentiate. Each earns its own angle and a worked data example.
  • Manual-tool “alternatives” (~24): re-angle to “switch from doing this by hand”, on a purpose-built template.
  • Thin or duplicate (~14): fold into the strongest sibling with a redirect, or give it real content. Decided page by page.
The method — not hand-rewriting 88 intros
That just makes the same sameness with more effort. Instead: you set the angle, the key features and the proof for each page; each shared section is then rewritten to that angle, section by section; the testimonial on each page is matched to its focus, or sourced. Angles are decided up front in one pass, then the rewrites run demand-first over a couple of sprints.
Per page, section by section
  • Intro: the generic promise → the one thing this connector does that matters to the buyer.
  • “What syncs” block: the boilerplate metric list → the fields this connector actually returns, and how often.
  • Proof: the shared screenshot → one worked example of this connector's data in a real report.
  • FAQ: the two questions agencies ask about this specific connector, added as structured data.
The intro, before and after: the swap test, failed then passed
Before · interchangeable

“Connect [Email Platform] to your dashboard and build white-label reports your clients love. Pull your key metrics into one place, automate reporting, and save hours every month.”

Swap “[Email Platform]” for “your CRM” and it still reads perfectly. Nothing in it is about email.

After · page-owned

“Show clients exactly what their email marketing did: open and click-through rates, unsubscribes, list growth and revenue per campaign, pulled straight from [Email Platform]. Start from one of six ready-made email report templates, add your logo, and let Marlo's AI write the plain-English summary of what moved and why. Synced daily, sitting next to their paid and organic in one white-label report.”

Swap in another connector and half of it stops being true: no CRM reports an open rate. That's a page element earning its place.

The “after” sells what only this connector does: the email-specific metrics, the ready-made templates, the AI summary. “Marlo” is a stand-in brand — the point is that a page can name real features and benefits instead of reciting boilerplate.

Owner & effort
Content ops, with product marketing for the proof examples · angles decided in one up-front pass, then the rewrites over a couple of sprints · the manual-tool template is the one dev (or CMS page-builder) dependency · no redesign.

Alongside this, the quick-win find-and-replace list (retired product names, unrendered template tokens, doubled headings) ships straight into the CMS on day one, so the surface reads clean while the rebuild runs.

Step 5 — the wrap-up review

A then-and-now read, once the recovery lands

Recovery registers when Google re-evaluates, so this isn't a week-by-week promise. Once the fixes have shipped and an update has passed, I read the recovery against the pre-drop baseline:

  • A recap of what was fixed — quick wins, template fixes, page reworks
  • The success measures quantified: then vs now, against the pre-drop baseline
  • Read at the update checkpoints, where re-evaluation actually happens
See the real section from an audit
The wrap-up review

What was fixed, and how the recovery landed

Recovery registers when Google re-evaluates, so this isn’t a week-by-week promise: once the fixes have shipped and an update has passed, I read the recovery against the pre-drop baseline. A clear before-and-after on the measures the audit set as its markers of success.

What was fixed:

The workDone
Quick winsStale facts corrected, dates and authorship added, doubled headings cleared
Template & systemic fixesThe page types that manufacture weak pages reworked; sameness across the family removed
Page-level reworksThe built-to-rank pages rewritten to the briefs; the useful-but-buried ones surfaced

And how the recovery landed — the success measures, then vs now:

Success measureAt the auditNowCall
Pages above the quality bar41% of the affected family78%Landed
Sameness across the familyHigh — interchangeable pagesCut; each page owns its angleLanded
Recovery vs the pre-drop baseline42%91% — most of it backOn track
Organic traffic18k/mo, post-drop31k/mo, after the next update re-evaluatedOn track

Optional extras

Optional extra

Track the recovery back to the business

Recovery only counts when it shows up in the numbers that pay for it. A private dashboard tracks exactly that, fix batch by fix batch. From £2,500, then £250 a month if you keep it on.

  • Every fix batch annotated on the chart the week it ships
  • Visibility recovery tracked against the pre-drop baseline
  • Carried through to conversions and revenue, not just sessions
Explore the SEO Activity Impact Tracker

Optional extra

Guardrails, so quality doesn't slip before the next update

Recovery holds until the publishing that caused the drop creeps back: sameness across a family, fresh thin pages, facts going stale. Guardrails are the standing checks that catch it early, so drift surfaces in a report rather than the next core update. Scoped to your site — what needs watching sets the price.

  • A publish gate so new pages meet the bar before they ship
  • A sameness watch across the page families the audit cleaned up
  • Dated facts flagged before they go quietly wrong

Optional extra

Bring me in to oversee the recovery

The plan is built so your team can run it alone. When you'd rather it was steered, I stay on to do the steering. On hand throughout, scoped per project:

  • The recovery roadmap managed and kept on track
  • Dependencies and priorities sequenced as the work ships
  • Each fix reviewed and signed off before it goes live

Every audit is a fixed fee, from £4,500, agreed before work starts — it covers most sites up to ~10,000 pages (assessed by page family); larger or more complex sites are scoped individually.

Ready to scope yours? Request a consultation

AgencyAnalytics

B2B SaaS

Argos

Retail

Barclaycard

Financial Services

Bravissimo

Fashion

CMO Group

Ecommerce

Dunelm

Home Retail

Hindawi

Publishing

IEDigital

Fintech

Jobber

B2B SaaS

MOO

Ecommerce

Technogym

Fitness & Sport

The Range

Retail

Virgin Experience Days

Leisure & Gifting

He is extremely knowledgeable about all matters SEO and we have trusted him explicitly. He has held our hand through a major domain change and move to https and it went extremely smoothly. Nothing ruffles him and I would not hesitate to recommend him.

Cathy Berman · VP Marketing, MOO.com

Dropped after an update — or worried about the next one?

Tell me what happened and when, or what you can see sliding. I'll tell you whether this audit is the right next step — and if the evidence points somewhere else, you'll hear that instead.

Before you enquire

Common Google update and content quality questions

What does a content quality audit cost?

A content quality audit is a fixed fee, from £4,500, agreed before work starts — and the fee includes the walkthrough and my support while the fixes ship, not just the documents. The exact price depends on how many pages are in scope: the fee covers most sites up to around 10,000 pages, assessed by page family, and larger or more complex sites are scoped individually. When there's been a drop, the diagnosis phase is part of that fixed fee, not a surcharge. If an audit isn't the right next step, I'll say so before you spend anything.

How do you measure content quality?

Two reads on every page, scored section by section: how good it is — accuracy, evidence, real expertise — and how well it serves the specific buyer it's for. The measures come from Google's published guidance and documentation, plus my own insight from years of doing this. Every page is scored across them, but I don't hand you a number — I hand you the improvements. The useful signal isn't either read on its own, it's the gap between them: a page that's useful but held below the bar is a cheap fix; a page that's polished but says nothing a buyer can use needs reworking. More on what "quality" actually means.

What does the audit include?

When there's been a drop, two documents. First the impact analysis: what was hit, what was spared, the alternatives ruled out in writing, and who took the visibility. Then the quality assessment itself: an executive summary with the traffic at stake, the quality read by page family, the priority matrix, worked findings with plain-English evidence, content and template briefs, a sequenced fix plan and a then-and-now wrap-up review once the recovery lands — plus a data sheet with every page's section-by-section findings. Regression guardrails and an ongoing impact tracker are optional add-ons. No drop? You get the assessment, with a baseline read where the diagnosis would sit.

We've dropped after a Google update. What happens first?

A triage read, within days of getting access: does the drop track the update, an incident, or something else. Then phase 1 in full. Two rules protect the diagnosis: if the update is still rolling out, changes wait until it settles — mid-rollout edits can't be read and usually make things worse — and if the evidence points somewhere other than quality (technical, or the results page changing shape), you hear that instead of a rewrite plan. Announced update or not, the method is the same; the timeline evidence just works harder.

Should we delete or consolidate low-quality content?

Sometimes — but not with a blanket sweep, and rarely by deleting. The audit gives every weak page a verdict: fix it, differentiate it, fold it into a stronger page, or retire it. Deleting pages that still earn traffic or links does more harm than the thin content did, and consolidating two near-identical pages almost always beats deleting either. The point is to decide page by page on the evidence, not to cut for the sake of a lower page count.

Is this an E-E-A-T audit?

In substance, yes. Experience, expertise, authoritativeness and trust run through the scoring — but E-E-A-T isn't a score you can buy or a checklist you can tick. It's evidence on pages: who stands behind the advice, whether claims are dated and sourced, whether the page shows first-hand knowledge. The audit names the missing evidence per page section, which is what makes it fixable.

Is AI content bad for SEO — do you check for it?

I don't use AI-content detectors, and the question they answer isn't the one that matters. The standards judge usefulness and evidence, not authorship. A page a human paraphrased eighty times to fill a template fails the same way an AI-generated one does — thin, interchangeable, nothing a buyer can use — and a page with real expertise behind it passes however it was drafted. What the audit does catch is sameness at scale, AI-written or not: it measures how much of your content is interchangeable between pages, which is where most "low-quality AI content" problems show up.

Is this Google penalty recovery?

No — an update hit isn't a penalty. But it usually signposts the same underlying problem: widespread quality issues, which is exactly what this audit finds and fixes. A manual action is a different thing — an actual penalty, with a notice in Search Console — and a specific job: fix the violation, document it, file the reconsideration request. Manual actions are rare, but if you've had a notice, I can help with that too.

Can you guarantee recovery?

No, and be careful with anyone who does. What I guarantee is a correct reading of the evidence: what was hit, what was spared, why, and the plan that follows. Most drops are recoverable when the diagnosis is right — and reassessments register when Google re-evaluates, which mostly means at later updates, so recovery is measured at those checkpoints rather than week to week. Core updates have historically landed every two to four months, so the first checkpoint usually falls within a quarter of the fixes shipping.

How is this different from an SEO content audit?

The SEO content audit is an inventory decision: it works through everything you have published and rules on each piece — keep, merge, refresh, retire or differentiate — based on how it performs. This quality audit answers a different question: why pages fail the quality bar, and which templates and systems keep producing pages that do. A big archive that has stopped earning usually needs the content audit; a template-built site, or one hit by an update, usually needs the quality audit. If it's unclear which fits, say so in the enquiry and I'll point you to the right one.

How long does the audit take?

A content quality audit usually completes in two to three weeks, depending on the size of the site and how quickly access is set up. When the diagnosis phase runs, its first read lands within days — the what-happened answer doesn't wait for the full document. The walkthrough call is booked as soon as everything is ready.

See all SEO audits