Google penalty » Check tools, Diagnose a Google Penalty » Search engine SPAM detector
Search engine SPAM detector
What does this tool do? This tool analyzes a web page, searching for characteristics that search engines could consider spam. If you don’t know what “search engine spamming” means or if you want to know how this tool works, you can read the Spam detector FAQ.
What type of tricks does it find? The tool tries to detect three main methods: keyword stuffing, doorway farms and hidden text. Any trick based on Javascript or on CSS positioning/layering will not be detected (for now). Search engine spam detection is very difficult to accomplish and this tool can’t recognize all the existing tricks/methods; it isn’t perfect and it sometimes fails.
Why did you create this tool? To persuade webmasters and SEO to think: if I have been able to create a simple tool capable of intercepting some techniques of spam, imagine what a team of engineers, working for a search engine, could do!
Tool Source : motoricerca.info
Filed under: Check tools, Diagnose a Google Penalty · Tags: seo tool, SPAM detector
Nice tool.
It can help a lot to avoid any kind of panalty in google and other search engines
I was greatly helped with the search engine spam detector. thanks
Swiffer Coupons…
[...]following are some references to websites online I always connect to because we feel these are really worth checking out[...]…
Just wanted to thank you for this information. Last month after my site had been gaining visitors I saw a sudden drop in my rankings.I read everything on penalties went back and made lots of changes. The URL’s were still there but not showing up in search results. Found this spam detector which reported possible keyword stuffing issues. After disecting a few of my post down to nothing and still having issues went to my SEO pluggins. I’m new at SEO so I don’t know if it was a combination of things but once I removed keyword meta tags in my Yoast SEO pluggin 3 hours later after being recrawled my post were back at the top.Hopefully this might help someone else if they run into the same issue as myself.
Thanks again, Kevin