# Unmaintained Tutorial Content Is an SEO and Safety Liability ## Claim 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 at once. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for high-volume how-to/docs sites in fast-moving tech niches; weaker for evergreen or low-volume topics where advice doesn't age as fast. - Breaks if a search engine judges historical-but-clearly-dated content neutrally rather than as a current signal of site quality — an assumption this claim doesn't verify. ## Evidence The WPBeginner case's two examples: a 2012 post still live in 2026 recommending an ancient, insecure WordPress version, and a tutorial built on `get_currentuserinfo()`, a function deprecated in 2016 so the code no longer runs. Proposed mechanism: broken tutorial → broken reader trust → bounce → Google reads those engagement signals across thousands of pages. ## Links - [[3. Resources/Permanent Notes/A Small Sample Cannot Prove a Sitewide Decay Claim]] — because contrasts; the evidence for this claim is itself a small, possibly non-random sample. - [[3. Resources/MOCs/DevRel MOC]] — because applies-in ## Tests / falsifiers - Run a controlled cleanup (update vs. noindex vs. leave-alone) on a stratified sample of aging pages and compare ranking trajectories; no measurable difference would weaken the claim. - Pair analytics engagement metrics (bounce, dwell) with code-validity checks per page to test the trust→bounce→ranking mechanism directly. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/WPBeginner Collapse — Outdated Content, Not Just Promotion (EEAT)]] — both worked examples and the proposed mechanism.