Editor’s note (March 2026): This article is part of Blog Herald’s editorial archive. Originally published in 2009, it has been reviewed and updated to ensure accuracy and relevance for today’s readers.
Back in 2009, we talked about a quiet change inside WordPress that most users never noticed — until they did. WordPress had switched its update pinging behavior from per-post to hourly, throttling how often a site could notify services like Ping-O-Matic about new content.
It was a reasonable technical decision. The problem wasn’t the decision itself. The problem was that nobody told anyone.
No announcement. No changelog entry that surfaced to ordinary users. No explanation in the dashboard. Bloggers noticed something felt off, started digging, and eventually pieced it together themselves. For a platform that had built its reputation on community trust and open-source goodness, it was a strange way to operate.
That moment was small in the grand scheme of things. But it planted a seed of a question that would only grow louder over the next decade and a half: who does WordPress actually answer to?
What pinging actually does — and why it mattered
To understand why that 2009 change frustrated people, it helps to understand what WordPress pinging was for. When you published a post, WordPress would fire off an XML-RPC notification to update services — most notably Ping-O-Matic — which would then relay the signal to search engines and blog directories. It was the web’s way of saying: something new is here, come look.
WordPress’s own documentation describes the system plainly: update services “process the ping and update their proprietary indices with your update.” For early bloggers, this was genuine infrastructure. Getting indexed quickly mattered for traffic, for community, for feeling like your words were reaching people.
The switch to hourly pinging was, technically, a spam-prevention measure. Sites that constantly re-saved posts were flooding ping services with noise. Throttling made sense. But bloggers who relied on rapid indexing — particularly news-adjacent content creators — were quietly disadvantaged without any explanation of why their reach had seemingly shifted.
That’s not a technical failure. That’s a communication failure. And the distinction matters enormously.
The pattern that never really went away
It would be satisfying to say that WordPress learned from that moment. That a small controversy over pinging in the summer of 2009 led to a more transparent, communicative platform. In some ways, it did. WordPress has become considerably more deliberate about publishing release notes, developer updates, and roadmap posts through make.wordpress.org.
But the underlying tension — between the platform’s power and its accountability to the people who depend on it — didn’t go away. It just waited for a bigger stage.
In 2024, that stage arrived. What started as a public disagreement between Automattic CEO Matt Mullenweg and WP Engine over trademark usage escalated into something the WordPress community had never seen before. WordPress.org blocked WP Engine from accessing plugin and theme updates, effectively leaving millions of websites potentially exposed. Automattic then took control of the Advanced Custom Fields plugin — one of the most widely used tools in the entire ecosystem — and pushed updates to its millions of users without their explicit consent.
What started in 2024 as a disagreement over brand usage escalated into lawsuits and community-wide implications. Over 150 Automattic employees resigned. Long-term contributors found their accounts blocked. The community that had given WordPress its soul was treated, as one observer put it, like cannon fodder.
The ping throttling of 2009 and the WP Engine crisis of 2024 are not the same kind of event. But they rhyme. Both involved consequential decisions made about infrastructure that millions of people depend on, without adequate transparency or community dialogue. The scale was different. The lesson was the same.
What bloggers and creators actually need from platforms
There’s a tendency in our industry to frame platform decisions as purely technical or purely commercial. The engineers needed to prevent spam, so they throttled pings. The lawyers needed to defend a trademark, so they escalated. These framings aren’t wrong — they’re just incomplete.
What gets left out is the human layer. The bloggers who built their readership using tools they trusted to behave predictably. The developers who contributed years of work to an ecosystem they believed in. The agencies whose entire client businesses ran on a platform they now couldn’t fully trust.
Platform decisions are community decisions. And communities don’t just need good outcomes — they need to be part of the process that produces them.
This isn’t idealism. It’s practical. When WordPress quietly changed its pinging behavior in 2009, the backlash was modest but real. When Automattic made sweeping moves in 2024 without genuine community consultation, the discontent was particularly noticeable among long-term contributors who once believed that WordPress was built on collaboration and transparency. Trust, once eroded, doesn’t restore on a software update schedule.
For content creators, the lesson is about diversification and vigilance — not paranoia, but realism. Understanding how your publishing infrastructure works, what dependencies you have, and how platform decisions affect your reach is no longer optional knowledge. It’s part of being a serious digital publisher.
The pinging question in 2025 and beyond
The technical landscape around pinging has also shifted considerably since 2009. Many of the original ping services that WordPress users relied on are now defunct or returning invalid responses. Testing has shown that of the extended ping lists that circulated for years, only a handful of endpoints still provide valid responses — and loading your WordPress installation with dozens of dead URLs only slows your site down without any indexing benefit.
Today, Google and other major search engines are far more sophisticated at discovering and indexing new content than they were when Ping-O-Matic was a meaningful lever. Search Console, sitemaps, and internal linking strategies have largely displaced pinging as the primary mechanism for rapid indexing. The hourly throttle that caused so much frustration in 2009 is, in practice, a non-issue for most modern publishers.
But that evolution didn’t happen by announcement either. It happened gradually, and bloggers who didn’t keep up were left optimizing for infrastructure that had long since moved on.
What this history is really asking of us
There’s a through-line in all of this that I think deserves to be named directly: the relationship between creators and the platforms they publish on has always been unequal, and pretending otherwise leads to poor decisions.
WordPress — for all its genuine contributions to democratizing publishing — is not a neutral utility. It is software maintained by people with interests, financial pressures, and blind spots. That was true in 2009 when an engineer made a pinging decision without thinking about the communication implications. It was true in 2024 when a legal dispute became a community crisis. It will be true in whatever form the next controversy takes.
None of this means WordPress isn’t worth building on. It almost certainly still is, for most publishers. What it means is that the posture of a serious content creator can’t be passive dependence. You have to understand your tools, follow platform developments, maintain optionality where you can, and treat your publishing infrastructure the way you treat any other critical business dependency: with clear eyes.
The 2009 pinging story was a small thing. The fact that its central question — does this platform respect the people who depend on it? — is still being asked today tells you everything about why it’s worth remembering.
