Create topic New topics

Forum

Help me, please!

Google Adsense Problem Also...

nightowl
Admin
Posts: 488
Message
on 03/18/2022

Hardly a days goes by that Google doesn't restrict ad serving on one of the articles. In some cases it seems to be temporary, in others it may be permanent.

As you may know, Google is very sensitive as to what content may be shown on a page in order to be considered for ad serving. "Offensive" items could be anything deemed shocking, scandalous, gory, sexual, tobacco or alcohol related, and so on.

It doesn't even need to be an article about those topics; sometimes the cover art of a featured book is enough to trigger ad blocks. I've also seen cases where I couldn't find anything wrong with the page except for the fact that some embedded videos were no longer valid. It's a good idea to revisit pages from time to time and make sure all the links, products, embeds etc. are still working. 

We don't really have much of a say in it. In the interest of everyone here who wants to use Adsense, we did however, on occasion, disable ad serving on pages that were obviously running afoul of Google's sensitive nature. 


SEO Praxis: Specializing in WordPress Hosting and Small Business Web Design.
boutiqueshops
Posts: 21
Message
on 03/18/2022

I guess Google is training their staff in over-sensitivity here on Wizzley.  I thought it was my costume site, but maybe they moved their classes here.  LOL So yes, I'm familiar with their sensitivities.

My zombie costume page is frequently targeted for "gory" because of images of people on a zombie walk and some zombie make up videos.  There was another page they objected to also, but I can't remember what it was.  YET, the Playboy bunny costume page has never been targeted.  

I'll have to think about how to proceed.  Since the affiliate marketing is limited to Amazon & Zazzle, with a little bit of Viglink (now SOVRN), I had hoped for a better contribution from Adsense. Frown

Disappointing because I really missed writing here.  Thanks for your help,

Sylvia

Loading ...
Error!