Policy
Dishonest declarations
There is a Google Publisher Policy with this exact name. Most publishers have never read it, which is a problem, because it is one of the easier policies to break by accident, and breaking it can quietly limit what Google will pay you.
By Mario Bailey · Published · Updated
It has nothing to do with your content. It is about whether the information you hand Google is true: your account details, the sites where your ads run, where your readers actually are, and your ads.txt file. Google's own wording is that the information you provide must be "materially accurate and complete, without misleading omissions," and cannot be "expressed in a deceptive or misleading manner."
Your account and contact details
Use your real address, date of birth, phone, and payment details, and do not dress them up. The policy specifically calls out obscuring your address with emoji or non-standard capitalization, submitting an inaccurate date of birth, and giving misleading phone or bank details. These feed payment and tax compliance, so a creative entry reads as evasion, not a typo.
Where your ads run
Run Google ads only on sites you have declared, and never falsify or hide the URL in a way that misleads where the ads will appear. An advertiser is buying a specific place. Misrepresenting that place is exactly the kind of declaration this policy exists to stop.
Where your users are
Do not override or spoof geolocation to make your traffic look like it comes from somewhere it does not. Geography is one of the largest drivers of what advertisers bid (US traffic monetizes far higher than most), so faking it to inflate your value is fraud, and an easy one for Google to detect.
Your ads.txt
ads.txt is the public file at your domain root that declares which companies are authorized to sell your ad inventory. The policy treats an inaccurate ads.txt or app-ads.txt as a dishonest declaration. Keep it current, list only sellers who actually sell your inventory, and remove the entries for networks you have left. Our free site scan checks whether yours is present and valid, which is the cheapest way to catch the most common version of this mistake.
Why it is worth knowing
None of this is about writing better articles, which is why it catches people off guard. Google's enforcement rule applies here as it does everywhere: when it finds a violating site, it either sends a warning asking you to fix it or, if the violation is severe, disables ad serving to the site immediately. And when policies are "repeatedly or egregiously violated," Google says it may act on the whole account, not just the site. The trigger is often accidental: a misconfigured ads.txt after a network switch, a stale URL, a VPN left running during setup. Publishers can spend weeks auditing their articles when the problem was a one-line file.
How to resolve a violation
If you have already been flagged, the path depends on whether you have a fixable issue in the Policy center or a full account suspension. The order is the same either way: find the exact problem, fix the real thing, then ask for one review.
- Find the exact issue. Do not guess. In AdSense, open the Policy center: it lists each active issue, the affected site or page, and the policy category, with a Fix link that shows the specifics. If the whole account was suspended or closed, the notice email names the reason. Start from what Google flagged, not from what you assume.
- Fix the specific declaration. Account or contact details: correct your real name, address, date of birth, phone, and payment details, and strip any emoji or odd capitalization. Where ads run: make the sites in your account match where the code actually runs. Geolocation: turn off any VPN, proxy, or geo override. ads.txt: correct the file at your root, then allow time for Google to re-crawl it, which Google says can take a few days, or up to a month on a site with few ad requests.
- Request the review, once. In the Policy center, select the fixed issues, confirm you have resolved them, and request the review. A suspension is different: Google says account suspensions "are unappealable," and describes the suspension as time to review everything, fix it, and put safeguards in place, because violations that continue afterwards lead to closure. Use that time to fix every declaration, not just the flagged one. A closed account has its own appeal path, covered in account disabled. Then wait. Do not resubmit an unfixed review; empty resubmissions waste the queue and your time.
- If you believe it is a false flag, you can still request a review saying so, but fix anything that even looks inconsistent first, a stale ads.txt line, an old address, because a clean account clears faster than an argument.
Honest expectations: Google says it typically responds to review requests "within a week but sometimes it can take longer." Accidental cases, ads.txt above all, are the kind a real fix and a re-crawl can clear. Keep a dated record of what you changed; if you have to escalate, that record is your case.
Staying clean
- Real legal name, address, date of birth, and payment details in AdSense. Never obscured.
- Google ads only on domains you own and have added to your account.
- No VPN, proxy, or geolocation override that changes where your traffic appears to originate.
- ads.txt at your root, current, listing only legitimate authorized sellers, with dropped networks removed.
- When your hosting, your sellers, or your business details change, update the declarations to match.
This is the one place where dishonest declarations run from you to Google. Most of what we write about is the same dishonesty running the other way, the claims the industry makes to you. Both can cost you money. This one can cost you the account.
Scan your site Read the studies
Sources: Google Publisher Policies, Dishonest declarations; AdSense Help, Account suspended for invalid traffic or policy reasons. Quotations are Google's. Current as of October 2026.