Google penalty recovery starts with one question: was it a penalty at all? A manual action is a decision by a Google reviewer, it’s listed in Google Search Console’s Manual actions report, and you recover by fixing every affected page and requesting a review. A core-update drop is algorithmic: there’s no notice and nothing to appeal, and recovery depends on improving the site and waiting for Google to reassess it. At #10, we separate the two before recommending any work, because the fixes are different and doing the wrong one wastes months.
Most ecommerce drops in organic traffic aren’t Google penalties in the strict sense. A migration or theme change accounts for a lot of them. So does a broken analytics tag, a seasonal dip, or a change to the results page itself. Treating every bit of lost traffic as a penalty leads to panicked link disavows and deleted pages that make things worse.
This guide is about understanding Google penalties well enough to tell the causes apart, what each kind of recovery involves, and what’s realistic. We won’t promise a recovery date or a traffic number. Nobody outside Google can, and anyone who does is guessing.
Types of Google penalties, and drops that only look like one
There are three broad families of cause, and only the first is a penalty in the sense Google uses the word. People often talk about manual penalties and algorithmic penalties as two penalty types, which is a useful shorthand as long as you remember that Google doesn’t describe its ranking systems as penalizing anyone.
| Type of drop | How you know | How recovery works |
|---|---|---|
| Manual action | Listed in Search Console’s Manual actions report, with a message | Fix every affected page, then request review |
| Algorithmic (core or spam update) | Timing matches an update on the Search Status Dashboard; no message | Improve or clean up the site; wait for systems to reassess |
| Not a penalty | Timing matches a site change, the season or a tracking change | Fix the technical cause, or adjust plans to demand |
Manual actions are applied when a human reviewer at Google finds pages that break its spam policies. Google’s Manual actions report documentation lists the types, from unnatural links and thin content to structured data issues and site reputation abuse. If you’re hit with a Google penalty of this kind, you get a notification in Google Search Console and by email, and there’s a defined process to send a review request to Google.
Algorithmic drops come from Google’s automated ranking systems. Core updates are broad changes to how Google assesses content. Google’s guidance on core updates says plainly that they don’t target specific sites or pages. Spam updates are different: they’re automated, but aimed at spam patterns like manipulative link building or scaled low-quality pages. Neither comes with a message, and neither has a review button.
Everything else covers the causes Google lists in its own guide to debugging traffic drops: technical problems, security issues, site moves and migrations, seasonality and changing interest. In our experience these are where an ecommerce investigation should start, because they’re the most common and the quickest to rule in or out.
Was it a penalty or an update? Work through it
Answer each question with your Search Console account open. The tree follows the order we use: rule out measurement problems first, then the causes Google tells you about, then the ones it doesn’t.
<div class=“google-penalty-recovery-ecommerce-tree” data-explainer=“google-penalty-recovery-ecommerce-tree”>
<ol>
<li><strong>Does Search Console show the drop, not just analytics?</strong> If not, check tracking and tags before anything else.</li>
<li><strong>Does the Manual actions report list an action?</strong> If so, it’s a manual action: fix every affected page and request review.</li>
<li><strong>Does the Security issues report show a problem?</strong> If so, clean the site and request a security review.</li>
<li><strong>Did you migrate, redesign or change redirects, robots rules or templates just before the drop?</strong> If so, look for a technical cause first.</li>
<li><strong>Did the drop start during a Google update on the Search Status Dashboard?</strong> A spam update points to an algorithmic spam demotion; a core update points to a reassessment of quality.</li>
<li><strong>Did the same pages dip at this time last year?</strong> If so, it’s probably seasonality or falling demand.</li>
<li><strong>Are impressions steady while clicks fell?</strong> If so, the results page has probably changed around you.</li>
</ol>
</div>
The tree is a starting point, not a diagnosis. Drops often have more than one cause, and a core update that lands the same month as a theme change is a real possibility. That’s why the next step is always to confirm the drop in the data.
Step one: confirm the drop and find its shape
Before deciding what happened, find out exactly what dropped. “Traffic is down 30%” isn’t specific enough to act on.
We pull at least 16 months of Search Console performance data, so the same period last year is visible, and compare the drop period with a matching period before it. Then we split it:
- By page type. Product pages, collection or category pages, blog articles and the homepage. A drop concentrated in one template points somewhere different from a site-wide drop.
- By query. Branded searches (people looking for you by name) versus non-branded. Branded drops usually mean less demand or a tracking problem, not a ranking problem.
- By device, country and search type. Web, image and shopping results can move independently.
- Clicks versus impressions. If impressions hold and clicks fall, you’re still being shown but chosen less, often because of AI Overviews, ads or shopping units above you.
Then we line the dates up against three timelines: Google’s Search Status Dashboard, which lists confirmed updates and their rollout dates; your own change log (deploys, app installs, migrations, redirect edits); and the marketing calendar. A drop that starts the day a new theme went live is rarely a coincidence.
Manual action recovery: fix everything, then ask
If the Manual actions report lists an action, you have a penalty in the plain sense, and you also have the clearest path out. Google tells you what the problem is and gives sample pages.
For an online store, the manual actions we’d look at first are:
- Unnatural links to your site: backlinks bought, swapped or built through networks to manipulate rankings, often with exact-match anchor text that gives them away.
- Thin content with little or no added value: large sets of near-empty pages or duplicate content, including product pages built only from manufacturer descriptions or category pages generated at scale.
- Hidden text and keyword stuffing: blocks of keywords written for a search engine rather than for shoppers, sometimes hidden in collection footers.
- Structured data issue: markup that doesn’t match what’s on the page, such as review stars or prices that aren’t visible to shoppers.
- User-generated spam: spam in reviews, Q&A or comment sections.
- Site reputation abuse: third-party content hosted on your domain to borrow its standing.
Recovery follows Google’s process. Fix the issue on every affected page, not just the samples, because Google says that fixing some pages won’t earn a partial return. Make sure the fixed pages are reachable (not behind a login or blocked by robots.txt). Then submit a reconsideration request (Google calls it Request Review) from the report, explaining what went wrong, what you changed and the evidence. Google says reviews usually take several days to a few weeks, and link-related reviews can take longer.
The disavow tool belongs here, and mostly only here. For a link action, the recovery process is an audit of the whole backlink profile, not just the sample links Google shows. Export links from Search Console and a third-party tool, then sort out the paid and network links. Ask site owners to remove what you can. Google’s disavow guidance says most sites don’t need it and that it’s meant for cases where spammy links have caused, or are likely to cause, a manual action. A request for review after a link-related action should show the links you removed and the ones you disavowed because you couldn’t get them removed.
Core-update recovery: improve, then wait
A core update isn’t a penalty, and there’s nothing in Search Console to fix. Google has changed how it weighs pages for the queries you compete on, and your pages now rank lower in the search results than the alternatives it prefers. The recovery strategy is to improve content quality on the pages that lost, not to hunt for a hidden penalty.
Google’s guidance is specific about what to do:
- Wait for the rollout to finish. Then wait at least a week before comparing with the week before it started. Reading the data mid-rollout misleads.
- Size the drop. A small move needs no drastic action. Google explicitly warns against changing pages that are already performing well.
- For a large, sustained drop, assess the affected pages honestly. Are they the most useful and reliable answer for the query? Do they show first-hand expertise, with sources where a claim needs one?
- Avoid quick fixes. Deleting large sections, stripping page elements because of a supposed SEO rule, or rewriting everything at once makes it impossible to see what helped.
- Expect it to take time. Google says some improvements can show within days, but it can take several months for its systems to recognize them, and sometimes the next core update is when they show.
On ecommerce sites, the pages that tend to lose in a core update have the least of their own to offer. Think of collection pages with a sentence of generic text, product pages that repeat the manufacturer’s copy, and buying guides written to a keyword rather than to a buyer’s question. The fix is rarely more words. To improve content in a way that lasts, add high-quality specifics only you can provide, like sizing notes drawn from your returns data, or honest answers to the questions your customer service team hears every week.
Google folded its helpful content system into its core ranking systems in 2024, so recovering from the old helpful content update and recovering from a core update are now effectively the same work. Google’s quality guidelines, formerly Google’s webmaster guidelines and now called Search Essentials, are the reference for both. They put the emphasis on quality and relevance to the searcher rather than on any single ranking trick.
Spam-update recovery: remove the pattern at the source
Spam updates sit between the two, and they’re what most people mean when they say a site was affected by an algorithmic penalty. Google doesn’t describe it as choosing to penalize a site, but the effect on traffic is the same. They’re algorithmic, so there’s no message and no review request, but they target specific patterns. If a drop lines up with a spam update rather than a core update, look for the pattern it was aimed at. That usually means links bought or exchanged at scale, large numbers of auto-generated pages, or third-party content hosted on your domain.
Remove the pattern rather than hiding it. Google’s systems need to recrawl and reassess the site, which takes months, and there’s no way to speed that up with a request.
When it isn’t a penalty: migrations and other self-inflicted drops
On ecommerce sites, the drop we look for first is the one the site caused itself. A platform migration with an incomplete redirect map can cut traffic overnight. So can a theme change that puts a noindex tag on collection templates, an app that rewrites canonical tags, or a robots.txt file copied from a staging site. They look like penalties to the people watching the dashboard, and they’re usually faster to fix than any penalty.
Our guide to the technical SEO audit covers those checks in order, and what gets lost in a Shopify migration covers the migration-specific ones. For a quick first look at a single page, our instant site audit checks the basics a crawler sees, including indexability, canonicals and robots.txt.
It’s also worth checking whether you lost visibility or just clicks. If AI answers now sit above your results, you may still be the source those answers draw on, without the click. Tracking whether AI assistants name you, as in our sample AI visibility report, tells you which of those is happening.
What this looked like for a premium olive oil and wine brand
Our relationship with a premium California olive oil and wine brand began in 2014, when the brand’s search visibility was already under pressure. An outside firm’s penalty report had tied traffic drops on the site to several separate causes: inbound links from a link network, a broader algorithmic issue, problems with the site’s HTTPS setup, and DMCA complaints.
That mix is typical. It wasn’t one penalty with one fix. Our first scope of work combined an SEO audit and a technical audit of the brand’s previous store with link cleanup and the explicit job of cleaning up the site’s risk from Google algorithm updates. The audit found its own technical issues alongside the penalty causes, such as temporary redirects that should have been permanent, duplicate title tags and missing breadcrumb markup.
The specific penalty categories from 2014 reflect how Google worked then, when Google Panda (aimed at low-quality content) and Google Penguin (aimed at manipulative links) still ran as separate updates, and Search Console was still called Google Webmaster Tools. Both have since been folded into Google’s core systems. The method still holds: separate the causes, fix each at its source, and keep watching after the cleanup. More than a decade later we still run search work for that brand, now on Shopify Plus.
Questions ecommerce teams ask about penalty recovery
How do I know if I have a Google penalty?
Open the Manual actions report in Search Console. If it lists an action, you have a manual penalty and Google will tell you what it’s about. If it’s empty, any drop is algorithmic or has another cause, and there’s nothing to appeal.
How long does Google penalty recovery take?
For a manual action, the review itself usually takes days to weeks once you’ve fixed everything, longer for link issues. To recover your rankings fully can take longer than the review. Rankings may not return to where they were, because the pages may have been ranking partly on what was removed. For core-update drops, Google’s own guidance talks in months, sometimes until the next core update.
Should we hire a Google penalty recovery service?
If you have a manual action and don’t have someone who has handled one before, professional Google penalty help saves time, mostly in getting the cleanup complete the first time. Be wary of SEO services that guarantee a date or a ranking, or that offer a penalty fix without looking at your data first. Our SEO programs page lists penalty recovery as its own project, with diagnosis first.
Do we need to disavow links after a core update?
Usually not. Core updates are about content and usefulness, not links, and Google says most sites never need the disavow tool. Disavowing is for link-related manual actions or a clear, large-scale link problem you can’t get removed.
Can a Shopify migration look like a Google penalty?
Yes, and it’s one of the first causes we check when a store’s traffic falls suddenly. Missing redirects, changed URLs and new templates with different indexing rules all cut traffic in ways that look like a penalty. The fix is technical, not a reconsideration request.
Will a reconsideration request fix a core-update drop?
No. Review requests only apply to manual actions. If there’s no manual action, there’s nothing for a reviewer to reconsider.
Where to start
Open Search Console and check the Manual actions and Security issues reports first; it takes two minutes and rules the clearest cases in or out. Then work through the decision tree above with 16 months of data in front of you. If the answer is a manual action, a technical regression or an unclear core-update drop, talk to #10. We’ll start with a diagnosis, tell you which kind of drop you’re dealing with, and only then propose the recovery work.
