Guide 03 / 16 By Lucas Vicente and Marco Kohns
Published
Updated
On this page

How to prepare a Google reconsideration request after a manual action

When we prepare a Google reconsideration request, we treat it as a concise record of what was wrong, what changed, and why the violation should no longer apply. The request should reflect completed work, not intentions.

Context
State the manual action plainly

Name the Search Console label, affected scope, and the root causes found during review.

Remediation
Document completed fixes

Summarize what was removed, rewritten, disavowed, consolidated, blocked, or governed.

Controls
Show what prevents recurrence

Explain workflow, moderation, publishing, or technical controls that changed.

Written by Lucas Vicente and Marco Kohns.

We wrote this guide from the evidence standard we use in penalty recovery work: explain the exact issue, document the cleanup, and make the operational change clear without overclaiming what Google will decide.

01

Submit when remediation is complete enough to defend

Submitting too early is one of the easiest ways to lose time. We want the request to follow real remediation, not promise future cleanup. Google reviewers need to see that the cited issue was addressed, whether the work was link cleanup or content remediation .

The review itself takes time. Google's documentation says most reconsideration reviews take several days or weeks, and link-related cases can take longer, which is one more reason not to spend an attempt on incomplete remediation.

The strongest requests we have worked on are specific and modest. They do not overclaim, blame Google, or bury the reviewer in irrelevant background.

02

Manual action reconsideration request: how to write reconsideration request evidence

First, we acknowledge the policy issue reported in Search Console and explain how it happened. Second, we describe the completed cleanup with enough detail that the reviewer can understand the work. Third, we explain the controls that reduce the chance of the same pattern returning.

What the manual action notice said
What URL, link, template, content, or governance patterns were found
What changed, with examples where useful
What process prevents recurrence
03

What weakens a reconsideration request

Generic apologies, keyword-stuffed narratives, claims of good intent, and promises to improve later do not substitute for evidence. We write the request so remediation is easy to audit.

Submitting before the underlying issue is fixed
Describing work without showing scope
Sending a template that does not match the actual violation
Arguing that previous performance proves the site should be restored

Sources and policy references

Google’s documentation supports the policy statements. The diagnostic worksheets and suggested controls are our practical guidance; they are not Google review requirements.

Questions this guide should settle

No. We use a structure, but the content must match the manual action, affected scope, and completed remediation.
Google's documentation says most reconsideration reviews take several days or weeks, though link-related cases can take longer. Google makes the review decision and turnaround is not guaranteed.
Often, yes. In our reviews, a denial usually points to remediation, evidence, or explanation that did not satisfy the review standard.

Need specialist review after reading?

If Search Console shows a manual action, bring the notice, affected scope, and examples into a confidential assessment with us.

Before you move on

Build a concise request around the named action, completed correction, coverage, and recurrence controls; retain the evidence and track the actual review decision.

Return to the final checks