The Manual Actions report in Search Console shows whether a human reviewer has flagged pages on your site for breaking spam rules. If an action is listed, do this first: open the report, write down the exact action type and scope, and change nothing until you know what was flagged and where.
What is the Manual Actions report?
The Manual Actions report is one page inside Search Console. It answers one narrow question: has a human reviewer placed a manual action on this property? A manual action means a person, not a machine, judged that pages on the site break the spam rules. The report shows the action type, a short description, the scope, and a link to help for that action. It also keeps a history, so you can see past actions and past review requests.
The report does not do more than that. It does not list every page on your site. It does not prove who made a change. It does not grade your content or your links in general. It does not promise anything about later crawling, indexing, or ranking. Treat it as a single piece of evidence with a stated scope, and it stays useful. Treat it as a full site verdict, and it will mislead you.
Start with the report itself, not with a theory about traffic. A drop in clicks can have many causes. A manual action is only one of them. Open the report, read what it lists, and let that decide the next step. If the report lists nothing, the cause of a traffic change sits somewhere else.
How do you read a green check?
A green check means the report lists no manual action on this property right now. Write that down with the property name, the date, and the name of the person who checked it. A simple line works: “Manual Actions report checked on the verified property on this date. No action listed.”
Do not stretch that line into more than it says. A green check is not proof that the site has no other problem. It says nothing about security, crawling, indexing, or the quality of any page. It is evidence for one question only: does this report list a manual action today?
If another report raises a question, open that report and judge it on its own. A green check in Manual Actions does not cancel a warning in Security Issues or a problem in Page Indexing. Keep each report in its own lane, and you avoid fixing things that are not broken.

An action is listed. What do you do first?
Write down the exact details before you touch anything. Copy the action type word for word. Copy the short description. Copy the scope language. Note the date shown and save the link to the help page for that action. These details are the core of your record. If you edit first and record later, you will not know what the original report said.
Next, read the help page linked from the report. The Manual actions report help page explains how the report works and what each action type means. The help page for your action type is the correction spec. Read it to learn what condition was found and what work is needed to stop it.
Do not turn the action name into vague shorthand. “Bad SEO” is not an action type. A structured data issue is not a link issue. A user generated spam issue is not cloaking. Each type points to different facts and different work. The action name, the scope, and the linked policy are the basis for the investigation. A generic checklist is not.
Set up a simple register before the work starts. One row per listed action. Each row holds the action type, the scope, the linked help, the owner, the changes made, and the date each change was checked. A small register keeps the response honest. It also stops a later reviewer from guessing why a page was changed.
What does the reported scope actually cover?
The report may name a part of the site, such as a directory, or it may say that all pages are affected. Keep that language exact. A path pattern is a boundary, not a full list. Not every page that matches the pattern is necessarily affected.
Map the pattern to real URLs. Open representative pages and check each one against the action. Keep four columns in your notes: the report pattern, example URLs you confirmed, related URLs still under review, and changes made. This keeps the work in proportion to the report.
The common mistake here is scale. A team reads a pattern, assumes every matching page has the same problem, and deletes or redirects a whole section. That is a destructive guess. A pattern tells you where to look. It does not tell you that every page in that path is broken. Check the pages, then act on what you found.

Is this a manual action or a different report?
A manual action can sit next to another finding, but one is not proof of the other. A Security Issues warning has its own report and may need a security response. A Page Indexing category is a URL level fact. A Crawl Stats trend sums up crawler activity. A temporary hide in the Removals tool is a different control. Do not fold them into one diagnosis.
When the real question is whether a single URL is indexed, canonical, or live, use the report built for that question. Our Search Console indexing triage guide walks through URL level indexing checks. Keep the manual action work focused on the manual action. A separate question gets a separate task with its own evidence.
This separation matters most under pressure. A team that treats every report as one big problem will change things that were never flagged. A team that keeps each report separate can fix the flagged issue and leave the rest alone. The Removals tool is a good test of this habit. A Search Console Removals tool request hides a URL for a time. It is not a reconsideration request, and it does not answer a manual action.
How do you fix the cause, not just the examples?
The report may show example URLs. Fixing only those examples is not enough. The work has to cover the whole reported scope. If the action covers a directory, the fix has to cover that directory. If it covers the whole site, the fix has to cover the whole site.
Start by naming the cause. Ask what put the flagged material on the page in the first place. Was it a template? A plugin? A bulk import? A form that takes user input with no review? A third party publishing on your site? The cause decides the fix. Removing pages without fixing the cause leaves the door open for the same problem to come back.
Then fix the cause across the scope. Change the template, tighten the form, add a review step, or stop the import. Then fix the affected pages. Then check representative URLs again and record what you saw. The spam policies for Google Web Search describe the conditions each action type covers, so the fix can match the condition, not a guess about it.
Before you ask for a review, check that the affected pages can be reached. Pages behind a login, a paywall, a robots block, or a noindex tag cannot be checked by a reviewer. Use URL Inspection to confirm what a reviewer would see. This does not mean you must expose private content. It means you must know which pages are public, which are private on purpose, and what evidence supports that choice. A page that should stay private keeps its access rule. A page that should be public must load and return the expected response.

What if the action is about links?
A link action points to links made to move a site up the results, not to links that serve readers. The fix is to remove the cause and clean up the links in scope. It is not to build new links, buy links, hide paid deals, or run a fresh link campaign while the action is open. New links do not cancel old ones.
Work from records, not memory. List the links under review, where they sit, who placed them, and what changed. If a link was paid for and not marked as such, fix the marking or remove the link. If a set of links came from one campaign, deal with the whole set, not one or two samples. Keep the record factual. A reviewer needs to see what was checked and what changed, not a claim that the site is now clean.
Do not use the review request to argue about links that were never flagged. The request covers the listed action and its scope. Extra material dilutes it. If a separate link question exists, handle it as its own task with its own evidence.
What if the action is about content or structured data?
Some actions point to content: thin pages, copied text, doorway pages, or pages that add little for readers. The fix is to look at the pages named in the report and judge each one on its own. Improve a page that can be made useful. Combine pages that say the same thing. Remove a page that has no real purpose. Do not answer a content action by publishing more volume, repeating phrases, spinning old text, or building near duplicate location pages. More of the same is not a fix.
Structured data actions need a different check. Compare the markup with what a reader can see on the page. Markup must describe visible, true content. It cannot describe hidden text, unrelated offers, or facts the page does not show. Changing a few fields while the mismatch stays in place does not fix it. Our structured data governance guide covers how to keep markup truthful across a small business site, while the action report and its linked help set the exact boundary for this fix. Keep screenshots, page URLs, markup versions, and validation notes in your evidence record.
User generated spam is a third pattern. It means spammy material came in through a channel meant for user content, such as comments, forums, profiles, or posts. The fix starts by listing the entry points: every form, comment box, and profile page where a visitor can publish. Then check what came through, remove the spam, and add a control that stops the next wave. Removing one visible comment while the form stays open is not a fix. Record which surfaces you checked, what you removed, what control you added, and when you rechecked each one. Do not publish sensitive examples or name real users in the record.
Cloaking needs careful comparison work. Cloaking means users and search engines see different content on purpose, to mislead. To check it, compare what a reviewer fetches with what a person sees on the same URL, at the same time, in the same setup. Note the URL, the time, both outputs, and the system that served each one. A normal responsive layout is not cloaking. A paywall that shows the same article to everyone is not cloaking. The question is whether the content itself differs in a way meant to mislead. Do not start a broad redirect project or a theme rewrite before you know the scope. Record the facts first.
Site reputation abuse is a narrower case. It covers third party pages published on a host site to borrow the host’s standing in search. Third party content on its own is not a violation. The question is the relationship, the purpose, and the way the pages were published. The site reputation abuse policy update sets out that context. Where an action names this case, check the reported pages, who owns them, why they were published, and what the linked policy guidance covers. Do not try to fix it by moving the same pages to another path on the same domain, or by adding redirects with no honest purpose. The fix is a clear page governance decision, followed by a factual review request when the work is done.
How do you write a reconsideration request?
A reconsideration request asks for a review of the site after the problems in a manual action or a Security Issues notice have been fixed. The reconsideration requests help page explains the process. A good request has three parts: the exact issue, the steps taken to fix it, and the outcome of those steps.
Use plain language and facts you can check. Name the action type and the reported scope. State what changed, where it changed, and how you checked representative pages or systems. Say what is still outside the documented scope. If a fact is unknown, say so, and finish the investigation before you submit.
Keep the evidence close to the issue. Useful material includes affected URLs, before and after details, dates, owners, and short notes on each correction. Leave out invented endorsements, edited screenshots that hide key facts, and unrelated exports added to look thorough. Volume is not clarity. A short, accurate record beats a long one padded with material no one asked for.
Watch the line between action and prediction. “We removed these pages and confirmed the current public response” is a fact. “This will restore our standing” is a guess about the future. The request is strongest as a map of work already done, not as a promise or a plea.

When should you send the request?
Send it only when every listed action is fixed across its full scope. That is the gate. Before you press Request Review, run through this list:
Is the verified property the right one? Is the action type, description, scope, date, and linked help recorded? Does every listed action have an evidence row? Is the documented issue fixed across the reported scope, not just on the sample pages? Were representative URLs checked and the results kept? Can the relevant pages be reached for review where that applies? Does the request text explain the issue, the steps, and the observed result?
If any answer is no, keep the record open and finish the work. A request sent too early wastes the review and weakens the next one. If the report raises a separate security, indexing, removal, canonical, or server question, give that its own bounded task. Keep the manual action request narrow so the explanation stays easy to audit.
A compact register makes the whole job easier to review. One row per action, with the property, action type, displayed scope, report date, linked help, representative URLs or systems reviewed, correction owner, changes completed, access checks, request date, submitted text location, confirmation, later report state, and facts still open. Keep sensitive technical detail or personal data in the right restricted system, not in a shared doc.
The register does not need to be fancy. Its job is traceability: what was reported, what the team confirmed, what changed, and what is still unknown. That traceability stops vague claims about recovery. It also gives a clean handoff if a developer, a content owner, a security specialist, or an outside reviewer needs to look at one narrow part of the work.
Watch for the common errors that weaken this work. Treating normal traffic movement as proof of an action. Editing pages before recording the report. Reading a path pattern as every affected URL. Fixing only sample pages. Using a general SEO checklist instead of the linked action help. Submitting before all listed actions are covered. Resubmitting while a request is still open. Each of these is easy to avoid once the register exists and the gate is clear.
What happens after you send it?
Most reviews take several days or weeks. Link related requests can take longer. You will get a confirmation that the request is in progress. Do not send another request while one is still open. Wait for a final decision on the request you sent.
While you wait, save the submission date, the confirmation, the request text, where the evidence lives, and who is responsible. Continue ordinary site work that is justified on its own, but keep it out of the correction record. Do not use the waiting period as a reason for site wide changes. Do not resubmit, and do not treat the wait as a deadline to fill with new edits.
When a decision arrives or the report state changes, record the date and the exact status shown. If the action is gone, keep that observed state without stretching it into a claim about every other measure of the site. If the action stays, reopen the exact action description, the scope, the register, and the linked policy help before you decide what to do next. Do not assume the work was useless because the report still lists the action, and do not assume every concern is settled because one entry changed. The next step depends on the documented state, the response you received, and fresh evidence from the pages or systems involved.

Questions, answered
What is a manual action?
A manual action is a finding by a human reviewer that pages on a site break the spam rules. It is listed in the Manual Actions report in Search Console, with an action type, a short description, and a scope. It is not the same as an automated ranking change or a crawl problem.
Does a green check mean my site is clean?
No. A green check means the Manual Actions report lists no action on that property right now. It says nothing about security, crawling, indexing, or page quality. Other reports answer those questions.
Can I ask for a review after fixing only the example pages?
No. The fix has to cover the full reported scope of every listed action. Fixing only the examples shown in the report leaves the rest of the problem in place, and the request will not reflect the work that is still open.
How long does a reconsideration review take?
Most reviews take several days or weeks, and link related requests can take longer. You get a confirmation when the request is in progress. Do not send a second request while the first one is still open.
Will fixing a manual action bring my traffic back?
No one can promise that. Fixing the action removes the flagged condition. What happens to crawling, indexing, ranking, or traffic after that is decided by search systems, not by the fix itself. The honest goal is a clean, truthful record of the work done.
If you are not sure whether a manual action is open on your site, or what the report is telling you, start with a free audit. It includes a 120-point crawl, a competitor gap map, and a 90-day roadmap, delivered within 48 hours. Free, with no obligation. Start with a free audit.
Get a free SEO audit of your website
A 120 point crawl, a competitor gap map and a 90 day roadmap, ready in 48 hours. Free, with no obligation.
