Updated SEO Siloing WordPress Plugin
The SEO Siloing WordPress plugin I released yesterday has been updated to version 1.1. The main updates are:
- Better category matching — the plugin now tries to match both the “human readable” name and the category slug to find the right category ID.
- Failing that, you can now explicitly specify the desired category you want used by name or by ID using this syntax:
<!-- seosiloing-category-posts#general -->
This will list the posts of the 'general' category. If you use a number, it assumes the number is the category ID.
- The plugin can be used on non-pages. In other words, you can include lists of category posts on pretty much any post/page in the blog.
- Two customizable messages for situations when the category has no posts or when the category is invalid.
- Special debugging mode that lets you see what the plugin is doing to your page, just insert the sequence <!– seosiloing-debug –> somewhere near the top of the page.
Watch this space, I'm going to use this plugin to convert my debt-free living site into a siloed WordPress blog as I described in SEO Siloing and AdSense.
Sponsored Link: Learn more about the ins and outs of
AdSense by reading Uncommon AdSense, my latest book about AdSense.
Eric Giguere is the author of Uncommon AdSense and the award-nominated (that just means it lost!) blog Make Easy Money with Google and AdSense.
Tags
Comments
3 Responses to “Updated SEO Siloing WordPress Plugin”
Hi Eric
I am using v1.1 but I seem to have hit a stumbling block.
I have a category called asian babes.
I created a page called asian babes and added the html comment however I get an error saying
There is no matching category for ‘asian-babes’
I then tried a different category called blonde babes and a page called blonde babes and I still get the same error
any ideas?
all the slugs are hyphenated
Try using the category ID instead, then. Go to your list of categories and write down the number for one of the categories. Go back to the category page and add the category ID to the HTML comment as shown above in this post.
works like a charm!