All publishers are required to adhere to the following policies, so please read them carefully. If you fail to comply with these policies without permission from Google, we reserve the right to disable ad serving to your site and/or disable your AdSense account at any time. If your account is disabled, you will not be eligible for further participation in the AdSense program.
Because we may change our policies at any time, please check here often for updates. In accordance with our online Terms and Conditions, it’s your responsibility to keep up to date with, and adhere to, the policies posted here. Exceptions to these policies are permitted only with authorization from Google.
Invalid clicks and impressions
Encouraging clicks or views (non-rewarded inventory)
Except for rewarded inventory, publishers may not ask others to click or view their ads or use deceptive implementation methods to obtain clicks or views. This includes, but is not limited to, offering compensation to users for viewing ads or performing searches, promising to raise money for third parties for such behavior or placing images next to individual ads.
Publishers should not place AdSense code on pages with content that violates the Google Publisher Policies. Doing so may result in your account(s) being suspended or terminated.
Publishers may place AdSense code on pages with content in scope of the Google Publisher Restrictions, though this content will likely receive less advertising than other, nonrestricted content.
Publishers may not place Google ads on sites that contain abusive experiences. See the abusive experiences page for more information.
Authorized inventory (ads.txt)
If AdSense publishers choose to use ads.txt on their domains, those publishers must ensure that they are included as authorized sellers of that inventory. For more information, see declare who is authorized to sell your inventory with ads.txt.
Google ads may not be placed on pages receiving traffic from certain sources. For example, publishers may not participate in paid-to-click programs, send unwanted emails or display ads as the result of the action of any software application. Also, publishers using online advertising must ensure that their pages comply with Google’s Landing Page Quality Guidelines.
Publishers are permitted to make modifications to the AdSense ad code so long as those modifications do not artificially inflate ad performance or harm advertisers. Please see modification of the AdSense ad code for more information.
Publishers are encouraged to experiment with a variety of placements and ad formats. However, AdSense code may not be placed in inappropriate places such as pop-ups, emails or software. Publishers must also adhere to the policies for each product used. Please see our ad placement policies article for more information.
Sites showing Google ads should be easy for users to navigate. Sites may not change user preferences, redirect users to unwanted websites, initiate downloads, include malware or contain pop-ups or pop-unders that interfere with site navigation.
Deceptive site navigation
Publishers may not use deceptive implementation methods that place ads in a way that might be mistaken for menu, navigation or download links to obtain clicks or views. Keep in mind that every publisher is responsible to ensure that their ad implementation adheres to the ad placement policies.
This includes, but is not limited to:
False claims of streaming content, or downloads
Linking to content that doesn’t exist
Redirecting users to irrelevant, or misleading webpages
Other types of navigation that is designed to intentionally mislead users
Pages where ads are implemented in placements that are intuitively meant for navigation.
To help you provide a quality user experience, Google has developed technical specifications for sites displaying Google ads. We only allow sites that comply with these technical specifications. Please review below for detailed technical requirements:
AdSense for content (AFC) and Ad Exchange (AdX) display ads are not supported through all WebView technologies. App developers wishing to monetize by publishing AFC and AdX display ads through a WebView must use one of the following supported viewing frames:
Android: Chrome Custom Tab
iOS: SFSafariViewController (iOS9 and iOS10 only)
Google AdMob and AdX in-app ads may be shown in an app next to a WebView so long as the Google