"We got hit by the algorithm" is the single most overused sentence in small business SEO. Nine times out of ten we hear it, the problem is something far more boring: a broken sitemap, a deindexed page, a robots.txt change someone made and forgot about months ago, or a seasonal dip dressed up as a crisis. Before anyone touches the word "update", we open Search Console. It takes five minutes and it settles most arguments before they even properly start.
Start With Coverage, Not Rankings
The Performance report is where most people look first, and it's the wrong starting point entirely. Coverage tells you whether Google can actually see your pages at all, which matters more than where they rank if they're not even indexed. We had a Clacton-on-Sea café client convinced a core update had buried her menu page. It hadn't, not even close. A plugin update had quietly added a noindex tag to eleven pages overnight, including the menu, during a routine WordPress update nobody had tested first. No algorithm did that. A badly tested plugin did, and it took us ten minutes to find once we knew where to look.
Coverage issues like this are disturbingly common, and they rarely announce themselves. A caching plugin update, a security plugin tightening its rules a little too aggressively, a hosting migration that quietly changed how the server handles crawler requests — any of these can strip visibility from a handful of pages without a single visible change on the front end of the site. The owner keeps browsing their own website, sees nothing wrong, and assumes the problem must be external. Checking Coverage first rules all of that in or out within minutes, rather than weeks of guessing.
Check For Manual Actions First
This one gets skipped constantly, and it really shouldn't be. The Manual Actions report sits under Security & Manual Actions and takes ten seconds to check once you know the path to it. If there's a manual action listed, that's not a core update at all — that's a human reviewer at Google flagging something specific, usually linked to spammy links, thin content, or sneaky redirects left over from a previous site owner. Manual actions and algorithmic drops need completely different fixes, and conflating them wastes weeks of effort, and often real money, aimed squarely at the wrong target.
Most business owners have never even opened this section of their account, which isn't surprising given how buried it is in the interface. We make it the very first screenshot in any diagnostic call now, mostly because ruling it out costs nothing and takes no time at all, and because it's the one check that completely changes the rest of the conversation if something actually turns up there.
Read The Performance Graph Properly
A sudden cliff on a specific date lines up with an algorithm change, and that's usually easy to spot once you're looking at the right date range. A slow, gradual decline over six weeks usually doesn't — that's more often content ageing badly, a competitor genuinely outpacing you with better content, or straightforward seasonality nobody accounted for. A shop in Billericay selling garden furniture sees traffic fall every October regardless of what Google does that month. That's not an update. That's autumn, plain and simple, and no amount of SEO work changes that pattern.
Set the date comparison to the same period a year earlier too, not just the previous month. A lot of "sudden drops" turn out to be perfectly normal when you look at last year's graph and see the exact same dip at the exact same point on the calendar. We've had this conversation with at least three different Essex retailers now, all convinced something had gone badly wrong in late summer, when their own historical data showed the identical pattern every single year without fail.
Compare Queries, Not Just Totals
Click into the Queries tab and compare the eight weeks before and after the suspected date, side by side rather than relying on memory. If you've lost visibility on dozens of unrelated queries across the whole site, that smells like an algorithmic reassessment touching the site broadly. If the drop is concentrated on three or four specific terms, that's usually a competitor outranking you on those specific pages, or a SERP feature — a new "People Also Ask" block, an AI Overview, a featured snippet someone else grabbed — eating the click-through rate rather than your actual ranking position falling at all.
Don't Ignore The URL Inspection Tool
For any page that's apparently vanished, run it through URL Inspection directly rather than guessing. It'll tell you the last crawl date, whether the page is indexed, and if there's a canonicalisation issue pointing Google somewhere else entirely without you realising. We fixed a Thurrock logistics company's "missing" service page in about four minutes this way — it was indexed, fine, just canonicalised to a near-duplicate page by mistake, probably from a CMS default nobody had checked since the site was built two years earlier.
This tool also tells you something people forget to check: whether the live page on the server actually matches what Google last crawled. Developers sometimes push a change and assume it's live everywhere instantly, when Google might still be working from a version crawled three weeks ago. If you've recently fixed something and nothing's changed in rankings, requesting indexing directly from this tool — rather than just waiting and hoping — at least confirms Google has seen the fix rather than leaving you guessing whether it noticed at all.
The Server Logs Most People Never Pull
If Search Console looks clean but traffic's still down, the next step is server log analysis — checking whether Googlebot's crawl frequency itself has changed over recent weeks. A drop in crawl rate can precede a visibility drop by weeks and tells you something's wrong with crawl budget or server response times before rankings even move noticeably. It's a more technical step, admittedly, and we don't pull logs for every client every month — it's reserved for cases where the easier checks turn up nothing useful at all.
Why We Insist On This Order
We've had clients push back on this process because they want the exciting answer — "Google changed the rules" feels like something happened to you, not something you could have prevented. A broken canonical tag feels embarrassing by comparison, almost too mundane to explain a real traffic drop. But embarrassing problems are fixable in an afternoon, usually for free. Algorithmic reassessments take months to recover from, if they recover at all without real, substantive changes to the site itself. Given the choice, you want the boring diagnosis every single time, even if it's less satisfying to tell people at a dinner party.
One Witham client admitted, after we found his issue was a stray robots.txt line blocking an entire folder, that he was almost disappointed it wasn't something more dramatic. We understand the feeling, slightly, but we'd rather hand someone a boring, fixable answer within the hour than let them spend a worried fortnight waiting on an algorithm to supposedly change its mind about a site that was never actually assessed in the first place.
The Bottom Line
Blaming the algorithm is the easy explanation and, most of the time, the wrong one entirely. A proper technical check-up through Search Console, manual actions, query-level comparisons and crawl data will usually surface the real cause within an hour, long before you need to start rewriting content or chasing a Google update that may not even apply to your specific site. We run this exact sequence for every client who comes to us convinced they've been hit, and more often than not, a closer look at the technical side finds something fixable that was never about the algorithm at all, and that's usually good news once the embarrassment wears off.
Looking for SEO agency in Essex?
Let's talk about what your business actually needs
Digital Impact Ventures provides SEO, AI visibility and digital marketing support for businesses across Colchester and Essex. Get in touch and we will talk through where your business is now and where it needs to go.