Rankings Dropped After a Google Update? What to Check First
A sudden drop in local rankings gets blamed on "the algorithm" a lot faster than it gets diagnosed. Here's how to confirm it's actually a core update, what Google's own guidance says to check, and what recovery realistically looks like for a home service business.
Short answer: check whether your drop's timing matches a confirmed broad core update on Google's Search Central blog and Search Status Dashboard, rule out a manual action in Search Console's Manual Actions report, and rule out a technical regression before assuming the algorithm is the cause. If it is a core update, Google's own guidance is to honestly assess whether your site's content is helpful and people-first rather than chase a specific technical fix — and to expect recovery, if it comes, to show up around the next core update rather than immediately.
Why This Gets Confused With Other Ranking Problems
A lot of local business owners see a ranking drop and jump straight to "Google changed something" because it feels like the least controllable, least personal explanation. Sometimes that's exactly right — Google does ship broad core updates several times a year that reassess how it evaluates content across the entire index, and a home service site can absolutely move because of one without having done anything wrong. But a drop that coincides with a core update isn't proof the update caused it. A site redesign that shipped the same month, a Google Business Profile that got flagged as a duplicate, or a manual action for a policy violation can all produce the same symptom — fewer calls, lower positions — with a completely different fix.
This matters because the fix is different for each cause. Content and helpfulness improvements are the right response to a core update. They do nothing for a manual action, which needs a reconsideration request after the underlying issue is fixed. And neither one helps a Google Business Profile duplicate or a broken canonical tag, which need a completely different, more mechanical fix. Diagnosing which one you're actually dealing with comes before deciding what to do about it.
Common Causes of a Post-Update Ranking Drop
| Likely Cause | How to Tell |
|---|---|
| A confirmed broad core update rolled out around the same time | Google announces broad core updates on the Search Central blog and tracks their rollout on the Search Status Dashboard. If your drop lines up with a confirmed rollout window, a core update is the more likely explanation than something you did. |
| A Google Business Profile issue, not a web-ranking issue | A drop in Map Pack visibility that isn't matched by a drop in your organic web rankings often points to a GBP problem (suspension, duplicate, category change) rather than an algorithm update — check both separately before assuming one cause. |
| A manual action or policy violation | Check Search Console's Manual Actions report first. A manual action is a targeted, specific-site penalty with a stated reason — it is a completely different problem from a broad core update and needs a different fix (a reconsideration request, not content improvements). |
| A technical regression unrelated to any Google update | A site redesign, a broken robots.txt rule, a canonical tag error, or a slow new template can all cause a drop that coincides with an update by pure timing coincidence — rule this out with Search Console's coverage and page experience reports before blaming the algorithm. |
| Genuine content-quality reassessment across the site | Google has been explicit that core updates work by reassessing the pages it already crawled against updated criteria for helpful, reliable, people-first content — this is the cause behind most drops when the first four are ruled out. |
Confirming It's Actually a Core Update
1. Check the Search Status Dashboard and Search Central blog
Google logs the start and end dates of every confirmed broad core update. Google's own documentation notes rollouts can take up to roughly two weeks to complete — a drop that starts mid-rollout and keeps shifting for a couple of weeks is consistent with a core update; a drop that happens overnight with no announced update that week usually isn't.
2. Rule out a manual action first
Search Console's Manual Actions report will say explicitly if a human reviewer applied a penalty and why. This is a different problem with a different fix — a reconsideration request, not a content quality pass — so ruling it out early saves you from working on the wrong thing.
3. Separate Map Pack visibility from organic web rankings
If your Map Pack position dropped but your organic web rankings for the same terms didn't move, that points toward a Google Business Profile issue — see our guides on GBP not showing up and GBP suspension — rather than a core update, which typically affects both together.
4. Check for a technical regression that coincides by timing alone
Review Search Console's Coverage and Page Experience reports for new errors, and check whether a site change — a redesign, a new page template, a robots.txt or canonical edit — happened around the same time. A technical mistake that coincides with an announced update is a common false attribution.
What Google's Own Guidance Says to Do Next
Google's core updates documentation is unusually direct that there is no specific technical fix for a core update the way there is for a manual action — because a core update doesn't flag anything as a rule violation. The stated response is to use Google's published self-assessment questions to evaluate whether your site's content is genuinely helpful, reliable, and created for people first, rather than search engines: does it offer real depth on the topic, does it reflect direct experience with the trade rather than a rewritten summary of other pages, and would a reader trust it enough to act on it. Google also specifically warns against removing pages as a quick cleanup response — it recommends treating deletion as a last resort after a genuine content review, not a first reaction to a drop.
One detail worth planning around: Google has said that the effects of working on a page after a core update often aren't visible in rankings until the next core update ships, because the reassessment that caused the movement is re-run at the next broad update rather than continuously. That means a realistic recovery timeline is measured in months, tied to Google's next confirmed rollout, not the next crawl.
Where Home Service Sites Are Most Exposed
A local business site with genuinely specific, useful service and trade pages tends to be less exposed to a core update reassessment than a site built around dozens of thin, near-identical city or trade pages generated with little unique detail per page. If your site leans heavily on templated pages that repeat the same content with a city name swapped in, a core update is exactly the kind of event that tends to surface that pattern — worth an honest look before assuming the update itself is the whole story.
Not Sure What Actually Caused Your Drop?
We check for core-update timing, manual actions, GBP issues, and technical regressions separately as part of every SEO audit — diagnosing the cause comes before recommending a fix.
Reducing Exposure to the Next Update
You can't predict what a future core update will weigh differently, but you can reduce how exposed your site is to any given one. Write service pages that reflect actual, specific experience with the trade rather than generic descriptions that could apply to any competitor. Avoid publishing dozens of near-duplicate location or trade pages with the same paragraphs and a swapped city name — that pattern is one of the more consistent things Google has said its systems are built to catch. And keep a running log of what you change and when, so the next time rankings move, you have your own timeline to compare against Google's announced rollout dates instead of guessing after the fact.
This overlaps with our local SEO checklist for the site-level basics, and why your business isn't showing up in Google Maps for the Map Pack-specific causes that are easy to mistake for a core update.
Frequently Asked Questions
How do I know if a ranking drop is actually a Google core update and not something else?
Check the timing against Google's own record of confirmed rollouts on the Search Central blog and the Search Status Dashboard, then check Search Console's Manual Actions report to rule out a targeted penalty, and check whether the drop is sitewide or limited to a handful of pages. A sitewide, gradual drop that matches a confirmed rollout window points to a core update. A sudden drop on specific pages with no matching rollout points somewhere else — often a technical issue or, less commonly, a manual action.
What does Google actually recommend doing after a core update drop?
Google's own core updates documentation is direct that there's no specific fix for a core update the way there is for a manual action, because nothing was flagged as against the rules in the first place. The guidance is to step back and honestly assess whether your site's content is helpful, reliable, and created for people first rather than primarily to attract search traffic — using Google's published self-assessment questions — and to treat page removal as a last resort rather than a first response.
How long does it take to recover rankings after a core update?
Google has said recovery from a broad core update's effects is often not visible until a subsequent core update ships, because the reassessment that caused the drop only gets re-run at the next broad update — not continuously. That means realistic recovery planning is measured in months, not days, and a page edited this week may not show a ranking change until Google's next confirmed core update rolls out.
Should I delete pages that dropped in rankings after an update?
Not as a first move. Google specifically calls out deletion as something site owners reach for too quickly, and recommends it as a last resort rather than a cleanup ritual. Look first at whether the page genuinely serves the searcher, whether it duplicates or thinly rewrites information available elsewhere, and whether it was written primarily to rank rather than to answer the question — fixing those issues in place is usually the better first move than removing the page and losing whatever ranking history it had.
Do local home service businesses get hit by core updates the same way as blogs and publishers?
Yes, in the sense that the same helpful-content criteria apply, but the practical exposure often looks different. A home service site with genuinely useful, specific service pages and honest claims tends to be less exposed than a site built mostly around thin, near-duplicate city or trade pages generated at scale with little unique detail. If your site has dozens of near-identical location or trade pages, a core update reassessment is exactly the kind of event that surfaces that pattern.
Get an Honest Diagnosis, Not a Guess
We'll help you confirm whether a core update, a manual action, a GBP issue, or a technical regression is actually behind your drop — then build a plan around the real cause.