AdSense Ad Serving Limit: What It Means and What to Do

By Idea to Traffic Editorial Team · Published October 10, 2026 · Last updated October 10, 2026

The banner usually shows up without warning: a red notice in your AdSense Policy center that reads Ad serving is currently limited. Your earnings line flattens, page RPM drops, and some ad slots sit empty. It feels like a penalty, but it works differently from one, and the steps that help are not the ones most people try first.

What the limit actually is

An ad serving limit caps how many ads your AdSense account can show. Google describes it as an account level enforcement, which matters: it applies to every site in the account, not only the one you think caused it. Your account stays fully accessible, your reports keep working, and ad requests from your pages are still received. Google just fills fewer of them.

The Policy center gives one of two reasons, and they mean different things:

• Account being assessed. This is the common one for new publishers. Google has not seen enough of your traffic to trust it yet, so it serves a reduced number of ads while it watches. Nothing has to be wrong for this to appear.
• Invalid traffic concerns. This one says Google has seen clicks or impressions it does not consider genuine. It does not prove you did anything on purpose, but it does mean something in your traffic looks off.

Do not confuse either of these with the two site level notices in the same Policy center, Disabled ad serving and Restricted demand. Those are tied to a specific site and usually point at content or policy problems on particular pages, which is a separate fix.

How long it lasts

Google's own help page says the limit typically affects publishers for less than 30 days, and that it can last longer in some cases. For the assessment reason it adds that it cannot say how long the review will take. There is no countdown in the dashboard and no button to request a review.

Two details from Google's troubleshooter are worth knowing before you plan anything:

1. The limit is reviewed and updated automatically as Google keeps monitoring your traffic. Nobody needs to approve its removal.
2. Google can put the limit back after lifting it, either because it detects new problems or because it no longer has enough information to evaluate your traffic.

That second point is the reason the most common panic move backfires, which brings us to what not to do.

Mistakes that make it worse

Pulling the ad code. Plenty of publishers remove their AdSense units to "reset" things. With the code gone, Google sees no ad requests and has nothing to assess, and the troubleshooter specifically names a lack of information as a reason the limit can stay or return. A limited account still earns something. A removed tag earns nothing and teaches Google nothing.

Buying traffic to make up the loss. Paid pops, traffic exchanges and cheap "targeted visitor" packages are a fast route from a limit to a closed account. Google's help page warns that further invalid activity can lead to more enforcement or permanent closure.

Clicking your own ads to test them. Even one click to check that a unit works is a self click. If you need to see an ad render, look at it, do not click it, and preview pages from a browser where you are signed out of tools that might refresh pages automatically.

Adding more ad units. Stuffing extra slots onto pages to recover revenue tends to push accidental clicks up, which is the opposite of what a traffic quality review wants to see.

A 30 minute traffic check you can do today

For the invalid traffic reason in particular, your job is to find what looks unnatural before Google decides for you. Work through these in order.

1. Look at clicks by country and by site in AdSense. Open Reports, choose the Countries breakdown, and sort by clicks. Then switch to the Sites breakdown. You are hunting for a row whose page CTR is far above the rest. If your account averages around 1 percent page CTR and one country sits at 8 percent on a handful of page views, that row is your lead.

2. Match it against GA4. In Google Analytics 4 go to Reports, then Acquisition, then Traffic acquisition. Add a secondary dimension of Country and look at the same period. Sessions with near zero engagement time from one source or one country, arriving in bursts, are typical bot or click farm patterns. Check Session source too: a referral domain you never promoted is a red flag.

3. Read your raw logs if you have them. On a server you control, a quick count of the busiest IP addresses shows whether a few machines are hammering your pages:

awk '{print $1}' access.log | sort | uniq -c | sort -rn | head -20

A few IPs with thousands of hits each, in a month where your whole site had a few thousand visitors, deserve a closer look. On Cloudflare, the same question is answered under Security, then Analytics, where you can filter by country, ASN and user agent.

4. Block what is clearly not human. If one hosting provider network or one country with no real audience for your content is producing the odd traffic, challenge or block it at the edge. On Cloudflare that is a custom rule under Security, then WAF. Turning on Bot Fight Mode under Security, then Bots, is a reasonable step for small sites, though you should check afterward that real visitors and search crawlers still get through.

5. Audit anything you paid for or traded. List every place traffic came from in the past 60 days: ads you ran, social posts, newsletter swaps, freelancers promoting the site, "SEO packages". Any of them can send junk visits on your behalf. Stop the ones you cannot explain.

6. Check placement for accidental clicks. Look at your pages on a phone. Ads directly under a menu button, beside a download link, or that shift into place as the page loads collect clicks that were meant for something else. Give them room, and set Auto ads to fewer formats if they are landing in awkward spots.

If you are new and being assessed

For the assessment reason, Google's advice is to keep building content and audience while it watches. In practice that means keep publishing, keep your existing ad code live, and grow from sources that send real readers: organic search, communities where you contribute, and an email list. Organic search visitors are the easiest traffic for a quality review to trust because they arrive with intent and stay to read.

It also helps to make sure the basics a reviewer and a crawler see are sound, since a site with broken pages, thin templates or missing policy pages tends to attract the wrong kind of attention. If you want a quick structural pass, the free site checker runs 30 checks on any URL, including ads.txt, indexability and page basics, in about ten seconds.

What to expect on earnings

Google does not publish how much a limit reduces revenue. It lowers the fill rate rather than switching ads off, so most publishers see a drop instead of a zero. Watch two numbers in your AdSense reports over the next few weeks: ad requests, which should stay steady if your traffic is steady, and coverage or impressions, which should climb back as the limit eases. If ad requests fall, the problem is on your side: code removed, pages broken, or traffic lost. If requests hold and impressions recover, the review is working through your account.

Keep a simple dated log of every change you make during this period, such as a block rule added on a given day or an ad unit moved. If the limit returns later, that log tells you which change lines up with it.

Where this question came from

• Ad serving limits, AdSense Help
• Guide for Ad Serving Limits (AdSense)
• r/Adsense: Ad Limit on AdSense and Ad Manager, advice needed

Questions about AdSense ad serving limits