These are the two explanations most often offered for a traffic collapse, and they are almost nothing alike. One is a person deciding your site violated a policy. The other is a system reassessing which results serve a query best. Confusing them means pursuing a remedy that does not exist.
The distinction in one check
Open Search Console, Security and Manual Actions, then Manual Actions.
- Something listed: a manual action. It names the type and scope, and there is a defined process to clear it.
- “No issues detected”: not a manual action. Whatever caused your decline, it was not this.
That check takes seconds and resolves the question definitively. There is no ambiguous middle case, and no such thing as an unreported manual action.
How they differ
- Notification: manual actions are reported explicitly. Algorithm updates are never reported for your site specifically.
- Cause: a policy violation versus a reassessment of relative quality.
- Fault: a manual action means something was done wrong. An update impact frequently means nothing was.
- Remedy: a manual action has a reconsideration process. An update has none.
- Timing: manual actions apply at a point. Update impacts develop over a rollout window.
- Recovery: clearing an action lifts it. Update recovery usually waits for a subsequent update.
Why algorithm updates get blamed so often
Updates are widely reported, so any decline in the same fortnight acquires a ready explanation. That explanation is comfortable because it implies nothing was done wrong, and it stops the investigation before the actual cause is found.
Before accepting it, test it: update impacts begin within a day or two of rollout and are usually broad rather than confined to one template. A decline that started a week earlier, or that affects only your product pages, is not an update. See algorithm update recovery.
What each actually requires
Manual action
- Identify the full scope, since partial actions cover specific sections.
- Fix the underlying violation properly rather than minimally.
- Submit a reconsideration request describing what was wrong and what changed.
- Wait for human review, which cannot be accelerated.
- Detail on manual action recovery.
Algorithm update
- Confirm the update is genuinely the cause before acting.
- Segment to see what lost and what held.
- Compare your losing pages against what replaced them and name the gap.
- Improve genuinely, then wait for reassessment.
- There is nothing to submit and nobody to appeal to.
The third possibility people overlook
Most declines are neither. They are self-inflicted: a directive shipped with a deployment, content shortened during a redesign, URLs changed without redirects, or your own pages now competing. These are more common than both of the above combined, and cheaper to fix. Check your change log before reaching for either explanation. See why Google rankings dropped.
Frequently asked questions
Can I have both at once?
Possible but uncommon. Check Manual Actions first, since that is definitive. If one exists, address it before considering anything algorithmic.
How do I appeal an algorithmic decline?
You cannot. There is no submission process because nothing was applied to your site. The only route is genuine improvement and reassessment at a later update.
Are manual actions common?
No. They are rare relative to how often the word penalty is used. Most sites that believe they have one do not, and Search Console will confirm it either way in seconds.
Does a manual action affect the whole site?
Not necessarily. Partial actions affect specific URLs or sections, and Search Console states which. Fixing one example while others remain will not clear it.
Consulting CTA
If traffic has fallen and you are unsure which explanation applies, book an SEO consultation to establish the cause before acting on the wrong one.