Fiction: I shouldn’t be held responsible if users post content on my site or network that violates AdSense policies.
Fact: You are responsible for ensuring that all of your content, including user-generated content such as forum posts, blog comments or outside feeds, is in compliance with AdSense policies on any page or site for which you’ve enabled AdSense ads.
As we’ve discussed in previous posts in this series, we regularly review the content in the AdSense network to ensure that it's safe for advertisers, users, and publishers, as network quality is of premium importance. Just as you, our publishers, expect us to do all we can to remove undesirable ads, our advertisers expect high standards to be maintained; for example, a company using AdWords to market baby clothes doesn’t want their ads to appear next to violent or mature content. In order to be transparent about what kinds of content violate our policies, we’ve published a complete list in our Help Center.
Making sure content complies with our policies can be complex when factoring in user-generated content. Keeping tabs on the hundreds (or even thousands!) of videos, blog posts, photos, tweets, and comments that can come in every day is a massive undertaking. However, you are ultimately responsible for all sites on which you have placed your ad code, regardless of whether you own or have produced the content. This blog post provides a few suggestions to help you prevent and monitor potential content violations.
In most cases, our first step after a policy violation is found is to issue a policy notification for the site. Exceptions include DMCA and egregious policy violations, more details here. After the initial notification, you need to take action, not simply respond to the warning, but implement solutions to proactively ensure that violating content is removed and new content added to the network or site complies with our policies.
We understand that it can take time to find the best solution to prevent problematic content from appearing on your site and we want to work with you to give you the time needed to find a fix. If it becomes evident that a publisher is unable to do so, or if the violation is continuing or egregious, then we will disable an account. We offer an appeals process, but the bottom line is, we can’t partner with publishers that pose a risk to our advertisers (just as we won’t partner with advertisers that could compromise you).
We know how hard you work to make sure that your sites are of the highest quality and free of adult content, unoriginal content, or anything else that may violate policies and we thank you for your efforts. When advertisers, publishers, and users know they can trust the integrity of our advertising environment, everyone wins.
Home /
Facts and Fiction /
Program Policies /
AdSense Facts & Fictions Part VI: User-Generated Content
Monday, January 31, 2011
AdSense Facts & Fictions Part VI: User-Generated Content
Share this
Related Articles :
Subscribe to:
Post Comments (Atom)
Labels
AdSense features
94
Optimization
88
Other
69
Other Google products
42
Mobile
39
International
35
Program Policies
26
Tips
26
Multi-Screen
23
Case studies
21
Video
21
Content strategy
20
AdSense Interface
19
AdSense Team
19
Best Practice
19
Earnings/Reports
19
Payments
19
Ad formats
18
AdSense101
11
Tips to earn more
11
Viewability
11
adsense guide
11
Active View
9
Global
8
Produce update
8
googlenew
7
Ad layout
6
AdSense In Your City
6
Facts and Fiction
6
Feedback
6
Google Analytics
6
Learn with Google for Publishers
6
Matched content
6
Newbie
6
PageSpeed
6
download
6
DoubleClick
5
Education
5
Support
5
guide
5
micro-moments
5
AskAdSense
4
Certified Partners
4
Passion into profit
4
Social
4
Webinars
4
audience
4
eBook
4
engagement
4
AMP
3
Responsive
3
Google's Certified Publishing Partner
2
News
2
infographic
2
native ads
2
Appeal
1
Branding
1
CPT
1
CTR
1
Guest Blogger
1
Hangout on Air
1
Help
1
Japanese
1
Material Design
1
Monetization
1
Portuguese
1
Product update
1
RPM
1
Spanish
1
Troubleshoot
1
YouTube
1
get started
1
Powered by Blogger.
0 comments
Post a Comment