Indexing slow? Blame WordPress 2.8
Last night I was complaining that my Servicing Stop post was taking a few minutes longer than normal to get indexed – with such a time sensitive topic it’s critical that Google indexes and ranks the content within a few minutes.
@ducedoon pointed out that it might be because of a new addition to WordPress 2.8 which rather than sending pings when a post is published sends them once per hour in a batch process!
In an attempt to reduce the numbers of outbound pings a new undocumented â€featureâ€ was introduced in WordPress 2.8 (this change is not mentioned in the WP 2.8 release notes).
Instead of notifing ping services every time a post is published or edited, pings are now sent once every hour, at the most. Every time a new post is published, WordPress checks if there is a ping batch queued to be sent within the next hour. If so, the ping is added to that batch. If there is nothing in the queue, a ping is sheduled to be sent after 3600 seconds (one hour).
Apparently this will be fixed in WordPress 2.8.3, until then don’t expect fast indexing or speedy distribution of your RSS feed.
Latest from B3Labs
- Another milestone reached for Branded3 as it’s acquired by the
St Ives Group
- The latest media consumer findings & what they mean for digital marketers
- Talk to Branded3 at @BuyYorkshire in Leeds next week!
Latest from Blogstorm
- Early thoughts on Penguin 2.0
- 5 myths about manual penalty recovery
- Google gets more aggressive with link devaluation