AdSense enforcement: restricted, disabled, terminated — which one are you?
Most AdSense enforcement is page-level: ads stop on the offending page, you fix it, they come back. Account-level restriction is rarer and usually temporary. Termination is rarest and comes from a short, specific list — invalid traffic at scale, distributing infringing material, and above all attempting to circumvent an earlier enforcement.
- Read which level the notice is at. The notice names its scope. "Page-level" affects specific URLs. "Site-level" affects a property. "Account-level" affects everything. Panic is usually a response to reading a page-level notice as an account-level one.
- Fix the named thing, not everything. Broad unfocused changes make it harder to demonstrate what you did. Address exactly what the notice describes, and keep a record of the change and its date.
- Check whether the same problem exists elsewhere. Enforcement names an example, not an inventory. If one page tripped a content rule, others probably do too, and fixing only the named one invites a second notice.
- Request review once, properly. One considered request beats three hurried ones. Say what you found, what you changed and when. Do not request review before the fix is live and crawlable.
- Never work around an enforcement. Moving the content to a new URL, spinning up a second account, or hiding ads from Google's crawler turns a page-level problem into a terminal one. This is the single most reliable way to lose an account permanently.
Three levels, and most people misread which one they are on
A policy notice arrives and the instinct is to assume the worst. Usually the
worst has not happened. AdSense enforcement runs at three levels, and they are
very different situations.
Page-level. Ads stop serving on specific URLs. The rest of the site is
unaffected, revenue barely moves, and fixing the named issue restores it. This
is the overwhelming majority of enforcement and it is closer to a correction
than a punishment.
Site or account-level restriction. Demand is limited rather than removed.
Ads still render — which is exactly why this one goes unnoticed. Nothing looks
broken. Fewer advertisers are permitted to bid, so RPM falls, and a publisher
who checks their account monthly connects the drop to nothing at all.
Termination. The account ends. Rare, and it comes from a specific short list
rather than from accumulated small mistakes.
Reading a page-level notice as though it were a termination leads to panicked
sitewide changes that make the actual fix harder to demonstrate.
What actually ends accounts
Not "too many violations". The list is shorter and more specific than the folklore
suggests:
Invalid traffic at scale. The largest single cause. Worth understanding that
intent is not part of the test — buying
traffic from a source that turned out to be a bot farm produces the same data as
generating it deliberately.
Distributing material you have no right to distribute. Not quoting or
referencing — hosting or linking to infringing files. This is treated far more
severely than an ordinary content policy issue.
Deceptive practices. Misleading ad placement, content that misrepresents
what it is, dressing ads up as navigation.
Circumventing an enforcement. The one that turns fixable problems into
permanent ones, and the one publishers walk into by accident.
Circumvention is the trap
When a page is restricted, the fastest-feeling response is to make the problem
go away rather than fix it. Move the content to a new URL. Noindex it. Put it
behind a login. Open a second account "just for that site". Serve different
content to Google's crawler than to visitors.
Every one of those reads as evasion, and evasion is treated as a different
category of problem from the original issue.
The specific version that catches honest publishers: a page is restricted, the
publisher deletes it and republishes essentially the same thing at a new URL,
believing they have complied. From the outside that is indistinguishable from
deliberately dodging the enforcement.
If you are unsure whether a response is a fix or a workaround, the test is
whether you would describe it that way in a review request. "I removed the
content" is a fix. "I moved it somewhere they were not looking" is not.
Restriction is the one to actively look for
Termination announces itself. Page-level notices announce themselves.
Restricted ad serving is the one that behaves like a silent revenue leak.
Your ads render. Your traffic is unchanged. Your dashboard shows a normal-looking
page. The only symptom is that RPM fell, and by the time anyone investigates,
several other things have changed too.
This is the same shape as every other problem this site is about: the failure is
real, the cost is continuous, and nothing surfaces it in the numbers you
routinely look at. If your RPM dropped on a specific date and you cannot explain
it, an account notice belongs on the checklist —
near the end, but on it.
Before you request review
Fix the named thing. Then check whether the same problem exists on pages the
notice did not name — enforcement gives an example, not an inventory, and
fixing only the example invites a second notice that looks like a pattern.
Then submit one considered request describing what you found, what you changed
and when. Not three hurried ones, and not before the fix is live and crawlable.
Frequently asked
- Does one policy violation get my account banned?
- Almost never. The overwhelming majority of enforcement is page-level: ads stop serving on specific URLs, you fix the issue, and they resume. Termination follows a pattern or a specific severe category, not a single first-time mistake.
- What does "ad serving has been restricted" actually mean?
- Demand is being limited on your account rather than removed. Ads still render but fewer advertisers compete, so RPM falls — often sharply, and often without the publisher connecting the drop to the notice sitting in an account they check monthly.
- What actually gets an account terminated?
- A short list: invalid traffic at scale, distributing material you have no right to distribute, deceptive practices, and attempting to circumvent an enforcement action. That last one converts fixable problems into permanent ones more often than the others combined.
- Can I appeal a termination?
- There is an appeal process and it does sometimes succeed, most often where the publisher can show the invalid traffic came from a source they did not control and have since stopped. Appeals that argue the policy is unfair rather than that the finding is factually wrong do not tend to go well.
- Will a new account solve it?
- No, and it makes things worse. Opening a second account after a termination is itself a violation, and the association is not difficult to detect. It moves the outcome from "one terminated account" to "this person cannot use AdSense".