How long recovery takes, using only the numbers Google publishes

The two distinctions that have to come before any number

How long will this take is the first question every victim asks and the one most often answered with a made-up number. This page collects only the timelines Google itself publishes, scenario by scenario, and states plainly where none is published. On this subject the absence of a figure is itself the finding: a vendor who quotes you a recovery time has told you something about the vendor rather than about your site.

Two distinctions have to be held apart before any figure means anything.

Review time is not recovery time. Google publishes how long some of its reviews take — the human or automated evaluations it performs when you ask it to look at a site again. It publishes nothing about how long rankings take to return afterwards, and it never promises they will. A revoked manual action restores eligibility to rank. It does not restore a position.

Removal time is not re-evaluation time. A warning being lifted, a URL being suppressed, a listing being restored: each is a discrete event with an observable completion. Ranking re-evaluation is continuous. It has no completion event, no notification, and no queue to be in. Waiting for one to conclude is the commonest way a recovery is experienced as taking months when the remediation was finished in week two.

An estimate that mixes the two categories — three weeks to review plus six weeks to recover, say — is not a longer estimate than the published one. It is a published figure with an invented figure added to it, and the sum inherits the accuracy of the worse half.

The published timelines, scenario by scenario

Every figure below is a direct quotation from Google, and nothing in this section is an estimate of mine.

A hacked site cleaned and submitted for review

The Security Issues report help page states that "a review can take from a few days to a few weeks to complete." Google's more specific breakdown, on its Request a review documentation, is by hack type: "Reviews for sites hacked with spam can require up to several weeks to process"; "Reviews for sites infected with malware require a few days to process"; "Phishing reviews take about a day to process." The clock does not start until the site is actually clean, and a failed review resets it. Repeated failed reviews are the single largest driver of long recoveries and they are self-inflicted — see the hacked site injection page for what a complete cleanup involves.

A malware interstitial or browser warning lifted

Google: "If Google finds that your site is clean, warnings from browsers and search results will be removed within 72 hours." One practical caveat that is not a Google timeline: browsers cache Safe Browsing data locally, so an individual visitor can see the warning briefly after it has lifted, and independent security vendors and corporate web filters run their own blocklists on their own schedules. A clean Safe Browsing status does not clear those, as the malware and blacklisting page sets out.

A manual action reviewed

From Google's Manual Actions report documentation: "Most reconsideration reviews can take several days or weeks, although in some cases, such as link-related reconsideration requests, it may take longer than usual to review your request." Note that Google itself singles out link-related requests as slower; that qualification is Google's, not an industry complaint. Google also states that "you will be informed by email when we receive your request, so you'll know it is active," and instructs: "Please don't resubmit your request before you get a decision on any outstanding requests."

Spam links with no manual action

There is nothing to wait for, because there is nothing to undo. The nearest thing to a published timeline is the Penguin 4.0 announcement of 23 September 2016, in which Google wrote that Penguin's data is "refreshed in real time, so changes will be visible much faster, typically taking effect shortly after we recrawl and reindex a page." That is a crawl cycle, not a release schedule. If a disavow file is genuinely warranted, Google publishes one figure for it: "It can take a few weeks for Google to incorporate your list into the index" — incorporation, not effect. The disavow file guide covers the rest.

Recrawl and reindex after any on-site fix

Google's URL Inspection documentation: "Indexing typically takes only a day or so, but can take much longer in some cases," and for newly requested pages, "indexing can take up to a week or two." Also, flatly: "Submitting a request does not guarantee that the page will appear in the Google Index." This is the floor beneath every other timeline here. Nothing you fix counts until it has been recrawled.

Urgent suppression of indexed spam URLs

The Removals tool: a request "usually takes up to a day to process, and is not guaranteed to be accepted," and "a successful request lasts only about six months." Google also notes that "blocking a URL does not prevent Google from crawling your page, only from showing it in Search results." It is a six-month bandage over a problem that still has to be fixed underneath it.

A copyright removal from Google Search

Google publishes one number, in its Transparency Report help documentation: "Our average processing time across all removal requests submitted via our web form for Search is approximately 6 hours." Read it for exactly what it is — an average across an enormous volume of automated filings by rightsholder agencies, including refusals — and not as a promise about a single manually reviewed request from one site owner. The procedure is in the guide to recovering from content scraping.

A fake or attack review reported for removal

Google Business Profile documentation: "review evaluation typically takes several days." A refusal can be appealed once per review, for up to ten reviews at a time, through the Reviews Management Tool — and Google publishes no timeline for the appeal stage at all. No success rate is published either, by Google or in any study with a disclosed method. See fake negative reviews.

Where Google publishes nothing, and says so by saying nothing

This is the half of the subject that vendors fill in. It should stay empty.

• Ranking recovery after any remediation. Not after a manual action is revoked, not after a security flag lifts, not after a disavow list is incorporated. Google publishes no figure and no statement that positions return at all. Every "X weeks to recover" number in circulation is unsourced.
• Business Profile reinstatement. No published timeline for reinstatement after a suspension, for a hijacked listing, or for reversing a false permanently-closed label. The one published clock in this area runs against the victim rather than for them: the three-day window in which a current owner must respond to a third party's ownership request before that request can proceed.
• The Business Redressal Complaint Form. No published processing time, and no published outcome data.
• Review-removal appeals. The first-stage evaluation has a published figure; the appeal does not.
• A host's initial response to a copyright notice. Frequently confused with the statutory restoration window, which is a different clock entirely and is described below.
• Reconsideration approval rates, average attempts, or time to revocation beyond the several days or weeks Google quotes.

Practitioners will tell you, correctly, that a Business Profile reinstatement takes anywhere from days to months. That range is worth knowing and it is not sourced to Google, so it should be labeled as practitioner experience every time it is used, including by me. The distinction between a published figure and an experienced one is exactly the distinction this page exists to hold.

Reading the clock honestly

The commonest reason a recovery takes months is that the wrong clock was started. Before counting days, establish four things.

1. What the date of the event actually was. Search Console Performance, day granularity, clicks and impressions plotted separately. Impressions falling while clicks hold is a different problem from both falling together, and the two have different remedies.
2. Whether a review is actually pending. Google emails on receipt of a reconsideration request — a formal submission asking Google to look at the site again after a fix. If no email arrived, the request may never have been filed. That is more common than it sounds, and people spend weeks waiting on a queue they are not in.
3. Whether the fix has been recrawled. Use the URL Inspection live test rather than your browser. An uncrawled fix is not yet a fix as far as any timeline on this page is concerned.
4. Whether the thing you are waiting for has a completion event at all. A warning lifting does. A ranking returning does not.

What a mid-recovery site is commonly mistaken for is a site still under attack. A cleaned site waiting on a recrawl looks identical, in every third-party tool, to one whose problem is ongoing — the tools are sampling the same stale index. The distinguishing evidence is Search Console's own reports, and nothing else has standing here.

What genuinely shortens a recovery

There is no way to accelerate a Google review queue. Any vendor describing a channel that does is describing something that does not exist, and no recovery of rankings or revenue can be guaranteed by anyone, including me. What actually shortens the elapsed time is unglamorous.

1. Fix completely before requesting a review. Partial fixes fail reviews and a failed review costs the whole cycle again. Google's own wording for manual actions: "Fixing the issue on just some pages will not earn you a partial return to search results."
2. Make the fixed pages crawlable. Not behind a login, not blocked in robots.txt, returning honest status codes. Blocking the affected directories before a review hides the fix as effectively as it hid the problem.
3. Write the request so a human can verify it in two minutes. Dates, counts, URLs and outcomes; the reconsideration guide has the standard Google publishes.
4. File once and wait. Resubmitting while a request is open contradicts Google's stated instruction and accelerates nothing.
5. Do nothing where nothing is wrong. The fastest recovery from a link attack with no manual action is the one where no remediation is attempted, because there is nothing to recover from and every action taken adds a variable to an already unclear diagnosis.

The one statutory clock, and why litigation is not a timeline

Timelines in the legal track are set by statute rather than by Google, and they are slower than everything above. The only statutory clock that appears routinely in this work is the restoration window under 17 U.S.C. 512(g)(2)(C): after a counter notification, material comes back "not less than 10, nor more than 14, business days following receipt of the counter notice" unless the complainant files suit. That window belongs to the host, not to Google, and it should be budgeted for before any takedown notice is sent.

Litigation timelines are measured in months to years. A search visibility problem is almost never solved by them, and treating a lawsuit as a recovery plan means accepting a schedule an order of magnitude longer than the one you are trying to shorten.

The mistakes that add months

• Quoting a recovery time to a client or a board. Give the published review window, then say explicitly that ranking recovery has no published timeline. A number you invented becomes the date you are judged against.
• Restarting the clock by resubmitting, against Google's stated instruction and to no effect.
• Filing a review before the fix is crawlable, which converts a two-week wait into a six-week one.
• Reading rank-tracker noise as evidence that a review failed. Reviews conclude with an email, not with a movement in a tracker.
• Assuming the interstitial lifting means the ranking loss is over. Different clocks. The 72-hour figure applies to the warning and to nothing else.
• Buying expedited or guaranteed recovery. No expedited channel exists, and the outcome cannot be promised by anyone with or without a queue.

Frequently asked questions