Posts Tagged ‘splogging’

Yaab autoblogging test results

Sunday, December 21st, 2008

And the results are in:

1) Duplication of content: I set up an autoblogger using the BBC news main feed, with an interval of 10 minutes. It published four separate posts, all with identical content. So, Yaab does not check for new content before publishing a new post. To be fair, the author doesn’t claim that it does – but this goes on the wishlist for the future. The perfect autoblogging tool would be something that you could leave alone entirely, without having to make guesstimates about how often the sources were likely to be updated.

2) The SEO Smart Links plugin works fine with Yaab. I have set it to publish only on individual posts and not the main page. I will post separately about this plugin, which is itself a fine piece of work.

3) The plugin worked beautifully with an RSS feed from Flickr, displaying pictures from the feed along with links and credits.

4) Multiple feed URLs worked well: although differently sourced RSS content displays differently. In particular, the content from a Google News RSS feed looks different. This may just be a feature of those feeds, but I think such issues could be ironed out with greater configurability of the data coming in from the feeds, as already suggested by another early adopter in his useful feedback post on Yaab, all of which I would agree with.

5) Adsense content units have gone on to the individual blog posts: they are mostly showing generic ads at present, but there is an advertisement for some sort of Goth/Emo dating site on the aggregated “glam rock” entry, so it seems that Google is picking up the content (as I would have expected). In time I am sure that I’ll see more relevant ads on all pages.

So, pretty impressive so far!

Yaab – next steps

Sunday, December 21st, 2008

As mentioned in a comment to an earlier post, following the author’s advice I have now been able to get the Yaab Autoblogger to work successfully with a Yahoo Pipes feed, by substituting the “feed” prefix with “http”, which is great.

The next thing that is really great is that setting the interval for fetching new content and posting it also works a treat. In my impatience to see it working, I set the timer for only 20 minutes, and it produced another post right on time. 

Now, 20 minutes is probably not the best time to set, unless you are referring to feeds that are updated extremely often! What happened in this instance was that it fetched exactly the same items that it had got 20 minutes earlier, and created an identical post (which I have now deleted to avoid duplication). What would be a really great feature for this plugin would be if it were to check whether there were any new items since the last time it fetched the feed, and only create a post if there were any such items.

However, I should probably test this properly: I made some other changes to the feed (the name of the post in particular) and it may be that it would have handled the duplication better had I not done so. 

So that becomes the first task on my Yaab testing to-do list, which follows:

Testing to-do list

1) Create a new autoblogger on the test blog that updates frequently and let it run without making any other changes; assess how the autoblogger handles non-updated material

2) Install the SEO Smart Links plugin and see whether and how this works with Yaab – the ability to add in my own predefined links on certain words/phrases is a feature that I liked in WP-o-Matic, and has obvious potential SEO benefits. Satheesh mentions this as a future upgrade to his plugin also.

3) Test the plugin with an images RSS feed.

4) Try the plugin with multiple feed URLs

5) Test the output blog posts with Adsense to get some insight into how Google treats the output content

Yaab Autoblogger – first impressions

Sunday, December 21st, 2008

I am probably taking a risk by uploading a plugin recommended to me by the author and downloadable only from their blog, but following an earlier comment on this blog I was moved to install the Yaab Autoblogger plugin.

So far it hasn’t stolen my identity, crashed my computer or created any other kind of unexpected havoc, so while I can’t give any guarantees, so far it looks as though I was right to trust the instinct that told me that Satheesh (the author) was not the malicious type…

Download and extraction was fine, installation was fine, and the plugin works. There are some friendly cartoons in the settings to let you know where you are, and although the language used is a slight variant from the English that I use, I could clearly follow what was going on.

I have to say that the principal inspiration for downloading this plugin to give it a spin was the hope that it might be able to cope with a wider range of RSS feeds than WP-o-Matic, which had trouble with certain feed variants.

Now, I do need to give the major caveats that I am (1) not very patient and (2) not terribly systematic, but what I found was that Yaab gave me feed URL errors with quite a wide range of feeds. The main news feed for the BBC news website - feed://newsrss.bbc.co.uk/rss/newsonline_uk_edition/front_page/rss.xml - produced an error, as did a customised feed from the BBC: feed://newsapi.bbc.co.uk/feeds/search/news+sport/glam%20rock

A particular disappointment was the apparent inability of the plugin to recognise RSS output from Yahoo Pipes, for example feed://pipes.yahoo.com/pipes/pipe.run?_id=ivS59KeM3RGF_9CarbQIDg&_render=rss&textinput1=glam+rock

I did get it to recognise the general feed from the Guardian newspaper:http://www.guardian.co.uk/rssfeed/0,,12,00.xml.

However, I’ll do a little more playing around with it and see what I can come up with! I might even dig around in the code a bit to see if I can work out what is going on in the validation stage.

Causality part II

Sunday, October 19th, 2008

I left it a little longer than a week, during which time I didn’t change any of the blogs, add or edit any posts, or even check the search results.

Today, the home page of the site is back up to #9 for the search term “search experiments”, which makes the previous change look something like the usual non-random churn.

Could it be that the initial dip was some kind of penalty, but the fact that no new splog posts have been published means that the penalty has diminished? It could, but there are a hundred other possible explanations. Beware of jumping to conclusions.

Causality, splogging and speculation

Thursday, October 9th, 2008

Here is a common issue for anyone involved in SEO or Google-watching, and I suppose in many other areas as well.

You take an action X. Event Y follows. You can build a plausible hypothesis for a connection between X and Y. X therefore caused Y.

The SEO version of this goes: you released new feature/code tweak/section on your website. Traffic went up the following week. New feature was a success! 

My latest version of this runs as follows: I experimented with some splogging on another blog (the relationship with this one is not disguised: they are cross-linked and hosted on the same account). I created a number of automatic posts using RSS-generated content about Google, ensuring that every time the word “search” appeared in the posts, it linked to the home page of this site. Before I did this, the home page of this site was #5 or #6 on Google, which it had been for a while. Today it is #20. So it might be very easy to jump to the conclusion that Google has spotted my nefarious tactics, and has penalised my site. 

Is that a reasonable conclusion based on the evidence?

Splogging and search

Sunday, October 5th, 2008

I’ve been experimenting with the Wordpress plugin WP-o-Matic on another blog of late. In combination with the SimplePie plugin, it allows you to automatically post to blogs using RSS feeds. 

The plugin allows you to create campaigns, into which you can place multiple RSS feeds – or just a single one if you prefer. For each campaign, you allocate a category, and the plug-in will post items from the feed as individual blog posts categorised accordingly. 

You can control how often each campaign checks the feed for new items, although I’ve had some teething problems getting this to work exactly as I would like. Ideally, you would want to organise this so that it published stories on a drip-feed basis pretty close to their publication dates, so you want to set the check time at about the same frequency as new items are published.

Incidentally, I’ve also had some difficulty getting the campaigns to refresh. I think it is something to do with being a bit new to cron jobs. More on that later.

So, why would you want to republish someone else’s RSS feeds as if they were your own blog posts? Isn’t this (a) a rather unethical theft of content and (b) unlikely to do you any good for search optimisation, as it will all be duplicate content?

I’ll leave the ethical questions for another time – for now, let’s just remember that the second S in RSS stands for “syndication”.

So, what possible benefits, including SEO benefits, could flow from republishing this material? The idea of each item in an RSS feed being reproduced as a new, individual post is definitely just dupe content spam, right?

Not really. There are all kinds of possible legitimate uses for this. For example, you might want to do some judicious selection of RSS feeds, perhaps filtered automatically as well, and combine them so that your particular blog carried every story that you thought was going to be of interest to your audience. Provided that the posts have links to the original story, your users could be reading the truncated RSS summary in your blog and then deciding whether to go to the full post.

Another possibility is that you effectively own the RSS feed – for example, it could be something like your del.icio.us feed, which you wanted to turn into a linkblog without doing any more work, but creating a post for each one.

However, from an SEO point of view there are some further uses.

First, although the posts themselves will not be unique, the permutation of them may well be, so that your main page – and in particular your category pages – can contain themed content in a combination that is not to be found elsewhere on the web. If reasonably well-linked, these pages could have a chance of ranking for those terms.

Second, there is a very nice feature in the plug-in that allows you to process the feeds as they come in using a search and replace function.

This is separated into two functions for ease of use: the first is a simple word-swap. The example that the author gives is that you could have the plugin search for “ass” and replace it with “butt”. Incidentally, this kind of auto-bowdlerisation is a risky business – witness the embarrassment of the right-wing Christian site that decided that “gay” was too euphemistic (and happy-sounding) for them, and then ended up publishing a number of stories about the Olypmic sprinter “Tyson Homosexual”.

The second element enables you to automatically place links behind certain specified words/phrases. This is obviously pretty powerful for building lots of links with the right anchor text, quite quickly.

I’m not sure whether the two would work together – I will give it a go – but on the assumption that they do, it would be possible to pick a news feed filtered on say, Barack Obama, and republish all of those stories with the words “digital cameras” automatically replacing “Barack Obama”, and linking to your digital cameras site. You might even avoid some of the duplicate-spotting in this way…

Warning: very much of any of this kind of stuff is pretty likely to get your site banned by Google.