Know when the form exists
A reconsideration request asks Google to review a site after problems identified in a manual action or security issue have been fixed. There is no equivalent form for an ordinary core-update loss, a clean Manual Actions report, or an SEO tool's “toxic link” warning.
If you do not have a notice, a better-written request cannot create a review channel. Investigate the loss instead. If you do have a notice, return to the remediation process and let the named issue define the work.
Build the request from the work log
Google says a good request explains the exact quality issue, describes the steps taken to fix it, and documents the outcome. Those are evidence categories, not headings that magically make a request complete.
- Issue: quote or accurately identify the Search Console category and affected pattern.
- Work: state what was removed, rebuilt, disclosed, or stopped, including changes to the process that produced the violation.
- Verification: provide representative URLs, counts, removal records, and tests that show the problem is no longer present.
Use dates and concrete examples. “We improved quality across the site” asks the reviewer to believe an adjective. “We removed the 412 generated city pages under this template, retired the generator, and returned 404 for the deleted URLs” describes something reviewable.
Do not hide the repaired evidence
Affected pages must be reachable by Google during review. Do not use robots.txt, authentication, a paywall, or noindex as a cosmetic way to make a violation invisible and then claim it was repaired. If content was intentionally removed, make the removal technically final; if it was repaired, let Google crawl the repaired version.
For unnatural inbound links, document good-faith removal work and use the disavow tool only for the remaining links that meet Google's stated threshold.
Set the right expectation after submission
Search Console confirms receipt and later reports the decision. Google does not provide a deadline worth turning into a customer promise, and it advises against resubmitting while a request is pending.
A successful review revokes the manual action. It does not restore a historical result set. After revocation, technical accessibility, relevance, links, competition, and the quality of the current site still determine what happens next.