# AdSense 网站审核：政策违规。您做了什么使其获得批准？ **URL:** \ **Category:** Support\ **Created:** [2019年三月27日 08:37 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678 "2019-03-27T08:37:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![WaitroseCarpark](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/waitrosecarpark/32/198599_2.png) [@WaitroseCarpark](https://meta.discourse.org/u/WaitroseCarpark)\ **Post date:** [2019年三月27日 08:38 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678/1 "2019-03-27T08:38:00Z")
I’m wondering whether anyone has recently (eg within the past few months) managed to get their site approved for AdSense ads. I submitted mine and got declined for the following policy violation reason: > You need to fix some things before using AdSense > We’ve found policy violations on [https://myforumurl](https://myforumurl) that are preventing your site from being approved: > > - Dynamic content > > Publishers may not place Google ads on pages or apps where dynamic content (e.g. live chats, instant messaging, auto-refreshing comments, etc.) is the primary focus of the page or app. I can’t really argue that the pages don’t contain dynamic content or that it isn’t the primary focus of the page or app, eh? Unless I wrap the forum inside a Wordpress instance?? Has anyone managed to get approved recently? Or if you had this issue, what did you do to resolve it? ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2019年三月27日 10:57 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678/2 "2019-03-27T10:57:45Z")
> [@WaitroseCarpark](#): > > dynamic content (e.g. live chats, instant messaging, auto-refreshing comments, etc.) is the primary focus of the page or app. Do you have any third party plugins installed? I’m not aware of any default configured Discourse instances running into this. ---
**Author:** ![WaitroseCarpark](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/waitrosecarpark/32/198599_2.png) [@WaitroseCarpark](https://meta.discourse.org/u/WaitroseCarpark)\ **Post date:** [2019年三月27日 12:03 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678/3 "2019-03-27T12:03:31Z")
Just the `discourse-sitemap` and `discourse-adplugin` (currently configured to use amazon (until I get adsense approved)). Think that might be something to do with it? ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2019年三月27日 23:46 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678/4 "2019-03-27T23:46:35Z")
Mostly I meant _third party_ plugins, we run most of the first party plugins on our hosting. ---
**Author:** ![WaitroseCarpark](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/waitrosecarpark/32/198599_2.png) [@WaitroseCarpark](https://meta.discourse.org/u/WaitroseCarpark)\ **Post date:** [2019年三月28日 05:27 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678/5 "2019-03-28T05:27:04Z")
None. I’m wondering whether it was because there was some profanity in one of the thread titles (that was the title of a film) so wonder if I got declined for that. ---
**Author:** ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)\ **Post date:** [2019年三月28日 05:52 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678/6 "2019-03-28T05:52:11Z")
That certainly would not have helped. If you run Adsense on content that is clearly controlled by third parties, you’re likely to get banned (or not accepted). Always make sure to moderate heavily if you want to use Adsense on your forum, or you’ll lose your account the first time someone uploads a picture of a nude woman holding a gun and they notice it before you do. ---
**Author:** ![WaitroseCarpark](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/waitrosecarpark/32/198599_2.png) [@WaitroseCarpark](https://meta.discourse.org/u/WaitroseCarpark)\ **Post date:** [2019年四月5日 18:48 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678/7 "2019-04-05T18:48:18Z")
I did the following and was approved only hours after re-applying: - Added privacy policy banner - Removed any profanities from post topic titles - Ensured Privacy/Terms/Contact info was clearly listed in the hamburger menu - Pinned a post for first time users asking new users to check the Terms and Privacy policy, and also stating the site was constantly moderated. Thanks all for the help. ---
**Author:** ![Terrapop](https://avatars.discourse-cdn.com/v4/letter/t/ecd19e/32.png) [@Terrapop](https://meta.discourse.org/u/Terrapop)\ **Post date:** [2020年九月6日 09:55 UTC](https://meta.discourse.org/t/adsense-site-approval-policy-violation-what-did-you-do-to-get-it-approved/112678/8 "2020-09-06T09:55:30Z")
这就是为什么我赞助了这个插件： > [@\[PAID\] Integrate Google Cloud Vistion API into upload process](https://meta.discourse.org/t/paid-integrate-google-cloud-vistion-api-into-upload-process/161746): > > A plugin that checks all images uploaded to Discourse via the Google Cloud Vision API and rejects if not appropriate according to set levels. Documentation: A Ruby Gem is provided by Google: [https://googleapis.dev/ruby/google-cloud-vision/latest/index.html](https://googleapis.dev/ruby/google-cloud-vision/latest/index.html)[https://googleapis.dev/ruby/google-cloud-vision/latest/Google/Cloud/Vision.html](https://googleapis.dev/ruby/google-cloud-vision/latest/Google/Cloud/Vision.html)[https://cloud.google.com/vision/docs/detecting-safe-search](https://cloud.google.com/vision/docs/detecting-safe-search) This plugin should hook into the main image upload process of Discourse for all images (posts, a… 它几乎可以投入生产了。 还有一个拉取请求需要与核心代码合并： > > > ~~I tried satisfying this condition forcefully which results in a console error.…~~ If the value is falsy i.e. an empty array/object, the control would go to the generic error condition in https://github.com/discourse/discourse/blob/f2842490d3ccaf9e29b0ffc43f193350334ead94/app/assets/javascripts/discourse/app/lib/uploads.js#L300 > > As an aside, would this condition ever be satisfied? > > IMHO, the \`displayErrorForUpload\` method should always be called so that the correct reason for the error is displayed in the popup. The current code forces the popup to be displayed for the generic condition which is not very helpful for the user. > > Here, an example where the method is called correctly(IMO) https://github.com/discourse/discourse/blob/f2842490d3ccaf9e29b0ffc43f193350334ead94/app/assets/javascripts/discourse/app/components/composer-editor.js#L772 > > I'll change the commit message if the changes are approved. 稍后更新。