News portal: 280 articles, traffic down 35% — editorial team running on empty

Editorial meeting: the chart that never rises

The editor-in-chief opened the 14-month traffic spreadsheet. The organic line was down 35% — while publish frequency had climbed from 8 to 12 articles per week.

“We’re more productive. Why are organic readers disappearing?”

The managing editor answered with sharper data: of 280 live articles, only 41 drove 68% of traffic. The rest were nearly dead — some had ranked well two years ago, now countable on one hand for impressions.

Editorial POV: writing on a graveyard

As a team proud of volume, this felt unfair. But the Oura audit showed a clear pattern — content decay. Articles never refreshed since 2023–2024 slowly lost position as competitors republished with newer data, cleaner structure, and extractable FAQ.

Worse for editorial: topics this portal once owned — when readers asked ChatGPT, AI citations went to competitors. Not because our old writing was bad. Because it was stale to machines.

What they had tried (editorial lens)

Publish frequency raised. Two freelance writers added. CMS theme swapped. Headlines A/B tested with clickbait.

Result: editorial costs up, traffic still down. Clickbait lifted CTR briefly; bounce followed. New production did not plug old leaks — adding buckets to a leaking tank.

Audit findings: 127 articles with no owner

Familiar pattern for mid-size publishers:

127 articles down >40% year-on-year — no “last reviewed” in CMS, no dateModified in schema, nobody maintaining after publish.

Cannibalization across 280 URLs — three different articles targeting similar queries without pillar/cluster hierarchy.

AI skipping old articles — generative engines prefer answer-first structure, FAQ, freshness signals. A 2022 long paragraph without question headings? Not citation-worthy.

The controversial editorial decision: cut new articles, scale refresh. From 12/week, 7 slots shifted to priority decay updates. New writers pushed back — “we were hired to write new.” Data won: refreshing 32 priority articles projected more recovery than 32 new posts in already cannibalized topics.

What we ran (Oura Content + Atlas)

Content at Oura is not a blind writing machine. For publishers:

1. Decay audit — 18 months GSC, per-URL classification, cluster map.
2. Answer-first refresh — not headline swaps, but restructure: question H2s, 2026 data, FAQ schema.
3. 60/40 calendar — 60% refresh, 40% new; priorities from data, not pitching.
4. Internal linking — decay posts point to strengthened pillars; stop cannibalization.
5. dateModified + Article schema — explicit freshness for Google and AI.
6. Atlas loop — monthly brief, dry-run, per-cluster recovery before next batch.

How to read the numbers below

Typical patterns for similar publisher profiles. Content engagement patterns:

• Decay usually halts after first refresh batch (8–12 weeks), not after new articles.
• Pillar traffic consolidation often moves from ~65% to 75%+ after cannibalization fixes.
• AI citations appear after refresh + FAQ + freshness — separate from classic ranking recovery.

Once decay is controlled, Growth adds OAVF and links on healthy pillars — not on 239 zombie posts.