2 Comments


  1. If you use Feedburner, as I wrote about recently, they do their own intelligent filtering based upon what has changed within a document.
    Exactly how that works is hard to determine, but combine that with their eventual full database of ping services, and you have a killer combination whereby services can potentially specify ping intervals.

  2. dg

    I use posts differently on some of my blogs, in a way that depends on frequent numerous edits. I open the post “live to the public” at the start of a real-time event. I add to the post continually, repeatedly, for the next 2-6 hours. It could be 20, 50, 100 edits. After the 6 hours the post is basically complete. If the readers visit the blog live during the event they will see the latest updates in the post, and can refresh for by-the-minute changes. If the readers visit the blog the next day (or anytime later), then the post is a complete permanent archive of the event. In my case the event is radio playlist of songs and announcements, but I could imagine others doing the same technique for reporting on a race, sports, or game. Anything where there is an opening-announcement which is later edited to include realtime statistics, and eventually finalized into a permanent record. For SEO purposes, it seems advantageous to maintain the flow of all that related content in the same post, same permalink.

    That’s why I always have turned off Ping-O-Matic on that kind of WordPress install. Don’t know if that is the correct decision. I feel it would be best for this site to Ping the first time I post it, and maybe Ping again on the next day when the post is finalized, but certainly not ping for each of 20+ edits in the span of 6 hours. Any advice of the best approach for my set up?

Comments are closed.