Everyone Is Talking About @Wpbeginner Collapse ![rw-book-cover](https://pbs.twimg.com/profile_images/1610447205785010176/vlmkx97J.jpg) 🔗 **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 > <!-- deep-read:sections start --> ## 🧭 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 talk on content decay vs. content volume — show the WPBeginner pattern with before/after rank data. - Education: run a workshop on auditing deprecated-function tutorials and writing version-stamped docs. - Developer experience: ship a docs template with a "last verified" date and a tested-against-version field. - Developer marketing: write a measured response post — useful audit advice, not tool hype. - Community management: open a survey asking which official tutorials readers found broken or out of date. - Internal/external/cross-project: align docs teams on a freshness SLA and a deprecation-sweep cadence. #### OSPO - Policy & Governance: set a content-lifecycle policy (review/retire dates) for project-owned tutorials. - License Compliance: not applicable to this source — no licensing claims raised. - Security Management: flag and retire docs that recommend end-of-life versions (e.g., the 3.3.1 example). - Software Inventory: track which docs reference which API versions so deprecations trigger doc reviews. - Developer Support: add "is this doc current?" feedback widgets with triage ownership. - Community Engagement: coordinate with downstream sites republishing stale tutorials. - Strategic Alignment: report a "docs freshness" KPI alongside traffic. #### Community - Maintainers: add a release-time checklist item — flag docs touching newly deprecated functions. - Contributors: create a "first issue" rotation for verifying and date-stamping old tutorials. - Sponsors: fund a content-freshness audit sprint with milestone reporting. - Ecosystem: run a coordinated sweep across project docs for end-of-life version advice. #### WordPress - Core: triage Codex/handbook references to deprecated functions like `get_currentuserinfo()`. - Core Performance: not directly applicable — this is content quality, not runtime perf. - Core AI: pilot an AI freshness scanner that flags deprecated-API references in docs. - **Core Program Team:** add a recurring docs-decay review to release retrospectives. - Mobile: audit in-app help links pointing at stale tutorials. - Playground: build a reproducible demo showing the deprecated-function failure. - Community: add "keep your meetup content current" guidance to organizer kits. - Training: refresh Learn.WordPress lessons that reference removed functions. - Marketing: avoid alarmist "Google penalty" framing; teach freshness as routine hygiene. - Support: map forum questions caused by following outdated third-party tutorials. - Design: design a clear "this content is outdated" UI pattern for archived docs. - Documentation: add visible version stamps and a deprecation banner pattern to DevHub/HelpHub. - Photos: not applicable to this source. - TV: caption and tag any talks on content lifecycle and EEAT. - Polyglots: ensure translated tutorials inherit the same outdated/archive notices. - Accessibility: ensure outdated-content banners meet contrast and screen-reader needs. - Meta: expose "last reviewed" metadata in the docs platform. - CLI: not applicable to this source. - Hosting: not applicable to this source. - Tide: explore scoring plugins' bundled docs for deprecated-API references. - Openverse: not applicable to this source. - Themes: not applicable to this source. - Plugins: nudge plugin authors to retire readme tutorials referencing removed hooks. #### The WPCC - Programs: fund a maintainer stipend for a docs-freshness audit track. - Projects: run a documentation sprint to retire or update end-of-life tutorials. - Funding experiments: milestone payouts tied to verified-current doc counts. ### FAIR - Technical independence: store doc provenance and last-verified metadata locally, not just in a CMS field. - Policies and covenants: adopt a sunset clause for unmaintained tutorials. - Productized governance artifacts: publish a content-lifecycle scorecard template. ## 🧪 Hypotheses - H1: Sites with a high share of tutorials referencing deprecated/removed APIs lost more organic traffic in recent Google updates than sites with current content, holding promotion constant. - H2: Adding visible "last verified" dates and noindexing dead pages improves sitewide rankings within two algorithm cycles. - H3: Over-promotion and content decay are independently associated with traffic loss; neither fully explains the other. - H4: Reader bounce/pogo-stick rates are higher on tutorials whose code no longer runs, and these signals correlate with ranking declines. - H5: A 30-article sample materially overstates or understates sitewide decay versus a stratified sample by publish year. ## 📊 Methodology - To test H1/H3: assemble a cohort of tutorial sites, classify each page for deprecated-API references and for promotional density, then regress traffic change on both factors with controls (niche, domain age, backlink profile). - To test H2: run a controlled cleanup experiment — randomize stale pages into update/noindex/leave-alone arms and compare rank trajectories. - To test H4: pair analytics engagement metrics (bounce, dwell, scroll) with code-validity checks per page. - To test H5: draw a stratified random sample by publish year and compare its decay distribution to the author's 30-article convenience sample. - Data sources: Search Console/third-party rank data, server logs, the WordPress deprecation timeline, and automated code-execution checks against current WP versions. ### ❓ Questions - Were the 30 articles randomly selected or chosen to make the point? - What exactly does EEATClean's 0–100 score measure, and is it validated against ranking outcomes? - How much of WPBeginner's drop is promotion, how much decay, and how much a broader algorithm shift hitting affiliate-heavy sites? - Did other large, non-promotional tutorial sites with stale content drop at the same time? - Would updating (not deleting) the worst pages recover traffic, or is deletion necessary? ### 🔮 Future Research - A public, reproducible dataset linking per-page freshness to ranking changes across many sites. - Comparative study of "prune vs. update vs. noindex" strategies on decayed content. - Whether Google's systems actually treat old, accurate-at-the-time posts as negative expertise signals, or only penalize live inaccuracies. - Interaction effects between affiliate/promotional density and content age. ### 💡 Implications - Practice: tutorial publishers need a standing freshness audit, version stamps, and a retire/redirect policy — not just new-content pipelines. - Policy: docs governance should define content lifecycles, not only style and accuracy at publish time. - Security: live posts recommending end-of-life software are a real user-safety problem, beyond SEO. - Education: teach writers to date-stamp and re-verify, and to mark deprecated content visibly. - Funding models: "keep content current" is unglamorous and under-funded relative to producing new content; this case is an argument for maintenance budgets. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch–Kincaid Grade ~6–7. Short, punchy lines, common vocabulary, one-sentence paragraphs. Flesch Reading Ease likely in the 70s (fairly easy). #### 👀 Visual learners - Present: references a video; describes scores (12/100, risk 8/10) but shows no charts. - Improve: add a before/after traffic chart, a sample-verdict bar (29/24/5/1), and a screenshot of the stale 2012 page. #### 🔊 Aural learners - Present: cites a YouTube video as the foil; no audio of this thread. - Improve: a 2-minute audio summary or narrated walkthrough of the two examples. #### 🗣️ Verbal learners - Present: clear analogies ("lives or dies"), concrete examples, defined stakes. - Improve: define EEAT and "content decay" inline for non-SEO readers. #### 🧩 Kinesthetic learners - Present: implies a hands-on audit but provides no steps. - Improve: a checklist readers can run on their own site (find deprecated functions, check index status, decide update/retire). #### 🧠 Logical learners - Present: a claim-evidence-extrapolation structure; numbers given. - Improve: show the sampling method and a causal diagram separating promotion from decay. #### 🧑‍🤝‍🧑 Social learners - Present: engages an ongoing public debate, names another creator. - Improve: invite replies with readers' own audit results; host a Q&A. #### 🧘‍♀️ Solitary learners - Present: self-contained argument readers can mull alone. - Improve: add reflection prompts ("which of your pages recommend dead versions?"). #### 🌿 Naturalistic learners - Present: implicit lifecycle/decay framing ("decaying tutorials," "going out of date"). - Improve: make the content-lifecycle metaphor explicit — plant, tend, prune, compost. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: plain text thread; no headings or landmarks (platform-limited). - Improve: when republished, use real heading structure and descriptive alt text for the example screenshots. (WCAG 1.3.1) #### Keyboard navigation - Present: not applicable to a text thread; depends on X's UI. - Improve: any republished version should have visible focus and logical order. (WCAG 2.4.7, 2.4.3) #### Contrast and readability - Present: inherits X's theme contrast. - Improve: republish with 4.5:1 minimum body text. (WCAG 1.4.3) #### Text resizing and reflow - Present: short lines reflow well. - Improve: ensure no clipping at 200% zoom in any republished layout. (WCAG 1.4.4, 1.4.10) #### Media and captions - Present: the thread ends with an unsupported `<video>` tag ("Your browser does not support the video tag") and no transcript or captions. - Improve: provide captions, a transcript, and no autoplay for any embedded clip. (WCAG 1.2.2, 1.2.1) #### Forms and interactions - Present: not applicable — no forms in the thread. - Improve: the linked EEATClean tool should have labeled inputs and accessible errors. (WCAG 3.3.2, 4.1.2) #### Standards reference - Primary gaps map to WCAG 2.2 AA: 1.2.1/1.2.2 (the captionless video), 1.1.1 (missing alt text for the cited examples), 1.4.3 (contrast on republish). ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-only, US/Western SEO context. - Improve: note that the freshness lesson applies across locales; link translated audit guidance. #### Inclusive language - Present: neutral, no exclusionary terms; some jargon (EEAT, noindex, deprecated) undefined. - Improve: add plain-language glosses so non-specialists aren't shut out. #### Neurodiversity support - Present: chunked, predictable one-idea-per-line structure — friendly to many readers. - Improve: add headings/sections if republished as an article. #### Representation - Present: minimal — names two creators, no broader voices. - Improve: cite multiple practitioners and counter-views, not just the author's tool. #### Psychological safety - Present: critiques a site's content, not individuals; tone is mostly analytical. - Improve: avoid implying WPBeginner's team is incompetent; frame decay as a systemic maintenance gap. ### ✅ Logical Validity #### Strong reasoning - Causal mechanism (lines on trust/bounce): the chain "broken tutorial → broken trust → bounce → negative sitewide signal" is a coherent, testable causal story. Strong because it names an observable mechanism; clarify by citing engagement data. - Concrete disconfirming-by-example reasoning (Examples 1 and 2): specific, checkable cases (a 2012 post; a 2016-deprecated function) are good inductive support that decay exists on the site. Strong as existence proof; weak as proof of magnitude. - Analogical framing ("lives or dies on one thing: is the information still accurate today"): a clear, apt analogy for tutorial content specifically. #### Fallacies - Hasty generalization — "I scanned only 30 articles out of their 3,000+ … Imagine what the other 3,000 look like" (lines 15–22). Weakness: extrapolates from a small, possibly non-random sample to 100x the content. Fix: stratified random sample by year and disclose selection method. - False dilemma / suppressed correlation — "The real problem may not be promotion. It may be outdated information" (lines 23–24) and "the real killer was invisible" (line 60). Weakness: frames promotion vs. decay as either/or when both can act together, alongside a broader algorithm shift. Fix: model them as joint, not competing, causes. - Single cause (causal oversimplification) — attributing a 99% drop primarily to decay ignores affiliate-site-wide updates, link profile, and SERP changes. Fix: control for confounders. - Appeal to (self-interested) authority / conflict of interest — the diagnosis is delivered by the seller of the tool that detects exactly this problem (lines 14, 65–70). Weakness: motivated reasoning; the framing favors the product. Fix: independent replication with a disclosed scoring rubric. - Unsourced statistics — the 2.6M→27K and "99%" figures (lines 7–8) are stated without a citation in the thread. Fix: link the rank-tracking source. - Anecdotal evidence — two cherry-picked examples stand in for thousands of pages. Fix: report the full distribution, not just the worst cases. #### Tone of voice - Confident, punchy, contrarian-explainer with a marketing close. Examples: "I don't think that's the full story," "the data is brutal 👇," and the slogan "Every outdated tutorial tells Google your expertise expired." Reads as authoritative and a little alarmist, engineered for engagement and a soft product pitch. ### 🛡️ DARVO Analysis - Deny: minor — the author denies the prevailing explanation ("I don't think that's the full story"), but this is ordinary disagreement, not denial of wrongdoing. - Attack: mild — implicitly critiques the popular take and WPBeginner's content quality; not a personal attack on the accusers. - Reverse victim/offender: not present. No attempt to recast an accused party as the victim. The thread is a competing causal claim plus a sales pitch, not a DARVO maneuver. Not applicable beyond the noted mild deny/attack rhetoric. ## 🎯 Conclusion - Bottom line: Content decay is a real and under-managed risk for long-lived tutorial sites, and the two examples are damning on their own. But the thread overreaches when it crowns decay "the real killer" on the strength of 30 hand-scanned pages delivered alongside a pitch for the tool that scores them. Promotion, decay, and a broader algorithm shift can all be true together. - Next steps for readers: audit your own docs for deprecated-function references and end-of-life version advice, add visible "last verified" dates, and decide update/redirect/noindex per page. Treat vendor-supplied diagnoses as hypotheses to verify, not verdicts — and demand a disclosed, validated scoring method before trusting any freshness score. ## 🔄 Refactor Appendix — Everyone is talking about @wpbeginner collapse > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. ### 📚 Literature Atoms (H3) #### [H1] Outdated tutorials, not just promotion, may sink rankings > [!quote] ID:rw_h1 > The real problem may not be promotion. It may be outdated information. **Context & use**: - Thread lines 23–24, the pivot from the popular "too promotional" take. - Reframes a famous traffic collapse around content decay — the core, debatable thesis. **Tags**: #xref #articleseed **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H2] A small sample is extrapolated to the whole library > [!quote] ID:rw_h2 > I scanned only 30 articles out of their 3,000+. The result? 29 were hurting the site. **Context & use**: - Thread lines 15–17. - The central evidence and the central weakness — a convenience sample stretched 100x. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H3] Stale tutorials signal expired expertise to Google > [!quote] ID:rw_h3 > Every outdated tutorial tells Google your expertise expired. **Context & use**: - Thread line 72, the closing slogan and the product's value claim. - Captures the proposed EEAT mechanism; aphoristic and quotable. **Tags**: #xref #aphorisms **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H4] Live 2012 security post still recommends an ancient version > [!quote] ID:rw_h4 > Published in 2012. Still live in 2026. Still telling readers to install a WordPress version that is now ancient and full of security risks. **Context & use**: - Thread lines 28–30, Example 1. - The strongest single piece of evidence — a concrete, checkable safety-and-SEO failure. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H5] A tutorial built on a 2016-deprecated function no longer runs > [!quote] ID:rw_h5 > That function was deprecated back in 2016. So the code simply doesn't work anymore. **Context & use**: - Thread lines 42–43, Example 2 (`get_currentuserinfo()`). - Shows decay as broken code, not just stale prose — a trust-breaking reader experience. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Unmaintained tutorial content is an SEO and safety liability **Claim** (one sentence, Courtney's voice): A long-lived tutorial site carries hidden risk when old pages stay indexed while their advice goes stale, because inaccurate live content erodes both reader trust and search-engine trust. **Evidence pointer**: [[#H1]] and [[#H4]] **Scope & conditions**: Holds for high-volume how-to/docs sites in fast-moving tech niches; weaker for evergreen or low-volume topics. Breaks if Google judges historical-but-clearly-dated content neutrally rather than as a current signal. **Links**: - [[Content decay]] — because extends - [[EEAT signals]] — because applies-in SEO ranking - [[Vendor-motivated diagnosis]] — because contrasts on evidentiary reliability <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Verify the WPBeginner 2.6M→27K figure against an independent rank tracker before citing it. — thread lines 7–8 #fleeting #inbox - [F2] Check whether `get_currentuserinfo()` is still referenced in any Learn.WordPress or DevHub material. — thread line 41 #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Draft a measured "content decay vs. content volume" post using the WPBeginner case, with the conflict-of-interest caveat — #things - [ ] Build a docs-freshness audit checklist (deprecated functions, index status, update/retire decision) — #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Tweets/Everyone Is Talking About @Wpbeginner Collapse.md|Everyone Is Talking About @Wpbeginner Collapse by Ahmed EL JAOUARI]] ## Highlights - 29 were hurting the site. ([View Highlight](https://read.readwise.io/read/01kw3dsgxmcfk7zth9q7krsqh0)) - Note: The headline stat — 29 of 30 sampled articles were hurting the site (note: self-reported via the author's own EEATClean tool; small sample). - Tags: atom/literature/h2 - The real problem may not be promotion. ([View Highlight](https://read.readwise.io/read/01kw3dsdtt5vvarmg4jhx9x2ss)) - Note: Thesis: the wpbeginner collapse may be driven by outdated content, not just over-promotion. - Tags: atom/literature/h1 - It may be outdated information. ([View Highlight](https://read.readwise.io/read/01kw3dsf2mh7p8erbjbsgrvp9b)) - Note: The completing claim — content decay as the root cause of the traffic wipeout. - Tags: atom/literature/h1 - That function was deprecated back in 2016. ([View Highlight](https://read.readwise.io/read/01kw3dsm2qvcc3nn1wyct83e6c)) - Note: Concrete decay example: tutorial code calling a function deprecated in 2016 — broken instructions still ranking. - Tags: atom/literature/h3 - Every outdated tutorial tells Google your expertise expired. ([View Highlight](https://read.readwise.io/read/01kw3dsjtqmx483q00nz97aen7)) - Note: The core EEAT claim worth keeping: stale tutorials signal expired expertise to Google. - Tags: atom/zettel/z1 ## Links - [[Update Signatures Prove Provenance Not Freshness]] — applies-in: an old tutorial can remain authentic while no longer representing current WordPress behavior. - [[AI Search Inherits the Trust and Fragility of the Sites It Cites]] — context: stale high-authority pages contaminate both search and AI answers that continue to cite them.