Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Fixing a false positive in Safesearch

         

Asia_Expat

12:06 am on Jan 21, 2011 (gmt 0)

10+ Year Member



For many years, my website has been wrongly filtered by Safesearch. Nothing I did fixed the problem. Even trying to communicate with Google via webmastertoold/re-inclusion request got me nowhere. A couple of WW thread on the problem here (including mine)...

[webmasterworld.com...]
[webmasterworld.com...]

Worse still, my site was being completely filtered from the normal websearch results by Safsearch 'strict'. This eliminated traffic I was getting from people surfing from work, as many corporate LANs have the safesearch strict cookie enfoced on their entire network.

It's caused me a lot of frustration over the years, and sometimes despair at the traffic I might have been losing...

Finally, I've got it fixed. The only way to communicate with Google over the problem is via the Google forums at Webmaster Central. The Google employee you need to approach is Susan Moskwa, and she's a regular poster there. If your site is genuinely clean, she will do her best to help you by liaising with her colleagues on the Safesearch team.

As far as I can tell, my site is finally free of the Safesearch filters. What a relief!

tedster

3:23 am on Jan 21, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Thanks for sharing the good news. It is good to hear that Google's own forums gave you tangible help. Given how many websites there are to deal with, it sounds like they're doing OK with webmaster support.

Can we assume that you are talking about Image Search here?

Asia_Expat

3:26 am on Jan 21, 2011 (gmt 0)

10+ Year Member



Yes, but my site was also being totally removed from the main web results if 'strict' safesearch was in place... Either way, my site is now completely free of the filters. It took around three years.

piatkow

10:28 am on Jan 21, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I had that problem years ago but in those days you could still communicate direct with G. It was down to a "suspect" character string within a place name for a location related site.