Algorithm Update vs. Technical Issue
How to tell whether a traffic drop is a Google algorithm update or a technical fault on your own site, using timing, scope and four Search Console checks.
Tell an algorithm update from a technical issue by shape and timing: a gradual, sitewide decline that starts within days of a confirmed Google update usually means the update, while a sharp cliff on one specific day — especially one matching a deploy — usually means a technical fault. Neither cause announces itself directly, so both need confirming, not assuming.
This is the head-to-head version of the broader triage in the organic traffic drop guide, narrowed to the two causes people confuse most often, because the fix for one does nothing for the other.
On this page
What's the core difference between these two causes?
An algorithm update changes how Google evaluates content or links across the web and reflects a judgment about quality or relevance; a technical issue is a fault in how your own site is built, served, or tagged that stops Google from crawling, indexing, or ranking it the way it otherwise would. One is a change in the evaluator; the other is a change in what is being evaluated.
That distinction is why the fixes are unrelated. Fixing a technical fault — restoring a blocked robots.txt line, removing a stray noindex tag, repairing a broken redirect — has an immediate, mechanical effect once Google recrawls the page. Responding to an algorithm update means improving the actual content or site in the ways the update is rewarding, which is slower, less certain, and does not resolve on any fixed schedule.
There is a third possibility worth naming here even though it is not the subject of this page: a manual action, where a human reviewer at Google flagged something specific. That one is the easiest of the three to confirm, because it shows up directly in the Manual actions report inside Search Console — see check for a Google penalty for that check specifically. Rule a manual action out first, since it takes thirty seconds, before spending longer comparing timing and scope for the other two.
How does the timing differ?
Algorithm updates roll out on Google's own schedule and are listed on its ranking releases page, typically unfolding over one to three weeks rather than landing all at once [2]. A technical fault has no schedule at all — it starts the moment a bad deploy ships, a certificate expires, or a configuration changes, and the drop that follows is usually visible within a day or two.
There is a subtlety worth flagging: a rollout date and a full-effect date are not the same thing. Google frequently announces a core update's start and, separately, when the rollout has finished, and the gap between the two can run a week or more. If your drop began on day three of a listed rollout and kept sliding through day twelve, that is still consistent with the update — it does not mean a second, separate cause joined in partway through. Read the full rollout window, not just the announcement date, before ruling an update out.
How does the shape of the drop differ?
A core update produces a slope — traffic declining over days to weeks as the update finishes rolling out across data centers and query types [1]. A technical fault produces a cliff — a visible, near-vertical drop concentrated around a single date, because whatever broke either works or does not; there is no gradual version of a robots.txt line blocking a folder.
| Signal | Algorithm update | Technical issue |
|---|---|---|
| Shape | Gradual slope over 1–3 weeks | Sharp cliff, often overnight |
| Scope | Broad, across many templates | Often one template or URL pattern |
| Timing match | Aligns with a listed update window | Aligns with a deploy or config change |
| Manual actions report | Empty | Empty |
| URL Inspection tool | Pages indexed normally | Often shows a block, noindex, or error |
| Recovery after a fix | Waits for next reassessment | Often visible within days of recrawl |
What does scope tell you that timing doesn't?
A lot. Algorithm updates evaluate content and relevance signals broadly, so a real update-driven drop tends to touch a wide mix of templates, sections and query types rather than one isolated corner of the site. A drop that hits exactly one URL pattern — every product page, say, or everything under one folder — while the rest of the site is untouched is a scope signature that points much harder toward a shared template fault than toward an update, because updates do not usually know or care which folder a page lives in.
Run the same split-by-page check described in SEO diagnostic tools: if the drop maps cleanly onto a template boundary, that is stronger evidence than the calendar alone.
Be careful with one common trap: a large site can have a drop that is technically confined to one template but still looks broad in raw numbers, simply because that template accounts for most of the site's pages. Look at percentage change within each template or section, not just absolute page counts, so a category page template that lost 40 percent of its traffic does not get lost inside a sitewide total that only moved 8 percent.
Check the Search Status Dashboard first
Rule out a Google-side outage or serving issue in under a minute before you investigate anything on your own site.
Match the date against the ranking releases page
A same-week match with a listed core or spam update is your first real data point, not a confirmation on its own.
Diff your deploy log against the same date
A same-day match with a release is usually the stronger and more actionable signal of the two.
Run the URL Inspection tool on affected pages
A block, a noindex tag, or an indexing error here settles the question almost immediately.
Check scope with a page-level breakdown
Sitewide and broad points to an update; confined to one template points to a technical fault.
Can the two happen at the same time?
Yes, and this is where most self-diagnoses go wrong. A site that redeploys a template, ships a redesign, or migrates a CMS in the same window a core update rolls out will show a drop that has features of both — a cliff from the deploy layered under a slope from the update. Treating it as one cause means fixing the technical half, seeing partial recovery, and then wrongly concluding the whole problem is solved.
The way through this is sequencing, not more guessing. Fix every technical fault you can confirm first, because those are within your control and their effect is fast and measurable. Once the technical layer is cleared, whatever traffic gap remains is either the algorithmic component working through its own timeline or a sign you have not found every technical fault yet — and at that point, causes of SEO traffic drops is the fuller checklist for what else might still be sitting underneath.
Keep a written log of exactly what changed and when, separate from your general deploy history. Note the date you fixed each technical item, not just the date the drop started. Without that log, a recovery that shows up three weeks later is impossible to attribute correctly — you will not be able to tell whether it was the redirect you fixed in week one or the reassessment the update itself completed in week three, and that ambiguity is exactly what leads teams to draw the wrong lesson from a real recovery.
What does fixing each one actually cost?
A technical fault is usually cheap to fix and expensive to have missed. Restoring a robots.txt line or removing a stray noindex tag is minutes of engineering time once found — the real cost is the weeks spent not finding it. An algorithmic cause is the opposite: there is no quick fix, and the cost is genuine content or site-quality work that takes real time regardless of how it is staffed. Our technical SEO service is built around finding the first kind fast, specifically so teams stop paying the "weeks spent not finding it" cost that technical faults are most expensive for.
What if it's genuinely just an update — is there anything to do?
Yes, though it takes longer to see results. Compare the pages that dropped against pages — yours or a competitor's — that held or gained for the same queries, and look honestly for a real gap: thinner content, less first-hand detail, a weaker match to what the query actually wants. Google's own technical guidance is explicit that the fundamentals — crawlable, indexable, genuinely useful pages — remain the baseline every update is built on top of [4], which means an update-driven drop is rarely arbitrary even when it feels that way.
This is also where the timeline gets confused with seasonality. A gradual decline that started around an update date but continues past the update's rollout window, or that shows up every year around the same season, may not be the update at all — see seasonality vs SEO decline before committing months of content work to a cause that resolves on its own every January.
How do you know when the fix actually worked?
For a technical fault, watch the affected pages recrawl and reindex — the URL Inspection tool will show a fresh "Last crawl" date, and traffic on those exact pages typically moves within one to two weeks of that recrawl, faster on pages Google already crawls frequently and slower on ones it visits rarely. For an algorithmic cause, there is no equivalent quick signal; you are watching for the next core update or the next scheduled reassessment to reflect the changes you made, which is a multi-week to multi-month wait with no reliable way to speed it up. SEO recovery results walks through what that waiting period actually looks like on a real timeline, including the plateau that makes people think a genuine fix has failed when it has not yet had time to register.
Questions people also ask
What's the fastest way to tell these apart?
Check the shape of the drop first. A cliff that starts on one specific day almost always points to a technical fault or a deploy; a decline that unfolds gradually over one to three weeks points to a core update. That single check rules out one of the two candidates for most sites.
Can it be both at the same time?
Yes, and it happens more often than people expect. A site that deploys a redesign in the same week a core update rolls out will show a drop that looks like one cause but is really two stacked together, which is why timing alone is a clue, not a verdict.
Does Google tell you which one happened?
Only partially. Confirmed algorithm updates are listed on Google's ranking releases page, and manual actions show in Search Console — but a technical fault is never announced anywhere; you have to find it yourself.
If it's a technical issue, how fast can traffic recover?
Often within days to a few weeks of the fix shipping and the pages being recrawled, because there is no reassessment lag the way there is with an algorithmic signal. That speed is itself a diagnostic clue if you are still unsure which cause you are looking at.
If it's an algorithm update, is there anything to actually do?
Yes — algorithm updates almost always reward something specific, even when Google doesn't spell it out. Compare what dropped against what still ranks well for the same queries, and look for a real quality or relevance gap rather than waiting it out.
Sources
- Debug Google Search Traffic Drops — Google Search Central (checked 22 September 2026)
- Latest Google Search Documentation Updates — Google Search Central (checked 22 September 2026)
- Google Search Status Dashboard — Google (checked 22 September 2026)
- Google Search Essentials — Google Search Central (checked 22 September 2026)
Get a confirmed diagnosis before you spend weeks on the wrong fix
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Jeremy ZavaCo-founder
Leads growth and client partnerships.
Works on: CRO, SEO
Reviewed before publishing by Ibrahem Helal, Co-founder.
- Causes of SEO Traffic DropsThe nine most common causes of an SEO traffic drop, the signal each one leaves in Search Console, and how to tell which one is hitting your site.
- SEO Diagnostic Tools for a Traffic DropThe tools that actually diagnose a traffic drop — free and paid — what each one tells you, and the order to run them in so you don't waste a day.
- Seasonality vs. SEO Decline: How to TellHow to tell a seasonal traffic dip from a real SEO decline using year-over-year comparisons, Google Trends, and the signals that rule seasonality out.
- Helpful Content Recovery: A Step-by-Step PlanHow to recover from a helpful content hit: what the classifier actually penalizes, the fixes that move it, and a realistic timeline for getting traffic back.