Merging plugins: the meta-robots WordPress plugin
I've merged a couple of plugins into one plugin, creating the meta-robots plugin. This plugin is able to add all meta robots tags you'd possibly wish to add to pages.
Related posts
- Update of Robots Meta plugin: more duplicate content issues solved
- More WordPress SEO: robots-meta update
- Update to Robots Meta plugin
- Definite guide to robots meta tags
- Update your robots-meta plugin!
Want more WordPress tips?
You should subscribe to my WordPress Newsletter, as you'll get a whole lot more WordPress tips and tricks there! Also, subscribe to this blog right now with RSS, or daily or weekly emails!
Cats: WordPress Tags: SEO, WordPress, WordPress Plugins
Gerben Coumou Aug 22nd, 2007 at 09:16
Joost, this is a very effective plugin: nice work!
Is it possible to add a Noindex, Follow option for Archives (Category, Author and Date pages) as well? In my opinion these pages are just some 'predefined' search queries. Without tweaking them, they generate too much duplicate content anyway.
Furthermore I suggest adding the following lines to any Wordpress’ robots.txt:
Disallow: /wp-admin/
Disallow: /wp-login.php
Disallow: /wp-register.php
Disallow: /*/feed/
Joost de Valk Aug 22nd, 2007 at 20:37
Good idea Gerben, I just added the possibility to noindex the login, register and admin pages, making the first three unnecessary. With the release of WordPress 2.3, the last will be unnecessary as well :)
You'll have to update to version 1.1 :)
George Aug 26th, 2007 at 12:03
Should I actually see a robots.txt file in my blog root folder? I see nothing there.
Also, curious on your thoughts on WordPRess robots.txt files from this post:
http://www.johntp.com/2007/03/29/create-a-robotstxt-file-and-increase-your-search-engine-rankings/
He seems to think much more should be blocked than your plugin allows for.
Joost de Valk Aug 26th, 2007 at 14:07
Hey George: no you shouldn't see a robots.txt, this plugin uses the <meta name="robots" content="noindex"> way of blocking the spiders.
As far as the post you refer to is concerned: I see no reason for blocking wp-content, as all the uploaded files are in there, the plugin allows you to block all the feeds, and in a previous post I explained how to make trackbacks 301 instead of blocking it. And his way of blocking trackback URL's won't work anyway as it should be /*/trackback/ :)
George Aug 26th, 2007 at 20:37
Joost - Thanks for the feedback, and for the plugin. Editing the redirect file now!
Joost de Valk Aug 26th, 2007 at 22:46
My pleasure George :)