Everyone Is Talking About @Wpbeginner Collapse  🔗 **Source:** [Everyone Is Talking About @Wpbeginner Collapse](https://twitter.com/aeljaouari/status/2069734418567024867/?rw_tt_thread=True) > [!note]+ Document Notes > --- > tags: [wordpress-seo, eeat, content-decay, content-pruning, google-algorithm, wpbeginner] > author: Ahmed EL JAOUARI > source: Twitter/X > reference: https://twitter.com/aeljaouari/status/2069734418567024867/?rw_tt_thread=True > date created: 2026-06-26 00:00 > --- > # 🏷️ Title: Everyone is talking about @wpbeginner collapse > ## 🧭 Table of Contents > - [📝 Summary](#-summary) > - [📖 Main Content](#-main-content) > - [🗒️ Notes](#️-notes) > - [📚 References](#-references) > - [🗣️ Paraphrase](#️-paraphrase) > - [📰 Newsletter](#-newsletter) > - [✅ Action Items](#-action-items) > - [🧪 Hypotheses](#-hypotheses) > - [📊 Methodology](#-methodology) > - [❓ Questions](#-questions) > - [🔮 Future Research](#-future-research) > - [💡 Implications](#-implications) > - [🧠 Learning Styles Assessment](#-learning-styles-assessment) > - [📊 Accessibility Assessment](#-accessibility-assessment) > - [🌍 DEIB Assessment](#-deib-assessment) > - [✅ Logical Validity](#-logical-validity) > - [🛡️ DARVO Analysis](#-darvo-analysis) > - [🎯 Conclusion](#-conclusion) > ### 🔗 References > - [WPBeginner](https://www.wpbeginner.com/) — the site under discussion. > - [Original thread by Ahmed EL JAOUARI](https://twitter.com/aeljaouari/status/2069734418567024867/?rw_tt_thread=True) > - EEATClean — the author's own scanning tool (the product this thread promotes). > ## 📝 Summary > - What happened: WPBeginner's organic search traffic reportedly fell from 2.6M monthly clicks to 27K, roughly a 99% drop. A YouTube creator (@edwardeachday) framed the cause as over-promotion. The author disagrees and ran 30 of WPBeginner's 3,000+ articles through his tool, EEATClean. > - Why it matters: It's a high-profile case in the WordPress and SEO worlds about how Google's helpful-content and EEAT signals treat aging tutorial content. The lesson generalizes to any long-lived docs/tutorial site. > - Key stakeholders: WPBeginner (Awesome Motive), SEO practitioners, WordPress tutorial publishers, and Google's ranking systems. The author is also a stakeholder — he sells the diagnostic tool. > - Risks and tradeoffs: The thread's central claim (outdated content, not promotion, drove the collapse) is plausible but unproven from a 30-article sample. The thread is promotional, so the framing conveniently points at the exact problem his product detects. > - Bottom line: Outdated tutorials probably contributed to the decline, and content decay is a real, under-discussed risk — but a 30-of-3,000 sample plus a sales pitch isn't proof that decay, not promotion, was "the real killer." > ## 📖 Main Content > - The core argument is a reframing. Where popular commentary blames WPBeginner's drop on aggressive self-promotion (ranking their own plugins #1, "fluff," too-promotional content), the author argues the bigger, less visible cause is content decay: thousands of tutorials describing deprecated functions, end-of-life WordPress versions, and steps that no longer match how WordPress works. > - The evidence is a sample scan. He ran 30 of 3,000+ articles through EEATClean. His reported verdict: 29 of 30 hurting the site, 24 candidates for deletion, 5 needing serious updates, 1 worth keeping. He then extrapolates to the full library. > - Two named examples carry the argument. (1) A 2012 post, "WordPress 3.3.1 – Security Update, Upgrade Now," still live and indexed in 2026, still telling readers to install an ancient version, with no archive notice, no outdated disclaimer, and no noindex — scored 12/100, risk 8/10. (2) A tutorial built on `get_currentuserinfo()`, a function deprecated in 2016, so the code no longer works. > - The mechanism he proposes: a tutorial site lives or dies on whether the information is accurate today. When readers follow broken steps, trust breaks and they bounce. Google reads those negative engagement signals across thousands of pages, and old indexed pages act as a current signal that the site's expertise has expired. > - Contested claims to flag: the 99% figure and traffic numbers are stated, not sourced in the thread. The causal claim ("the real killer was invisible") rests on a small, possibly non-random sample and on the author's own scoring system, which isn't described. "Self-promotion in small doses is survivable" is asserted, not demonstrated. The two failure modes (promotion and decay) aren't mutually exclusive; both can be true at once. > - Term notes: *EEAT* = Experience, Expertise, Authoritativeness, Trustworthiness, Google's quality-rater framework. *Content decay* = the gradual loss of accuracy/relevance/traffic as content ages. *noindex* = a directive telling search engines not to index a page. *Deprecated function* = code kept for backward compatibility but slated for removal and discouraged from use. > ### 🗒️ Notes > - The headline stat: 2.6M → 27K monthly clicks, framed as a "99% wipeout." > - The foil: @edwardeachday's YouTube video blaming "too promotional," "too much fluff," "they ranked their own plugins #1 everywhere." > - The pivot: "I don't think that's the full story." The author runs EEATClean on 30 articles. > - Sample verdict: 29 hurting, 24 delete, 5 serious updates, 1 keep. Extrapolation: "Imagine what the other 3,000 look like." > - Example 1 — the 2012 WordPress 3.3.1 security post: still live in 2026, fully indexed, no archive/outdated/noindex signal. Score 12/100, risk 8/10. Reads as a "current signal of the site's expertise." > - Example 2 — `get_currentuserinfo()` tutorial: function deprecated in 2016, so the code doesn't run. > - The thesis statement: "A WordPress tutorial site lives or dies on one thing: Is the information still accurate today?" > - The trust-and-bounce mechanism: broken tutorial → broken trust → bounce → Google reads those signals across thousands of pages. > - The closing pitch: EEATClean "scans every article" and shows what's outdated, what needs fixing, what to remove, what to add. > - The slogan: "Every outdated tutorial tells Google your expertise expired." > - Promotional tell: the thread is structured as a problem the author's product uniquely solves. Treat the diagnosis as motivated. > ## 📚 References > - [WPBeginner](https://www.wpbeginner.com/) > - [Original thread](https://twitter.com/aeljaouari/status/2069734418567024867/?rw_tt_thread=True) > - [Google Search Central — Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) > - [WordPress code reference — `get_currentuserinfo()` (deprecated)](https://developer.wordpress.org/reference/functions/get_currentuserinfo/) > ## 🗣️ Paraphrase > - The crowd blames WPBeginner's traffic crash on heavy self-promotion. The author thinks that's only part of the picture and points instead at a decade of tutorials quietly going stale. > - He scanned a small slice of the site (30 of 3,000+ articles) and found almost all of them hurting performance, with most fit for deletion. He uses a couple of vivid examples — a 2012 security post still telling people to install an ancient WordPress, and a tutorial built on a function killed off in 2016 — to argue that inaccurate content erodes reader trust and, through engagement signals, Google's read of the site's expertise. Then he points you to his tool that finds all of it. > ## 📰 Newsletter > WPBeginner reportedly went from 2.6M to 27K monthly clicks — and the internet immediately reached for the obvious villain: too many "rank our own plugin #1" plays. Ahmed EL JAOUARI says hold on, check the basement: a 2012 post still cheerfully telling readers to "upgrade now" to WordPress 3.3.1, live and indexed in 2026, plus tutorials built on functions that died in 2016. His take: a tutorial site lives or dies on whether the steps still work today, and a decade of quietly decaying pages tells Google your expertise expired. Fair warning — it's a pitch for his scanner, EEATClean, so weigh the diagnosis against the sales motive. But the underlying lesson is free and real: if you run docs or tutorials, schedule a content-freshness audit, noindex or redirect the genuinely dead pages, and stop letting 14-year-old security advice represent your brand. Thread: https://twitter.com/aeljaouari/status/2069734418567024867/?rw_tt_thread=True > ## ✅ Action Items > #### DevRel > - Developer advocacy: turn this into a Everyone is talking about [@wpbeginner](https://twitter.com/wpbeginner) collapse. 2.6M monthly clicks down to 27K. A 99% wipeout. In a recent YouTube video, [@edwardeachday](https://twitter.com/edwardeachday) pointed to what many people are blaming: “Too promotional.” “Too much fluff.” “They ranked their own plugins #1 everywhere.” I don’t think that’s the full story. So I ran WPBeginner through EEATClean. I scanned only 30 articles out of their 3,000+. The result? 29 were hurting the site. 24 should probably be deleted. 5 needed serious updates. Only 1 was worth keeping. And if 30 random articles look like that… Imagine what the other 3,000 look like. The real problem may not be promotion. It may be outdated information. And the data is brutal 👇 Example 1: “WordPress 3.3.1 – Security Update, Upgrade Now.” Published in 2012. Still live in 2026. Still telling readers to install a WordPress version that is now ancient and full of security risks. Score: 12/100. Risk: 8/10. And here’s the kicker: No archive notice. No “this is outdated” disclaimer. No noindex. It’s still fully indexed and presented like fresh, valid content. So Google may read it as a current signal of the site’s expertise. Example 2: A tutorial about getting logged-in user information. The whole tutorial is built around get\_currentuserinfo(). That function was deprecated back in 2016. So the code simply doesn’t work anymore. Here’s the real story: A WordPress tutorial site lives or dies on one thing: Is the information still accurate today? WordPress moves fast. Functions get deprecated. Versions become security risks. Methods break. Interfaces change. WPBeginner built thousands of tutorials over more than a decade. But a huge share of those tutorials now describe dead code, risky versions, and steps that no longer match reality. When a reader follows a tutorial and it doesn’t work, trust breaks. They bounce. Google reads those signals across thousands of pages. Self-promotion in small doses is survivable. A decade of decaying tutorials is not. Everyone focused on the plugins because they are visible. But the real killer was invisible: Thousands of pages quietly going out of date. Still indexed. Still ranking. Still treated as current. I scanned just 30 articles with EEATClean. It scans every article and shows exactly: What’s outdated. What needs fixing. What should be removed. What needs to be added. Because old content isn’t neutral. Every outdated tutorial tells Google your expertise expired. Your browser does not support the video tag., Everyone Is Talking About @Wpbeginner Collapse, Ahmed EL JAOUARI, 01kvykp7axm9ebpaxxt2vfetf2.