How Google Ads enforces policy
The Google Ads pillar summarises enforcement in its section on policies and account safety. Google enforces advertising policies at the ad, keyword, asset, landing page and account level. Ads that breach a policy are disapproved; repeated or serious breaches can suspend the account, and suspensions are far harder to reverse than disapprovals are to fix. That asymmetry is the reason to treat policy as part of account management rather than an occasional nuisance: a disapproval costs one ad's impressions until it is fixed, while a pattern of careless resubmissions puts every campaign at risk.
Three consequences follow for day-to-day work. First, policy applies to every element that can appear in or behind an ad: the headlines and descriptions of a Responsive Search AdA Google Ads search ad built from multiple headlines and descriptions combined at auction time., the sitelinks, images and other Ad AssetsExtra information such as sitelinks, callouts and phone numbers that Google Ads can add to an ad., the keywords that trigger them and the page the click lands on. Second, the landing page is reviewed too, so a change on the website can disapprove ads that nobody in the account touched. Third, the account carries a history: the pillar's advice to read the reason and fix the cause, rather than resubmitting an ad that still breaches the policy, exists because each careless resubmission adds to that record.
This guide covers what the published policies and the site's own guides state. It does not cover how strikes are counted, advertiser verification, appeal forms, review times or suspensions, none of which the cited pages document; Google Ads Help and the policy centre are the references for those. Nothing here is legal advice for a regulated category.
The four policy groups
The Google Ads policies page, listed in the sources below, organises every policy into four groups. Knowing which group a problem belongs to tells you what kind of fix to look for.
| Policy group | What it covers | Examples from the policies page | Usual kind of fix |
|---|---|---|---|
| Prohibited content | Things that cannot be advertised at all | Counterfeit goods, dangerous products or services, enabling dishonest behaviour, inappropriate content | Remove the product or the ad; no wording makes it acceptable |
| Prohibited practices | Ways of advertising that are not allowed, whatever the product | Abusing the ad network, data collection and use, misrepresentation | Change how the ad, the offer or the page behaves |
| Restricted content and features | Things that can be advertised only with limits, and sometimes only with certification | Alcohol, gambling and games, healthcare and medicines, financial services, trademarks, legal requirements | Meet the extra requirements, apply for certification where it applies, or accept limited serving |
| Editorial and technical | The quality and working standards ads and destinations must meet | Editorial standards, destination requirements, technical and ad format requirements | Fix the text, the asset or the landing page |
The policies page lists every policy within each group and links each to its detail; treat the table as a map for finding the right one, not as the policies themselves. Most problems in ordinary accounts sit in the last two groups: a restricted category the business did not realise it was in, or an editorial or destination problem that a careful read would have caught.
What each review status means
Ads and assets carry a review status. The ads not showing diagnosis names the ones that matter, and the policy detail on each ad explains the reason in the account.
| Status | What it means | What it asks of you |
|---|---|---|
| Under review | The ad or asset is new or was edited and has not been reviewed yet | Nothing yet; avoid repeated edits that send it back to review |
| Approved or eligible | The ad meets the policies and can serve | Nothing; whether it wins auctions is a separate question |
| Limited by policy | The ad can serve, but only in some places or to some people, because of a policy restriction | Read the detail; accept the limit if it is expected, otherwise fix the cause |
| Disapproved | The ad breaks a policy and cannot serve | Read the reason, fix the cause, then resubmit or appeal |
The status messages guide reads these alongside the campaign, keyword, bid strategy and conversion statuses in a weekly sweep. Ad strength is a different thing: it rates the asset pool for completeness rather than reporting whether the ad may serve.
Responding to a disapproval: fix the cause, then resubmit or appeal
The response the ads not showing diagnosis gives is the one to follow every time. Open the policy details on the ad, change the text, asset or destination that breaks the policy, and appeal only when you believe the decision is wrong. Done in order, it looks like this:
- Read the reason. The policy detail names the policy and usually the element involved: a headline, an asset, a keyword or the destination. Read the policy itself on the policies page, not just the label.
- Find the cause, not the symptom. If the reason is about the destination, the fix is on the website. If it is about a claim, decide whether the claim is true and supportable before rewording it. If several ads share the reason, the cause is probably shared too: a template, a page or an asset used everywhere.
- Fix it at the source. Correct the page, rewrite the claim, replace the asset. Editing the ad to slip past a reviewer without fixing the underlying problem is the resubmission the pillar warns builds a record.
- Resubmit, or appeal if the decision was wrong. Once the cause is fixed, resubmit the ad for review. If you believe the ad never broke the policy, appeal instead and say why. The mechanics of appeals are in Google Ads Help.
- Keep an approved fallback. The ads not showing diagnosis advises keeping an approved fallback ad in every ad group, so one disapproval never empties it.
Record each disapproval, its cause and its fix in the decision log. A cause that recurs is a process problem, and the record shows where.
Destination problems
The pillar lists what destination requirements cover: broken pages, misleading claims and pages that do not match the ad. It adds that many unexpected disapprovals are landing page problems, and the ads not showing diagnosis notes that a page that is broken, slow to load or blocked for Google's crawler can stop an ad.
That makes the website the most common source of policy trouble that the advertising team did not cause. A site release that changes URLs without redirects, a product page taken down, a login wall in front of a page that used to be public, or a new page whose offer no longer matches the ad can each disapprove ads overnight. The ads did not change; the destination did.
Two habits prevent most of it. Keep Message MatchHow closely a landing page repeats the promise and wording of the ad or link that sent the visitor. between the ad and the page: the price, the offer and the claim in the ad should be the ones the visitor sees on arrival, which is also what the landing page entry treats as the first test of a page. And make the paid account part of every website release: someone checks the final URLs of active ads after any change to page addresses, templates or access, as the guide to Google Ads during a website migration sets out for larger changes.
Restricted categories and certification
The pillar names some of the restricted categories, healthcare, financial services, gambling and alcohol among them, and states that they carry extra requirements and often certification. Its advice is to check the policy before building a campaign in a regulated category rather than after the disapproval. The policies page is the reference for which requirements apply to which category and country.
Trademarks sit in the same group. The responsive search ads guide notes that Google's trademark policy limits using a competitor's name in ad text, which is why competitor campaigns state what the business offers rather than naming the rival. Merchant Center has its own policies for products: a product disapproved for a price or availability that does not match its page is a feed problem, and the product feeds guide covers the account, feed and item checks that find it.
Where the business operates in a regulated sector, the advertising policy is only one of the rules that apply. The organisation's own compliance review, as the creative approval SOP describes, checks claims against their evidence before anything is published.
A pre-launch policy review (table)
A short review before launch catches most of the problems this guide describes. It sits inside the creative line of the campaign launch QA checklist, which asks for the ad to have passed policy review, and expands it into checks a reviewer can tick.
| Check | Question | Where the answer comes from |
|---|---|---|
| Category | Does anything the campaign promotes fall under prohibited or restricted content? | The policies page, read for the product or service |
| Certification | If the category is restricted, are the extra requirements met and any certification in place? | The policy for that category |
| Claims | Is every claim in headlines, descriptions and assets true and supported by evidence on file? | The compliance review in the creative approval process |
| Trademarks | Does any ad text use another business's name or mark? | The trademark policy; the responsive search ads guide |
| Editorial | Are spelling, capitalisation, punctuation and symbols used normally? | Editorial standards on the policies page |
| Destination works | Does every final URL load on a phone and a desktop without errors or unexpected redirects? | A manual check of each URL |
| Destination matches | Do the price, offer and claim on the page match the ad? | A side-by-side read of the ad and the page |
| Products | For product ads, are price and availability in the feed the same as on the page? | Merchant Center diagnostics |
| Fallback | Does every ad group have at least one ad already approved? | The ad status column |
A disapproval traced to the landing page (illustrative)
Tallowfinch Soap's disapprovals after a site change
Tallowfinch Soap, an invented handmade-soap shop, moves its website to a new theme on a Tuesday evening. By Wednesday morning 11 of its 26 search ads are disapproved, and the search campaign's impressions have halved. Change history shows no edits in the account that week. The policy details on all 11 ads point to the destination.
| When | What happened |
|---|---|
| Tuesday evening | New theme goes live; product collection pages move to new addresses |
| Wednesday morning | 11 ads disapproved; all point to the old collection addresses, which now return a not-found page |
| Wednesday, first fix | Web developer adds redirects from the 6 old collection addresses to the new ones; final URLs updated to the new addresses |
| Wednesday, second fix | While updating the URLs, the owner sees that 2 ads say "fragrance-free" while the new page for that range lists a fragrance oil in two of its bars; the range is checked against its ingredient sheets, the headline becomes "unscented options" and the page labels which bars are fragrance-free |
| Wednesday, resubmission | The 11 ads resubmitted once both fixes are live |
| Thursday | All 26 ads approved or eligible |
The shop adds two lines to its release checklist: check every active final URL the morning after any theme or address change, and check product claims in ads whenever product pages are rewritten.
Common mistakes
- Resubmitting without fixing. The ad is disapproved again, and the pillar warns that each such resubmission builds a record against the account.
- Fixing the ad when the page is the problem. A destination fault is fixed on the website; rewording the ad changes nothing.
- Treating limited by policy as an error. In a restricted category it may be the expected state; read the detail before changing anything.
- Building first and checking the category afterwards. The pillar advises checking the policy before building a campaign in a regulated category.
- Leaving website releases out of the paid account's process. Pages change, ads that pointed at them are disapproved, and nobody in the account touched anything.
- Appealing as a first response. Appeals are for decisions that were wrong, not for problems nobody has looked at yet.
- Running ad groups with a single ad. One disapproval empties the group; keep an approved fallback.
- Confusing Merchant Center and Google Ads problems. Product disapprovals are fixed in the feed or on the page, not in the ad.
