S.
  • Services
  • For you
  • Solutions
  • Work
  • About
  • Know-how
  • Blog
Start a project
EN/PL/RU
  • Services01
  • For you02
  • Solutions03
  • Work04
  • About05
  • Know-how06
  • Blog07
Start a project
EN/PL/RU
Vlad Sedenko
Independent web product developer
EU / Poland / Warsaw
Products
  • NextWooNext.js storefront for WooCommerce
© 2026. All rights reserved
Services
  • Product Discovery
  • UX/UI Design
  • MVP Development
  • SaaS Development
  • Website Redesign
  • Web Application Security
  • Conversion Optimization
  • API Integrations & Business Automation
  • Product Support
Explore
  • Services
  • For you
  • Work
  • Solutions
  • About
  • Blog
  • Know-how
  • Contact
Start a project
  • vlad@sedenko.net
  • LinkedIn
  • Privacy/Cookies
Know-how/Next.js SEO Checklist: The Complete Guide for App Router (2026)

Part 21 of 22

Content decay: refresh, consolidate or prune

Rankings erode by default: how to spot decaying pages in Search Console and decide per page whether to update, merge into a stronger one, or remove it entirely.

2026-07-15
Content decay: refresh, consolidate or prune

All topics in this guide

A practical, section-by-section SEO checklist for Next.js: rendering strategy, Metadata API, hreflang, structured data, Core Web Vitals, and optimization for AI answer engines.

Every page starts dying the day you publish it: competitors ship newer takes, information goes stale, Google's freshness preference kicks in. Decay is the default state of content — growth is what happens when your refresh rate beats your decay rate. Sites that only ever add pages end up as graveyards where the dead weight drags down the living.

Detect it before the traffic is gone

In Search Console, compare the last 6 months against the previous 6, per page:

  • Clicks down, position down → classic decay, act on it.
  • Position stable, CTR down → the SERP changed around you (AI Overview, new features) — a title/intent problem, not a content one.
  • Impressions down across a whole cluster → demand shift or a sitewide quality issue.

Keep a content inventory (a spreadsheet is fine): URL, target query, last real update, 6-month click trend. Review quarterly — the same cadence as your orphan-page audit.

The four verdicts

For each decaying page, pick one deliberately:

  1. Update — topic still has demand, page still ranks somewhere on pages 1–2. Refresh facts and screenshots, cover the follow-up questions searchers now ask, cut dead sections. Real changes only, then an honest dateModified and a re-index request in GSC.
  2. Consolidate — three thin posts circling one topic split their authority and cannibalize each other. Merge into the strongest URL, 308 the losers to it, update internal links to point at the winner directly.
  3. Prune — no demand, no links, no conversions, no salvage value. Return 410 (or 404) and remove from the sitemap. Post-Helpful-Content, a mass of zero-value pages measurably suppresses the whole domain; deleting can lift what remains.
  4. Leave alone — stable evergreen performers. Don't churn them for the sake of a fresher date; cosmetic edits with a bumped dateModified are the fastest way to teach Google your dates lie.

Updating that actually recovers rankings

The pages worth the most effort are the almost-winners: queries sitting at positions 5–15 in GSC. For each: what do the top 3 have that you lack (data? screenshots? a table? freshness?), close that gap, strengthen internal links to the page with descriptive anchors, and give it two–four weeks before judging. Track updated pages in the inventory — the before/after click delta tells you whether your refresh playbook works.

Checklist:

  • Quarterly GSC decay review: 6-month click/position deltas per page
  • Content inventory maintained with last-real-update dates
  • Every decaying page gets an explicit verdict: update / consolidate / prune / leave
  • Consolidations ship with 308s and internal-link updates in the same change
  • dateModified bumped only for substantive edits; refresh results measured
← PreviousAccessibility and SEO: one job, two rewardsNext →Off-page for developers: earning links without buying them

01—22

All topics in this guide

  1. 01Rendering strategy: what does the crawler actually see?→
  2. 02Metadata API: titles, descriptions and the template pattern→
  3. 03Canonical URLs and hreflang: one page, one address→
  4. 04Open Graph and dynamic OG images→
  5. 05sitemap.ts and robots.ts: file conventions instead of hand-written XML→
  6. 06Structured data: JSON-LD that earns rich results→
  7. 07Images, fonts and scripts: the classic performance trio→
  8. 08Core Web Vitals: the three numbers Google measures→
  9. 09Redirects, 404s and status codes→
  10. 10Caching and content freshness→
  11. 11AEO/GEO: getting cited by ChatGPT, Perplexity and Google AI Overviews→
  12. 12Monitoring: SEO is a loop, not a launch task→
  13. 13Trust and E-E-A-T: making your site believable→
  14. 14Image SEO: turning pictures into traffic→
  15. 15Internal linking and site architecture→
  16. 16Search intent: pages that match what people actually type→
  17. 17Programmatic SEO in Next.js: pages at scale without the spam→
  18. 18SEO migration: replatforming to Next.js without losing traffic→
  19. 19Pagination and faceted navigation without index bloat→
  20. 20Accessibility and SEO: one job, two rewards→
  21. 21Content decay: refresh, consolidate or prune•
  22. 22Off-page for developers: earning links without buying them→

Want this handled for you?

I audit and fix technical SEO on Next.js sites — indexing, performance, hreflang and AI visibility.

Technical SEO service