The honest answer is that recovery timelines vary widely, and the single biggest factor is whether the penalty is a manual action or an algorithmic suppression. These two situations follow completely different recovery paths, so a credible SEO company will tell you which one you are dealing with before it predicts any timeline.
Manual actions follow a defined process
A manual action is a penalty applied by a human reviewer at Google. It shows up in the Manual Actions report inside Google Search Console, and it can be cleared through a reconsideration request once the underlying problem is genuinely fixed.
This is the faster of the two paths because there is an actual review process with a defined endpoint. After an SEO company corrects the issue, such as removing or disavowing unnatural links or cleaning up thin or spammy content, it submits a reconsideration request describing what was fixed. Google confirms receipt by email, then a reviewer evaluates the case. Review times generally range from a few days to several weeks. Link-related cases often take longer than other types because the reviewer has to assess a larger body of work.
Recovery here depends on the quality of the cleanup, not on guessing. If the request is rejected, Google explains what is still wrong, and the site owner should wait and complete a more thorough fix before resubmitting rather than sending the same request again. So with a manual action, an SEO company can reasonably say recovery is possible within weeks once the fix is real and complete. What it cannot do is promise a specific date, because the review queue is controlled by Google.
Algorithmic suppression is slower and less predictable
The more common situation today is not a manual action at all. When a site loses rankings after a broad core update or another algorithm change, that is an algorithmic effect, not a penalty in the formal sense. There is no report to check and no reconsideration request to file. Google has been clear that reconsideration requests apply only to manual actions.
Because there is no review process, recovery cannot be triggered on demand. It works in two stages. First, the SEO company has to make substantive improvements to the content, the site’s expertise signals, the technical foundation, or whatever the analysis points to. Second, Google has to recrawl those pages and reassess the site.
The reassessment is the part nobody can schedule. Google recrawls and reindexes pages continuously, so some improvement can appear gradually as updated pages are re-evaluated. But meaningful recovery from a core update is often recognized only when the next broad core update runs. Those updates have historically arrived every few months, which means a site that was affected may wait until the next cycle for its improvements to be fully credited. In practice, a realistic window for algorithmic recovery is several months, and deeper or longer-standing quality problems can take longer still.
Why the variation is so wide
Several factors push the timeline in either direction. The type of penalty matters most, as described above. The severity of the original violation matters, since a site with a single thin section recovers faster than one rebuilt from a weak foundation. The completeness of the fix matters, because partial cleanups simply delay recovery. And for algorithmic cases, Google’s own update and recrawl schedule sets an outer limit that no SEO company controls.
What to expect from a credible SEO company
A trustworthy SEO company will diagnose the penalty type first, then set expectations accordingly. For a manual action, it should describe the reconsideration process and a likely range of weeks. For an algorithmic drop, it should explain that recovery depends on real improvements being recrawled and reassessed, often across one or more core update cycles, and that the timeline is measured in months rather than days.
Be cautious of any company that guarantees a fast or fixed recovery date. The fix is within an agency’s control. The timing of Google’s review or reassessment is not.