Manual action recovery · evidence first
Google Penalty Recovery Services
Address the manual action with a clear plan
A manual action in Google Search Console gives you a specific problem to address. The next step is to understand the notice, find the full pattern behind it and correct the violation before requesting a review.
EduGuestPost’s Google penalty recovery services help you organize that work. We review the action and affected scope, investigate the supporting evidence, then plan the agreed corrections. Your project can include implementation, coordination with your team and preparation of a reconsideration request that documents what changed.
You receive a record of the findings, completed work and remaining dependencies. Google decides whether to revoke the action. Our role is to help you make the necessary changes and explain them accurately, with a practical plan to prevent the problem returning.
Request a manual action review with your website and the exact Search Console notice, including any examples or previous review responses.
Start with the right problem
Confirm whether this is the right service
A confirmed manual action appears in Search Console’s Manual actions report. Read its description and affected patterns before choosing a remedy. An action may apply to a section or the whole website, and its effect depends on the issue.
A traffic decline, a ranking-update date or a third-party risk score does not establish a manual action. If the report shows no current action, the investigation should examine other causes, including technical changes, demand and how Google assesses the pages. That broader work belongs in an organic traffic recovery project.
Security warnings require their own checks in the Security issues report. Where a compromised website also has a manual action, both problems need suitable remediation. A security review and a spam reconsideration request are separate processes.
If you recently acquired the website, tell us about its history. An ownership change does not correct an existing violation. We review the current site, the available acquisition records and what needs to be explained truthfully in the request.
01 · Confirmed noticeManual actionThis service
Review the exact notice, affected patterns, previous submissions and the work needed across the affected scope.
02 · No current actionTraffic or rankings declinedA different investigation
A decline alone does not establish a manual action. Investigate the relevant technical, content and demand evidence before choosing a remedy.
03 · Separate reportSecurity warningSecurity review
A compromised site may need specialist security work as well as any separately confirmed manual-action remediation.
04 · Ownership changedRecently acquired websiteInclude the history
Available acquisition records and earlier notices help explain the current site. Ownership changes do not correct an existing violation.
These routes explain service fit. This page does not inspect your Search Console account or diagnose a website.
A defined project, not a penalty score
What your recovery project includes
The proposal defines coverage, delivery responsibilities and follow-up before work begins.
Deliverable | What it contains | Why it matters |
|---|---|---|
Manual action brief | Notice, affected patterns, history and relevant policy | Establishes the problem the project must resolve |
Remediation plan | Findings, proposed corrections, owners and dependencies | Gives each team a specific action to complete |
Implementation record | Approved changes, dates and supporting evidence | Shows what was actually corrected |
Reconsideration support | Draft explanation, evidence references and submission arrangements | Connects the violation to the completed work |
Decision and prevention review | Google’s response, unresolved work and agreed controls | Guides the next step after the review |
Some projects mainly involve editorial changes. Others need a developer, security specialist or cooperation from external publishers. We identify those dependencies when agreeing the scope, including who implements changes and who submits the request.
Different actions need different corrections
Match the response to the violation
01 · Inbound links
Unnatural links pointing to your website
We investigate the linking pattern identified by the action, using available Search Console exports, third-party link data and campaign records. The records can help distinguish paid placements, exchanges or automated activity from legitimate editorial mentions.
Search Console’s Links report is a sample, not a complete current backlink inventory. It can retain links that have since changed or disappeared and does not identify each link’s qualification attributes. We record the sources and gaps, then inspect relevant links in context.
Low authority scores, unusual domains and repeated anchor phrases can prompt investigation. They do not prove a violation on their own. A useful finding explains the source page, destination, commercial or acquisition context and the reason the link needs action.
For confirmed problematic links, the plan records good-faith removal or qualification efforts and their outcomes. Publishers may respond, decline or remain unreachable. Requests should be specific enough for them to find the actual link, and follow-up should reflect the circumstances.
02 · Outbound links
Unnatural links from your website
This action concerns links you publish to other websites. Reviewing your inbound backlinks alone will not resolve it. We examine the affected sections, templates and commercial arrangements, including older sponsored articles that may still contain unqualified links.
Google recommends rel="sponsored" for paid links; nofollow remains acceptable. A visible sponsorship label does not replace appropriate link qualification. Check the published markup and each occurrence rather than assume an editor setting changed every link.
Our dofollow and nofollow guide provides background for discussing the terms with publishers and writers. Qualification addresses the linking relationship; the page still needs a legitimate purpose and useful content.
03 · Publishing patterns
Content and third party publishing issues
Where the notice concerns thin content, scaled content abuse or other content violations, we review the affected pages and how they were produced. The response might involve substantive improvements, removing abusive material or an appropriate exclusion from search. The decision follows the actual issue and page purpose.
Adding words or replacing phrases is insufficient when the underlying page offers little value. We look for useful explanations, supported facts and a clear reason for the page to exist. Ordinary duplicate URLs or shared wording should not automatically be labeled a penalty.
For site reputation cases, we review the publishing relationship, host contribution and integration of the content against current guidance. Third-party authorship alone does not establish abuse. A cosmetic redesign or an editorial approval label alone does not establish compliance either.
Search markets also matter. Under Google’s current site reputation policy, the manual-action effect applies outside the European Economic Area. Within the EEA, the affected section may instead be assessed independently of the main domain. Reporting should identify the relevant markets rather than assume one worldwide effect.
This distinction concerns the searcher’s location and this specific policy, not the publisher’s address or every manual action. See the policy context.
04 · Behavior & markup
Technical behavior and misleading markup
Cloaking, deceptive redirects and back button hijacking require inspection of actual behavior and the code or services responsible. A developer may need to compare user experiences, remove a problematic script or correct a template. A public HTML check alone cannot reproduce every device, referral or session condition.
For structured data actions, we compare the declarations with the visible page and the relevant feature policy. A syntax validator can pass misleading markup. Google states that a structured data manual action removes rich-result eligibility without affecting the page’s ordinary web-search ranking, so the recovery goal must match that distinction.
User-generated spam needs attention to the entry point as well as the published material. Removing forum or comment spam should be accompanied by suitable moderation and publishing controls. If compromise is involved, security expertise is required.
A specialist decision, not a default cleanup
Use disavow only when it is justified
Disavow is a specialist step for qualifying inbound-link cases. Google advises using it only when there is a considerable volume of artificial or low-quality links and those links have caused, or are likely to cause, a manual action. Most websites do not need it.
Where the evidence warrants a file, we document the proposed URLs or domains and why they are included. Preserve useful organic links. A domain-wide entry has a wider effect than one URL, so its scope needs a deliberate decision.
Before upload, retain the existing file and reconcile it with the proposed version. A new upload replaces the previous list for that property. The tool uses URL-prefix properties rather than Domain properties, and uploading requires property-owner access. The agreed submission arrangements should reflect those requirements.
We keep disavow preparation, upload and reconsideration as separate recorded steps. Uploading a file does not remove links from the web or automatically revoke a manual action. An export of every vendor-flagged link is not a substitute for review.
Discuss your manual action if you have a previous disavow file or a rejected request and need the existing work assessed before further changes.
Coverage before reconsideration
Correct the pattern across the affected scope
Example URLs help explain a problem, but they are not necessarily its full extent. We inspect the relevant page groups, publishing rules and recurring templates, then record what was checked and what remains inaccessible. A limited sample should not be presented as complete coverage.
The action plan identifies the change, owner and verification method. For a publishing-template fix, that might mean updating the rule, checking older articles and verifying the live result. For content work, it includes reviewing substantive accuracy and whether the revision addresses the violation.
Keep a record of the earlier state before making changes. Protect suitable existing redirects and deliberate access controls. Moving the same violating material to a new path or domain is not a reliable remedy, and routing everything to the homepage does not resolve the underlying issue.
Before review, Google needs to be able to verify the relevant corrections. Where the agreed remedy removes or excludes content, check the actual response or indexing directive and explain it. Blocking crawling can prevent Google from seeing a noindex instruction.
See how the evidence connects
An example of an outbound link correction
Consider a fictional education publisher with an unnatural outbound-links action affecting its sponsored guides. Its current editor setting qualifies new paid links, but older article templates still publish some paid links without qualification.
Illustrative workflow · no client-result claim
Finding | Agreed correction | Evidence to retain |
|---|---|---|
Older sponsored guides contain unqualified paid links | Correct the relevant links and publishing rule | Before and after markup with affected URLs |
The new setting does not update every old template | Review the remaining affected templates and occurrences | Coverage record and live verification results |
The process could recreate the problem | Update writer instructions and publication checks | The revised procedure and responsible owner |
The reconsideration request explains the action, completed corrections and checks across the affected section. It distinguishes verified changes from outstanding work. Fixing new articles while leaving the older pattern intact would not address the full issue.
This scenario illustrates a workflow. It is not a client result or a prediction of Google’s decision.
Follow the review record
Open each stage for a short explanation. This visual walkthrough is not an audit result.
Record the notice
Start with the confirmed action and affected scope. Keep earlier requests, responses and the evidence available to the team.
Correct the underlying pattern
Agree owners and dependencies, then address the relevant publishing rule, affected pages or technical behavior—not just a single example.
Verify and document
Record completed corrections and dates, check the live result, and distinguish verified work from unresolved dependencies.
Prepare the review explanation
Connect the action to the completed work. Agree final approval and submission arrangements, then retain the response and next steps.
Explain what changed, accurately
Prepare a reconsideration request supported by the work
A useful request explains the exact issue, describes the corrections and documents their outcome. We help organize that explanation around the actual findings and completed work. Previous submissions and Google’s responses remain part of the history.
Evidence may include affected URL groups, implementation dates, removal attempts, revised markup and relevant supporting documents. Keep the explanation focused. Any evidence linked for Google’s review needs to be accessible without a sign-in barrier and contain only the information required for that review.
Where several manual actions are listed, address all of them before requesting reconsideration. A request should not imply that planned work is complete. We agree who checks the final wording, confirms implementation and submits through the appropriate Search Console access.
After submission, retain the confirmation and monitor the decision. Google advises waiting for the response to an outstanding request before resubmitting. If a request is rejected, examine the feedback, investigate what remains unresolved and document further corrections before preparing another submission.
Focused tools, explicit coverage
Tools that help inspect the evidence
The EduGuestPost tool directory provides focused checks that can support the investigation. Select the tool for the question and retain its coverage alongside the result.
Tool | Useful evidence | Interpretation limit |
|---|---|---|
Qualification attributes and source-page directive evidence | Initial HTML or supplied markup does not prove Google’s treatment | |
A known source and target link observation | It does not discover a complete backlink profile | |
Wording, repetition and destinations in selected evidence | No anchor percentage establishes a penalty | |
Matching passages and differences between two sources | Wording overlap does not prove plagiarism or a policy violation | |
Public responses, crawl rules and indexing directives | Accessibility does not confirm Google indexing or action removal | |
Initial HTML and response observations in a small sample | Up to 20 outcomes cannot certify an entire affected section |
URL-based HTML checks may miss links inserted by JavaScript. Supplied rendered markup can support another comparison, but it does not establish the current live state. Larger investigations need suitable crawl coverage and manual verification.
Make the correction repeatable
Improve the process that created the issue
EduGuestPost’s editorial standards provide a starting point for discussing relevance, originality and factual support. Recovery turns the specific findings into instructions your writers, publishers and developers can apply.
For commercial publishing, record the relationship and appropriate link terms before publication. Our guide to the risks of cheap bulk backlinks explains why acquisition history deserves scrutiny. Price, a publisher’s authority score or an education domain does not establish compliance.
The existing SEO campaign service connects destination-page readiness, content, internal links and publisher planning. Further campaign work should follow the recovery findings and agreed publishing controls. Acquiring more links does not cancel an existing violation.
Practical answers before the project
Google penalty recovery questions
How long does a reconsideration review take
Google says reviews can take days or weeks, and link-related cases may take longer. Investigation and implementation add their own time. We agree project milestones and follow-up arrangements without promising a review deadline or a fixed date for restored traffic.
Will removing the action restore previous rankings
Revocation and subsequent performance are different outcomes. Lost credit from artificial links, other website issues, competing pages and demand changes can affect the result. We record Google’s decision separately from indexing, relevant search clicks and reliable business metrics.
Can you guarantee that Google will approve the request
No. Google makes that decision. The proposed work provides a documented investigation, agreed corrections and an accurate submission. A prior rejection can inform further investigation, but it does not justify claiming that the next request will succeed.
What does penalty recovery cost
The quote depends on the action, affected scope, available records and work required. Developer support, publisher coordination, content changes and review follow-up can affect delivery. The proposal identifies what is included and who is responsible for each part.
Define the work before you commit
Request a manual action recovery plan
Share your website, the exact notice and affected patterns, plus any prior requests or responses. Include available link exports, campaign records, previous disavow files and recent publishing changes. Let us know who can approve content and technical corrections.
Request your Google penalty recovery plan or email [email protected]. We can review the evidence available and define the investigation, implementation and reconsideration support your case needs.
Use a redacted notice and your website URL. Do not send account passwords, recovery codes or private access credentials through this form. Agree a suitable way to share sensitive evidence with the team. Read our privacy policy.
Tell us about the confirmed action
Your enquiry starts a scope discussion. This form does not submit a reconsideration request to Google.