Consolidating a Decaying Content Library Before a Replatform

Neither extreme. The CMO is right that 900 low-traffic posts and 140 near-duplicates create risk, but a mass deletion before a migration conflates two changes and makes attribution impossible. With a three-week dev freeze, only changes that do not require engineering should happen now. That means editorial consolidation of near-duplicate alternatives pages into stronger comparison pages using existing templates, 301 mapping, internal link updates via CMS, and a prioritized inventory. The actual migration should carry a reduced, mapped URL set. The legal requirement that all URLs resolve or redirect means every retired URL needs a 301 to a relevant page, not a 410, unless the page has no topical equivalent. Consolidating before migration reduces the mapping burden and prevents 4,200 URLs from being carried forward. But do not delete pages with backlinks or conversions without review. Sequence: inventory and scoring in weeks 1-2; merge 140 alternatives pages and update internal links in weeks 2-3; freeze other content changes; migrate with the 301 map; post-migration monitor 404s and rankings. This isolates migration risk from content-pruning risk.

Build a page-level inventory with sessions, conversions, assisted conversions, backlinks, keyword rankings, and topical fit. Do not use traffic alone. The conversion gap matters: blog posts at 0.4% may still assist, so check path analysis before cutting. Classify: keep and improve pages with conversions, backlinks, or rankings; merge thin posts that target the same intent into a hub; redirect retired URLs to the closest hub; remove only pages with no traffic, no links, no conversions, and no strategic role, and still redirect them. The 900 low-session posts are not automatically dead; some may be seasonal or long-tail. Prioritize the 140 near-duplicates first because they cannibalize the head term. For the head term, choose one canonical page, merge unique content from the other two, and internally link with descriptive anchors. Given two writers and a freeze, limit to 30-40 merges before migration. After migration, run a 90-day test on a sample: consolidated hubs vs untouched control to measure clicks and conversions.

At 30 days: crawl errors, 404s, redirect chains, index coverage, and whether the 301 map resolves. Expect temporary ranking fluctuation; do not panic. At 90 days: organic sessions and conversions for consolidated hubs vs control, rankings for the head term, and internal link equity flow. At 180 days: revenue per organic session, hub conversion rate, and whether the head term improved. Guardrails: if organic conversions fall more than 15% against control for two consecutive months, pause further pruning and audit redirect targets. If 404s exceed 1% of migrated URLs or redirect chains exceed two hops, fix immediately. Also track branded search and direct traffic to detect lost equity. The test should be a holdout, not a before-after comparison, because seasonality and migration effects confound. Rollback is not restoring deleted pages blindly; it is restoring the highest-equity URLs with proper 301s and content.