Guide

How to Write a Reconsideration Request That Works

A reconsideration request is your case to Google that a manual action is fixed. It works when the problem is truly cleaned up and the request shows the evidence.

A reconsideration request works when the manual action is truly fixed and the request proves it. Fix the cause across the whole site, keep records of what you did, then explain the problem, the cleanup and the result in plain, factual language. Vague or rushed requests are the ones that come back rejected.

When you can file one

A reconsideration request only applies to a manual action. That is a penalty applied by a human reviewer at Google, and it appears in Search Console under Security and Manual actions. The report shows the type of issue and often the affected pages. If nothing is listed there, there is nothing to reconsider. Our answer on how to know if you have a manual action shows where to look.

Before you write anything: fix the problem

Filing early is the most common mistake. Google asks you to resolve the issue first, across the site, not only on the examples it listed. The sample pages are a clue, not a full list.

Manual actionWhat must be fixed first
Unnatural links to your siteRemove the manipulative links where you can, and disavow the rest.
Thin content with little or no added valueRewrite, merge or remove the weak pages across the whole site.
Spam or hacked contentClean the hack, close the hole it came through, and remove the injected pages.
Pure spam or user generated spamRemove the spam content and tighten how new content is accepted or moderated.
Match the fix to the action listed in Search Console.

For link problems, read our guide on the unnatural links manual action. For content problems, read the guide on the thin content manual action.

Why requests get rejected

Most rejections come down to a handful of causes. Knowing them saves weeks, because each attempt takes time to be reviewed.

Before you submit

Check these first

If any line on this list is a no, the request is not ready.

Reviewers read many requests. A clear, honest, well documented one stands out from a vague one.

Pre submission checklist

  • The cleanup covers the whole site, not just the sample pages
  • Every bad link or weak page has been handled or documented
  • The documentation opens without a login
  • The request names the real cause
  • Nothing new that breaks the same policy has been published

Another common cause is repeat offending. If new spam content or new paid links appear while your request is pending, Google can see that the problem is not gone. Freeze risky activity until the review is finished.

Partial fixes and sample pages

Google often lists only a few example URLs in the manual action. Owners fix those and file. Reviewers then check the rest of the site and find more of the same. Treat every example as a pattern: find all the pages or links that share it, and deal with each one. For link problems, that means pulling the full backlink data from several sources and not relying on a single report. For content problems, it means reviewing every page that matches the pattern, not only the ones Google named.

What to document

Reviewers cannot see your effort unless you show it. Keep a record as you work:

Put the records in a shared document and link to it from the request. Make sure the link can be opened without a login.

How to write the request

1. State the issue

Name the manual action as Search Console lists it, in one sentence. Do not argue that it was unfair.

2. Explain the cause

Say what caused it, honestly. If a previous agency built the links, say that. Owning the cause shows you understand it.

3. Describe the cleanup

Summarise what you did, in order, with numbers you can back up from your records. Keep it short and link to the detail.

4. Say how you will prevent it

One or two lines on what has changed so it does not return, such as a new process for approving content or links.

5. Submit from Search Console

Use the Request review button in the Manual actions report. Then wait. Google tells you the outcome in Search Console and by message.

After you submit

Do not file again while the request is pending. Our answer on how long a reconsideration request takes explains what to expect. If Google lifts the action, rankings do not always bounce straight back. The pages and links that were suppressed may have lost the value they used to carry, and recovery can mean rebuilding.

When to call for help

Get help when you cannot find all of the problem, when a request has already been rejected, or when you inherited the site and do not know its link or content history. Those cases need evidence work before any request is written.

Our Google penalty recovery service handles the cleanup, the documentation and the request. Ask for a free SEO triage and we will tell you honestly whether a request is the right next step.

FAQ

Questions owners ask us

Can I file a reconsideration request without a manual action?

There is nothing to reconsider without one. If a drop is not listed under Manual actions in Search Console, it was not a manual penalty, and a request will not help. Look at algorithmic causes and technical faults instead.

What should I do if my request is rejected?

Read the response. Google usually gives an example of what is still wrong. Fix that issue and look for more of the same, then submit again with fuller documentation. Rejection usually means the cleanup was incomplete.

Should I write a long emotional appeal?

No. A short, factual request works better. State the issue, what you did to fix it, and link to your documentation. Reviewers want evidence that the problem is resolved, not an apology or a story.

Get started

Tell us where it hurts.

Your site, what changed and when. We reply with a first read on the cause.