Restore / Research / RR Response Time Response Window Reference Reconsideration request response time. The typical window and the no-response decision tree.
Two to six weeks is the typical window for Google's response on a reconsideration request. Specific timing depends on case complexity and review-queue depth. The decision tree for next steps if no response lands runs through the Search Console verification check first.
The typical response window
Most reconsideration requests resolve in a two-to-six-week window. The variance reads against three factors. Case complexity: a linking-pattern Manual Action with documented removal outreach and a tight disavow file resolves faster than a sitewide content-quality rebuild case where the manual reviewer audits the full corpus. Review queue depth: the queue varies with the volume of submissions; high-queue windows extend response times. Request quality: a reconsideration authored to the three-element shape with explicit citation of what was remediated reduces review time because the reviewer has less inference work.
Outside the two-to-six-week window: cases under two weeks happen on simple violations with tight remediation and clear documentation. Cases beyond six weeks happen on complex sitewide rebuilds or on queue-depth peaks. The operator-side expectation should be the median rather than the floor or the ceiling.
What "response" actually looks like
Google sends two signals: an email notification to the property's Search Console verified owners and a notice inside Search Console under the Messages section. The Manual Actions report status updates alongside. The email arrives first; the in-app notice follows by minutes to hours.
The response carries one of three outcomes. Acceptance: the Manual Action is lifted, the report shows no active issues for the property. Rejection: the specific reason is named (disavow file missing entries, removal-outreach documentation not provided, remediation evidence not addressing the cited URLs, or other category-specific gaps). Request for more information: less common but possible; Google asks for additional evidence or specific remediation surfaces to be addressed before the review can complete.
The diagnostic check on whether the response actually landed: the email reaches the verified owner, the Messages tab in Search Console shows the new message, and the Manual Actions report status reflects the outcome. All three should agree.
The no-response decision tree
If the six-week window passes with no notification, the decision tree runs three checks in order.
First: verify the Search Console property is owner-verified at the correct level. A reconsideration filed against a property verified at the subdomain level will not notify owners of the root-domain property and vice versa. Confirm the notification address.
Second: check the Messages tab and the Manual Actions report directly. Email notifications can be filtered or missed; the Search Console in-app signal is the source of truth. If the Manual Actions report shows the violation still active and no message has landed, the request is still in queue.
Third: hold position. Manual review can take longer than the typical window for complex cases. Resubmitting the same request before the original has been reviewed is operationally counterproductive and signals as a process violation to the review team. The operational discipline is to wait for the response to the original submission, then iterate.
The Restore engagement that runs the authoring and the post-submission monitoring is reconsideration authoring. Adjacent reference: security issues vs manual actions for the surface distinction; the Disavow tool for the inbound-link workflow that pairs with unnatural-links reconsiderations; lifting a manual action for the broader engagement entry. The diagnostic in front runs at the program.
What operators ask in the post-submission window.
- 01.
What is the typical Google response window?
Two to six weeks for most cases. Specific timing depends on the case complexity (a linking-pattern case with documented outreach and a tight disavow file resolves faster than a sitewide quality rebuild case) and the manual-review queue depth at the time. Some cases land in under two weeks; some run beyond six.
- 02.
What does Google actually send?
An email notification to the property's Search Console verified owners, plus a notice inside Search Console under Messages and the Manual Actions report status. The two surfaces should agree. The email arrives first by minutes to hours; the in-app notice follows.
- 03.
What if no response lands within six weeks?
Check the Search Console Messages tab and the Manual Actions report directly. Confirm the property is verified at the right level (root domain versus subdomain affects which notifications land where). If no message and no status change, the request is still queued; manual review can take longer for complex cases. Resubmitting before the original request lands is operationally counterproductive and signals as a process violation.
- 04.
If the request is rejected, can I resubmit?
Yes, after addressing the specific rejection reason. Google's rejection notification names what was insufficient (disavow file missing entries, removal-outreach documentation not provided, remediation evidence not addressing the cited URLs). The resubmission addresses the named gap. The engagement at reconsideration authoring covers the three-element shape that minimizes rejection probability.
If your reconsideration request is past the typical window and you need the decision tree run plus the next-step routing, book the diagnostic.
We verify the property verification level, audit the Search Console surfaces for the response signals, and route the next step (wait, resubmit-with-correction, escalate via Twitter forum signal) per the case state.