Why is my Google ad limited, not disapproved? Limited ad serving explained
Direct answerIf Google limited your ad serving, the ads can still be Eligible. Google is capping impressions because it currently treats the account as unqualified in scenarios it thinks are more likely to produce a bad user experience. That is not the same as a policy disapproval on a headline. Complete verification, make your brand unambiguous, then use the Limited Ad Serving appeal — not a rewrite of one RSA.
Two different statuses
| What you see | Limited ad serving | Disapproved ad |
|---|---|---|
| Object | Account / serving scenarios | One ad or asset |
| Ad status | Eligible (impressions capped) | Disapproved until the violation is fixed |
| How Google tells you | In-account notification when a meaningful share of impressions is in scope | Policy label on the ad (Policy manager) |
| Appeal path | Limited Ad Serving Appeals Form | Policy manager — see how to appeal |
Google’s Limited ad serving page is explicit: “Individual ads will not be disapproved.” If your RSA is actually Disapproved for unreliable claims or destination mismatch, fix that first. Limited serving will not be the reason that asset cannot run.
What “qualified advertiser” means
Google says it limits impressions from unqualified advertisers in scenarios more likely to produce negative experiences, using user feedback, prevalence of abuse, and industry trends. Factors it lists for qualification:
- Account attributes
- User activity and reports (it says it takes persistent user reports especially seriously)
- Account maturity
- Ad format usage
- History of policy compliance
- Advertiser industry
- Advertiser verification status
That list is an interpretation framework Google published — not a score you can see. Do not invent a “trust score.” Build the inputs Google named.
Advertiser verification is a separate program: Google emails you, an admin completes tasks, some ads may be restricted until it finishes, and missing the deadline can pause the account. Completing it does not automatically lift limited serving, but Google lists verification as a qualification factor and a best practice.
Search vs YouTube (2026 updates)
Treat these as published rollout notes, not a promise that every account has every rule live:
- YouTube (and related surfaces): Google may limit impressions from unqualified advertisers. Enforcement began earlier and expands over time.
- June 2026 Search update: Google may limit Search impressions when users persistently report the advertiser, when ads reference other brands without a clear association, or when ads and pages are generic with no branding. Implementation is gradual through 2028.
- August 2026 update: Google will extend the policy to all Google Ads, with a restated layout and best practices, still rolling through 2028.
What to change on Search ads
Google’s Search best practices (illustrative — they do not guarantee qualification):
- On Search, pin your own domain in headline position 1, put your brand on the ad and the landing page, and stop generic “official store” copy that could be any retailer.
- Fix actual policy issues first (claims, destination, misrepresentation). Limited serving stacks on top of those; it does not replace them.
| Pattern Google is worried about | Clearer pattern |
|---|---|
| “Official Nike store — 70% off today” (you are a third-party reseller) | “Shop at Northside Athletic. Authentic Nike gear in stock. See sizes.” |
| Headline 1: “Best deals online” with no brand or domain | Pin your domain in position 1, then a product-specific line |
| Landing page is a coupon blog that hops through three domains | Land on the HTTPS storefront you own — see destination mismatch |
Interpretation, not a rule: if users report “this wasn’t the store I thought,” Google may treat you as unqualified on those queries even when every RSA is Eligible. Branding is the published lever. Coupon cloaking is a different policy.
What not to do
- Do not clone 40 new campaigns hoping the cap is per campaign. Google describes an advertiser-level assessment.
- Do not file a disapproved-ad appeal for an Eligible ad.
- Do not expect Google to publish a calendar for when the cap lifts.
Frequently asked questions
Is limited ad serving the same as a disapproved Google ad?
No. Google’s Limited ad serving policy says individual ads will not be disapproved. You get an in-account notification when a meaningful share of impressions is in scope. A disapproval is a policy label on a specific asset (for example Unreliable claims). Limited serving is an impression cap while Google treats the advertiser as unqualified in certain scenarios.
Will rewriting one headline fix limited ad serving?
Usually not by itself. Qualification considers account attributes, user reports, account maturity, ad formats, compliance history, industry, and advertiser verification. Search best practices also include clear own-brand, avoiding generic copy, and pinning your domain in headline position 1. Editing a single RSA does not reset an account-level limit.
How do I appeal limited ad serving?
Google tells advertisers to complete the Limited Ad Serving Appeals Form from the in-account notification. It will reinstate an advertiser once they become qualified. That is a different path from Policy manager appeals used for disapproved ads. Google says it cannot say how long automatic reassessment takes.
Does this apply only to YouTube?
No. Early enforcement focused on YouTube. Google’s June 2026 update added Search scenarios (unclear branding, generic ads, user reports). An August 2026 update says the policy will cover all Google Ads, with implementation rolling through 2028. Confirm the live policy page for what is already live in your account.
Sources
- Google: Limited ad serving
- June 2026 Search update
- August 2026 all-Google-Ads update
- Advertiser verification
Rollouts are gradual through 2028. This page reflects public Google Ads policy articles as of September 18, 2026. Not a guarantee of impression volume.
Fix policy issues while the account is assessed
Limited serving does not replace claim review. Scan the RSA and landing page for unreliable claims and destination problems so compliance history is not working against you.