Google doesnt need to be that smart to find autoblogs

peixe01

Junior Member
Joined
Apr 17, 2010
Messages
198
Reaction score
338
search for: inurl:wp-content/plugins/WPRobot3/

and let the ban stick fall... guys protect yourself, use a condom.
 
@basstrackerboats= good point again BUT its upto google to decide how to judge those blogs.
 
Collateral damage. Cynical but those who can afford not to care about it are simply ignoring it.
 
I actually have it on a site as part of an experiment I am doing to see if something in particular works for SEO.. it's nothing to do with my linkpushing process but I do have an idea and think that what I am doing is going to work.

If G comes and slaps me... too bad for me but I've had the site up for only 6 weeks... not monetizing it at all and am getting some traffic and some ranking in G of course.
 
I read in some autoblog book that you can set in the robot.txt file not to spider the Plugin folder.Never do it myself...But i guess those who do it can survive the doomsday...when it comes.
 
with new wordpress version this folder is not browsable ;)

If it is just put a html file in there and thats it
 
Consider following..

robots.txt doesn't block SE in the way that they can't see beyond it, it is for informational purposes only, it is actually up to SE if it want to obey it or not.

.htacces file does block SE from physical access to the certain directories, but can be indirectly detected by response headers that in the rules

directory name of any plugin can be simply renamed with the little tweaking

there is more plugins out there can do autoposting, not just WP-Robot

Therefore it should be pointless for G or any other big SE to develop any specific mechanisms that look into WP plugins directory and make any assumptions based upon it. They already have mechanisms on the place to detect duplicate content, all you need is just to spin it better. However it is always good idea to restrict access to whole wp-content directory with .htaccess but it does require some tweaking as it may block some plugins and/or themes
 
HTACCESS

AuthName "Restricted Area"
AuthType Basic
AuthUserFile /home/.htpasswd
AuthGroupFile /dev/null
require valid-user

OR

blank index.php in plugins folder

OR

rename wp-robot folder to something else
:D
 
just rename your wp robot to something else
i got some similar to visit tracking

Also robot.txt can stop this right ?
 
humm i dont trust robot.txt
 
to be very honest .. even EZINE is an AUTO BLOG... so is hubpages... goog doesnt give a damn about autoblogs... they just ask you to have meaningful content... content that is not there on millions of other website... ive seen that google allows certain level of duplicacy and that makes perfect sense...

a crappy autoblog can easily be spotted out, however a well built autoblog that adds some value to the net can be successful... and iam saying this from personal experience..
 
LOl this is pointed and well known long back in 2009 itself..
As wicked guy suggested.. These are few tips that put you out of your fear.

And those who implement autoblogs know very well ;)
 
blank index.html? should any directory be browsable?

Options -Indexes

Not a bad idea to rename that folder too, why broadcast you could be autoblogging for any reason? Believe me, it would not be beyond G's operating procedure to check for that...

Also they do not adhere to robot.txt, just a different category...
 
but I can't create real content.. that would involve time. will keep using autoblogger regardless
 
rename the plugin?

I had the same kind of question. A lot of the examples to fix the problem seem plausible, but if you change the name of the folder, you change the file path for the plugin, making it unusable, correct? Am I missing something in oversight here or just being too precautious?
 
Renaming the plugin name will make it not working. Why not you just hide it with htaccess/robot?
 
Back
Top