When can an SEO company recover from a penalty?
That depends first on what kind of penalty it is. A manual action, applied by a reviewer at Google and shown in Search Console, can be lifted once the problem is fixed and a reconsideration request is approved, so its timing is set by the quality of the fix and Google’s review queue. A drop caused by an algorithm change, such as a core update, has no request to file; recovery comes when Google’s systems reassess the improved site, which can take months and may wait for a later update. A company can control how fast and how well it fixes the site, but not when Google reviews or reassesses it.
Manual actions: fix, request, review
A manual action is listed in Search Console’s Manual Actions report, with the reason. The company fixes the cause across the whole site, documents what it did, and files a reconsideration request. Google’s manual actions documentation says reviews can take several days or weeks, and longer for some link-related requests, that you are emailed when the request is received and again when the review is complete, and that you should not resubmit before a final decision. If it is rejected, the next step is a more complete fix, not the same request sent again.
So the realistic answer for a manual action is a range: the time the fix takes, which depends on how widespread the problem is, plus a review period that Google sets. A company that has done the work properly can tell you when it will file the request; it cannot tell you the date of the decision.
Algorithmic drops: improve and wait
A fall after a core update is not a penalty in the formal sense, and there is nothing to request. The company improves the site based on what the analysis shows, and Google’s systems have to recrawl and reassess it. Google’s guide to core updates explains that some changes take effect within days while a broader reassessment can take several months, and that a site may need to wait for the next core update to see the full effect.
How long that wait could be is visible in Google’s own record. Its Search Status Dashboard lists the start dates of recent core updates: March 13, 2025; June 30, 2025; December 11, 2025; March 27, 2026; and May 21, 2026. The gaps between those starts run from 55 days to 164 days. If future gaps resemble recent ones, a site that improves just after one update may wait from under two months to more than five before the next, and the core updates guide says Google gives notice of them when they happen, not before.
What makes the timeline longer
The size and age of the problem matter: a site with one weak section recovers faster than one whose content was built for search engines rather than readers. Completeness matters too, because a partial cleanup delays every later step. For manual actions involving links, the work of finding and removing or disavowing them adds time before a request can even be filed.
What a credible answer sounds like
A credible company names the type of problem before it names a timeline. For a manual action, it describes the fix, when it will file, and that Google sets the review time. For an algorithmic drop, it explains the improvements, when it will measure their effect, and that full recovery may wait for a future update whose date no one outside Google knows. A promise of recovery by a fixed date is a promise about Google’s schedule, which no company controls.