What Is a Google Manual Action?
The single most useful fact about manual actions is that you are told. A site with one is notified, in a specific place, with a stated reason. That means you can resolve this question in a few minutes rather than speculating about it for weeks. The likeliest outcome is that it does not apply to you.
Somebody Looked At Your Site
A manual action is applied after a person has reviewed the site. Google's Search Console documentation puts it directly: an action is issued when a human reviewer at Google has determined that pages on the site are not compliant with Google's spam policies.
Why that word matters so much. Manual means manual.
A person looked, formed a judgement and applied something. That is a completely different event from an automated system assessing a site. Almost every confusion in this subject comes from those two being described with the same word.
What follows from a person being involved. There is a record.
A judgement made by somebody has a stated reason, a defined scope and a route to respond. None of those exist when a system simply evaluates a site differently, which is the subject of what is an algorithmic penalty.
Why this page comes first in the group. It defines the others.
The three pages that follow all depend on this distinction. Whether you have a manual action decides what kind of problem you have, what work is required and whether there is anybody to ask.
The practical point. This is the only checkable one.
Everything else in this area is inference. This is the single category where certainty is available. It takes a minute to establish.
And You Are Told
You cannot have a manual action without knowing. Where a site is affected, Google's documentation states that the owner is notified in the manual actions report and in the Search Console message centre.
Two places rather than one. Worth knowing.
The report is where the current position is shown. The message centre is where the notification arrives. Businesses frequently have one of these monitored and not the other. Messages sent to an address nobody reads are the usual reason somebody finds out late.
What the notification contains. A reason, not a hint.
The type of issue, a description of it and which pages are affected. This is not a vague signal that something is wrong. It is a specific statement of what was found.
What that means for the anxious reader. The question is answerable now.
Rather than theorising about a drop, you can establish in minutes whether this category applies at all, which is set out step by step in how to check for a Google penalty.
The prerequisite. Access.
None of this is visible without access to the site's Search Console property. If nobody at your business has it, that is the first thing to sort out and it is worth doing regardless of whether anything is wrong.
Which Means Most Sites Do Not Have One
Because these are announced, plus most businesses have never received such a notification, most sites do not have a manual action. That sounds obvious written down. It is routinely ignored in practice.
What people say instead. Penalised.
A business whose rankings fell will describe itself as penalised. The word arrives before anybody has checked. From that point the conversation is about what was done wrong rather than about what actually changed.
Why the misdiagnosis is expensive. It sends the work the wrong way.
Believing you have been penalised means looking for something to remove. If nothing was ever detected, there is nothing to remove. A business can spend months undoing work that was never the problem.
Why it persists. Penalty is a satisfying explanation.
It gives a fall a cause, a villain and a fix. The accurate explanation is usually that assessment changed or somebody else improved, which is harder to act on and much less satisfying to hear.
What to do with this. Rule it out first.
Checking takes a minute and eliminates the only category that can be established with certainty. Doing it first rather than last is the single most useful habit in this whole subject.
What They Are Applied For
Google's documentation states that most manual actions address attempts to manipulate the search index. That is the organising idea. It explains why the categories are not a separate list of offences.
They map onto the spam policies. Rather than standing apart.
An action is issued where a reviewer finds pages not complying with the published spam policies, so the categories are the policy areas. What those cover, with attribution, is on the Google spam policy page.
The broad areas in practice. Described rather than listed.
Issues with links pointing at a site or out from it. Content produced with little value or at scale. Showing something other than what visitors see. Structured data that misrepresents the page. Sites that have been compromised. And spam contributed by users where a site allows contributions.
Why we describe rather than enumerate. The list changes.
Published categories are revised as practices evolve, so a page that hard-coded them would quietly go out of date. The report itself names the issue in your case, which is more reliable than any article.
The one that surprises people. Contributions from users.
A site allowing comments, forum posts or profiles can be affected by what other people put there. That is not a manipulation the owner chose. It still has to be dealt with.
Site Wide Or Partial
An action may apply to a whole site or to part of one. The report tells you which. That distinction decides how much work recovery involves and how much of the business is affected in the meantime.
Site wide. Described as affecting all pages.
The most serious version, since nothing on the site is outside it. Usually issued where what was found is characteristic of the site as a whole rather than of one corner of it.
Partial. Described against a pattern.
The report may show a pattern such as everything under one directory, which tells you where the reviewer was looking. This is frequently a section built by somebody else, at a different time, for a different purpose.
The nuance most writing omits. A pattern is not a verdict on every page in it.
Google's documentation notes that not all pages matching a stated pattern are necessarily affected. That matters, because a business seeing a directory named will otherwise assume every page in it is condemned and start deleting.
What to do with the scope. Let it direct the investigation.
A pattern is a strong hint about where the problem lives. Establish what is actually in that section before deciding what happens to it.
What It Actually Does
Google's documentation states that most issues reported there result in pages or sites being ranked lower or omitted from search results. The effect varies with the action, so no figure is given here and anybody quoting one is inventing it.
Two different outcomes. Lower, else absent.
Ranked lower means the pages still appear and appear worse. Omitted means they do not appear. Those feel very different to a business and they sit under the same heading, which is why the report's own description matters more than any general account.
The part that explains a great deal. Nothing is visible to anybody else.
The documentation notes that this happens without any visual indication to the user. Nothing appears beside a listing, no visitor sees a mark and no competitor can tell. You cannot detect this by looking at a results page.
Why that matters practically. It removes a whole approach.
Businesses try to diagnose this by searching for themselves and studying what they see. There is nothing there to find. The report is the only place the information exists.
What it does not do. Announce itself to your customers.
Nobody who visits your site knows. Whatever else is happening, this is not a public embarrassment. That is worth knowing while working out what to do.
It Does Not Expire By Itself
Waiting does not resolve a manual action. The issue has to be addressed and a review requested, which is the fundamental difference between this and every other explanation for a fall.
Why people assume otherwise. Everything else does pass.
Assessment changes get reassessed. Seasonal falls end. Competitors move around. Almost everything else in search resolves itself given time, so waiting is a reasonable instinct that happens to be wrong here.
What has to happen instead. Two things, in order.
The cause has to be genuinely dealt with, then a review has to be requested through the report. Neither works without the other. Requesting a review without fixing anything wastes the attempt. Fixing without requesting leaves the action in place indefinitely.
Why this is good news. There is somebody to ask.
A defined problem, a stated reason and a process for saying it has been dealt with is a considerably better position than a decline with no cause and nobody to appeal to.
What we will not tell you here. How long it takes.
Nobody controls that and no period should be quoted as fact. What the process involves is set out in how to check for a Google penalty and the recovery guide it points to.
Inherited Actions
A site bought, taken over or rebuilt may carry a manual action applied long before you arrived. This is more common than people expect and it is nobody's fault who is currently involved.
How it happens. Ordinary business events.
A business is acquired. An agency relationship ends badly and nobody hands over the accounts. A site is rebuilt on a new platform by people who never saw the old reporting. In each case the action stays with the site.
Why it goes unnoticed. Nobody was looking.
The notification went to somebody who has left, at an address that no longer exists, in a property nobody has access to. The information was published and simply never reached anybody.
The useful thing the report holds. History.
Google's manual actions report shows a site's manual action history rather than only its current position. For anybody taking over a site, that is a direct answer to what has happened here before. It is worth looking at during due diligence rather than after a problem.
What to do about one. The same as any other.
It still has to be addressed, however unfair that feels. The one advantage is that you have no attachment to whatever caused it, which usually makes removing it considerably easier. The full series is on the dangerous SEO practices guide.
Check first.
Theorise
afterwards.
A review that establishes what changed and when, before anybody spends money on a theory. We will tell you plainly if we find nothing wrong with your site, because that is the usual answer and it is worth more to you than agreement.
What a risk review covers:
A risk review is a one-off piece of work rather than a monthly service, so it is scoped against the size of the site and how much history it carries.
Every guide.
One practice.
Black hat, grey hat, link risk, thin content, the spam policies, negative SEO, manual actions, algorithmic penalties, how to check for one and how to recover from one.
