Policies & violations

AdSense policy edge cases: forums and UGC, comment sections, login pages, PDFs, print pages and staging sites

Last updated Published By the editorial team6 min5 sources

Key takeaways

  • Google defines content as anything on a monetized page, including user-generated content like comment sections, other advertisements and links to other sites.
  • Google states that publishers are responsible for the content on every page they monetize, even content created by someone else, such as on sites with user-generated content.
  • Google may disable ad serving on content it cannot evaluate, including password-protected content when the publisher has not provided login credentials to Google.
  • Google ads may not be placed on screens where private communication between people is the primary focus, such as direct messages, live chats and private chatrooms.
  • Another publisher may place ad code on the same page as yours with the site owner's permission, but each publisher is responsible for the content of sites carrying its code.
Red jigsaw puzzle pieces fitted together
Image: Red jigsaw puzzle pieces,Profpcde,CC0,via Wikimedia Commons.

Most AdSense edge cases come down to three rules: everything on a monetized page counts as your content (including comments and forum posts), Google must be able to evaluate the page, and ads never go on screens without real publisher content or meant for private communication. Forums, login areas, PDFs, print views and staging sites each apply those rules differently.

Quick answers

Situation Allowed? Condition or reason
Ads on forum threads and Q&A pages Yes You are responsible for all user posts on monetized pages
Ads on articles with open comments Yes Comments count as your content; moderate them
Ads in private messages, inbox, live chat No Private communication screens are excluded
Ads on members-only pages Yes, with care Google must be able to evaluate the content
Ads on login, sign-up, password pages No Behavioral screens without publisher content
Ads inside PDF files No supported method AdSense code runs only on web pages and approved WebViews
Ads on separate “print version” URLs Avoid Duplicate, navigation-free copies add no publisher value
Ads on a staging or preview site Avoid Only your team visits; risk of inflated impressions
Your ad code on someone else’s site Yes, with permission You share responsibility for the site’s compliance
Ads on Blogger or other hosted platforms Yes Check the host’s terms; you may need HTML access
Ads on content not in a supported language No “Unsupported languages” policy

Forums, communities and user-generated content

Google’s definition of content is the starting point. In Understand the Google Publisher Policies and Google Publisher Restrictions, content means “anything present on your page or app - including user generated content like comment sections, other advertisements and links to other sites or apps.”

Google’s page on accounts closed for policy reasons adds the consequence: “you are responsible for the content on every page you monetize with Google ad code, even if the content was created by someone else, such as on sites with user-generated content.” An extensive history of policy violations is listed among closure reasons.

How forum operators keep ads compliant:

  1. Moderate before monetizing. New threads or new members can go to a moderation queue before appearing on monetized pages.
  2. Exclude risky sections. Off-topic, “anything goes” or adult-adjacent boards can run without ad code.
  3. Filter obvious problems automatically. Word filters, link limits for new accounts and image moderation reduce exposure.
  4. Make reporting easy. A visible “report post” button helps you find problems before Google does.
  5. Act on Policy center issues at the template level. If one thread triggers an issue, check similar threads and the section rules.
  6. Watch user uploads. Pirated files or copied articles posted by users count as your content; see copyrighted material.

Comment sections on articles

Comments live on the same monetized page as your article, so a single unmoderated comment can bring hate speech, harassment or explicit content onto it. Options, from safest to most open: closed comments, pre-moderated comments, comments loaded only after a click on a separate unmonetized view, post-moderation with fast removal. Google does not mandate one approach; it holds you responsible for the result.

Pages behind a login

Two rules from the Ad placement policies apply:

  • “Ads on content that we cannot evaluate”: Google may disable ad serving on content it cannot evaluate, “including but not limited to content whose robots.txt file blocks Google’s crawling and password-protected content where the publisher has not provided login credentials to Google.”
  • “Ads in private communications”: no ads on screens where private communication is the primary focus, such as “direct messages, live chats, video-chats, private chatrooms.”

So a members-only article library can carry ads if Google can evaluate it, while a members’ inbox cannot carry ads at all. The login form itself is a behavioral screen with no publisher content; keep it ad-free (see no content screens).

PDF files and print pages

Google’s ad placement policies say: “AdSense code may only be implemented on web-based pages and approved WebView technologies.” A PDF is not a web page running the AdSense script, and Google documents no way to place AdSense inside one. Monetize the HTML page that presents the document, and make sure that page has real content, not just a download link (a page with only a download button and ads is also an accidental-click risk).

Print pages are not addressed by Google. Two practical points:

  • Separate “print version” URLs are usually stripped copies without navigation or added value. Keep ad code off them.
  • Print styling of your normal pages is a user experience choice; Google does not publish guidance about ads in printed output.

Staging, preview and development sites

Google does not publish a staging-specific rule. The relevant policies are general:

  • Publishers may not “use any means to inflate impressions and/or clicks artificially, including manual methods” (AdSense Program policies).
  • A staging site is visited mainly by you and your team, who load pages repeatedly while testing.

Best practice therefore is to load the AdSense script only on the production hostname, show neutral placeholders elsewhere, and block staging from search engines with authentication. See clicking your own ads and safe testing.

Sharing a page with another publisher

The ad placement policies allow it: if the site complies and its owner has given you permission, “you may place your ad code on the same page as the other publisher’s ad code.” You are credited only for clicks and impressions on your own units. Google adds: “every publisher is responsible for the content of a site on which their ad code is placed. If a site is found in violation of our policies, we will notify any publisher(s) whose ad code is on the site.”

This is common on guest-author platforms and revenue-sharing communities. Before agreeing, check the site’s moderation and traffic sources, because their problems become yours.

Hosted platforms and subdomains

Google allows AdSense on “any page which complies with our Program policies, including hosted sites”, but notes you might need access to the site’s HTML and that “it is also your responsibility to check with your host and determine if using AdSense is a violation of their terms of service.” For how to add hosted sites and subdomains to your account, see subdomains and subdirectories.

Hacked sites with someone else’s ad code

Google’s AdSense policy FAQs cover this: remove the injected ads by deleting the ad code from your source, and review your site’s security so unauthorized people cannot access your source code. Then check the Policy center: injected spam pages can trigger issues on your own account if your code is on them.

Pages in unsupported languages and multilingual sites

The Google Publisher Policies include “Unsupported languages”: Google does not allow content that “is not primarily in one of the supported languages.” On multilingual sites, keep ad code off sections written primarily in an unsupported language. Before launching a new language section, read the “Unsupported languages” policy details linked from the Google Publisher Policies.

Common mistakes

  • Monetizing every forum board by default, including unmoderated ones.
  • Leaving ad code in the members’ inbox because it shares the forum layout.
  • Blocking Google with robots.txt on monetized sections, then wondering why ad serving is disabled.
  • Running live ads on staging and on preview links shared with clients.
  • Letting a partner add their ad code without checking their traffic sources. For the complete list of forbidden places, see where ads cannot go, and for content categories, prohibited vs restricted content.

Frequently asked questions

Am I responsible for what users post in my forum or comments?

Yes. Google defines content as anything present on your page, including user-generated content like comment sections, and says you are responsible for the content on every page you monetize, even when someone else created it. A hateful or explicit comment can trigger a policy issue on the page, so moderate actively and keep ads off sections you cannot moderate.

Can I show AdSense ads on pages that require a login?

Login-protected pages are not banned, but Google says it may disable ad serving on content it cannot evaluate, including password-protected content where the publisher has not provided login credentials to Google. Private messaging screens are a separate case: Google does not allow ads where private communication is the primary focus.

Can I put AdSense ads in a PDF?

No supported method exists. Google's ad placement policies say AdSense code may only be implemented on web-based pages and approved WebView technologies, and a PDF is a document file, not a web page running the ad script. Monetize the HTML page that links to or describes the PDF instead.

Should my staging site have the AdSense code?

Keeping live ad code off staging is the safe choice. Google's policies prohibit inflating impressions or clicks by any means, and a staging site is mostly visited by you and your team, who are testing, not genuinely interested in ads. Use placeholder boxes of the same size on staging, and load the real code only in production.

Sources

  1. Understand the Google Publisher Policies and Google Publisher Restrictions · Google AdSense Help
  2. Ad placement policies · Google AdSense Help
  3. AdSense account closed by Google for policy reasons · Google AdSense Help
  4. AdSense policy FAQs · Google AdSense Help
  5. Google Publisher Policies · Google Publisher Policies Help