Google manual actions: prepare a reconsideration request
Read the conclusion first
Use the native Manual Actions notice to define the actual issue and scope. Repair the reported violations across the affected pages, verify them, then submit an honest reconsideration record. A traffic decline without a notice does not establish a manual action, and acceptance of a review request does not establish removal.
Applicable conditions
Applies to authorized managers who have received a clear manual action notification.
Before you open the report
The actual Manual Actions report, the named violation and scope, and the affected URLs or templates.
Use one concrete URL or report first. Keep account credentials and private visitor data out of shared notes.
Steps and verification
Preserve the notice and translate its scope into work
Record the exact issue type, affected pattern, notification date and current state in a protected file. Read the linked official instructions for that issue. Build an inventory of affected templates and important URLs rather than treating example URLs as the whole scope.
If there are several actions, give each its own work and evidence record. Do not substitute a general content rewrite for a specific link, markup or spam violation. If no notice exists, investigate traffic changes through the appropriate workflow instead of inventing an appeal.
Fix and verify the real violation
For each issue, record the original condition, actual corrective action and a reproducible check. Remove or correct the prohibited behavior and its generating source so new pages do not reproduce it. Verify representative pages across the affected scope.
Keep remediation evidence truthful: no fabricated outreach, deletion attempts, reviews or before/after numbers. Check that Google can access pages relevant to the review. A fix to one visible example is insufficient when the same fault remains in the template or elsewhere.
Submit a concise evidence-based reconsideration
When the reported problems are fixed, explain the issue, actions taken, verified outcomes and recurrence controls in the native request. Include useful evidence that supports those facts without exposing credentials or private customer information.
Record submission and the subsequent decision separately. If review is unsuccessful, use the response to identify unresolved work and collect fresh evidence before another request. Do not promise restoration timing or rankings; even a removed action does not guarantee a return to previous traffic.
Common mistake: Repeatedly request review without fixing
This won't provide new valid evidence and can't replace real remediation.
How to decide when you encounter different situations
Match your actual observation to a row before changing the page. If it does not match, collect the missing evidence first.
| What you see | Next step | How to confirm |
|---|---|---|
| No clear notification | Don't determine a manual action | Run traffic decline diagnosis |
| Notification involves some directories | Review according to the notification scope | Save real fix evidence |
| Reconsideration submission accepted | Wait for result notification | Acceptance is not removal |
A traffic decline is not a manual-action notice
Teaching scenario. Names, URLs and numbers illustrate the method; they are not customer or measured site results.
- What you observe
- Example: organic clicks decline, but the Manual Actions report has no issue. A team drafts a reconsideration request anyway.
- What it establishes
- A graph does not establish a manual action. Without a notice, follow the traffic-drop investigation instead of inventing a penalty.
- What to do next
- For a real notice, preserve its precise scope, fix the cited practice throughout that scope and document what changed. Prepare a truthful reconsideration explanation rather than a generic appeal.
What counts as a checked result
Keep representative repaired URLs and source evidence. Submission acceptance, review decision and later search recovery are separate milestones.
If a required check fails, keep the error and return to the matching decision branch. A blank record means unverified, not passed.
Leave with a checked result, not another vague instruction
- Your deliverable
- A notice-scoped remediation record with real evidence and a separate reconsideration decision.
- Stop and resolve this first
- Do not submit a generic appeal without fixing the notice’s actual issue and recurrence path.
Record missing evidence in the worksheet below. An unresolved test is useful information; a blank field is not a pass.
Checklist for this page
Fill in your own check results, then decide the next step. Blank means not yet verified, not normal. Content is saved only in the current local session and is not submitted to the server or AI.
Frequently asked questions
Can AI automatically write an appeal guaranteeing removal?
Removal cannot be guaranteed; an appeal must reflect real remediation facts.
Can I send a reconsideration request for any ranking loss?
Treat reconsideration as the workflow for an actual manual-action notice. Other losses need evidence-based diagnosis.
Official materials and usage boundaries
This page provides operational judgment and checking methods, and does not show customer success cases. Calculation examples and request samples are teaching materials, not actual website metrics. Google's reports, conditions, and interfaces may change; please refer to the current official documentation.
Read the corresponding Google official documentationContinue with the relevant tool
Use saved AISEO Site analysis to retain search context around the repair. Submit the reconsideration request and evidence in Google's own manual-action workflow.
See how it works →