How to Handle Old Content During a Website Redesign: Keep, Merge, Rewrite, or Delete
Redesign meetings often focus on the new home page and visual direction, while hundreds of legacy pages are dismissed with "we'll migrate them." At launch, the team discovers that ranking articles were missed, customer-bookmarked resources broke, and duplicate content moved into the new site unchanged.
Legacy content should not be judged by preference. Evaluate every page against user value, business value, search performance, backlinks, accuracy, and the new website's positioning.
01 Build a Complete URL and Content Inventory
Include public pages, PDFs, images, downloads, campaign pages, and old language versions—not only pages reachable through navigation. Combine sitemaps, crawlers, analytics, Search Console, and server logs.
For every URL, record at least its title, type, traffic, search queries, backlinks, conversions, update date, owner, and destination on the new site. Without an inventory, redirects and acceptance rely on memory.
Five Actions for Legacy Content
| Action | When to Use It | Execution Priority |
|---|---|---|
| Keep | Accurate content with ongoing traffic and business value | Migrate body content, media, metadata, and the original or equivalent URL |
| Update | The topic remains valuable, but information is outdated or incomplete | Rewrite key passages and add evidence and current search intent |
| Merge | Several pages overlap or are individually too thin | Choose a primary page, consolidate content, and redirect each old URL |
| Delete | No user value, backlinks, or replacement need | Return 404 or 410 and remove internal links and sitemap entries |
| Replace | An old service or product has a clear new version | 301 redirect to the most relevant new page, not automatically to the home page |
02 Low Traffic Does Not Mean No Value
Some technical resources receive little traffic but are essential evidence before a sale. Privacy, contract, and support pages are not measured by traffic either. Consider the customer journey and internal use.
Conversely, high-traffic content that no longer relates to the business, produces no conversions, and repeatedly misleads users may not deserve retention. Traffic is only one form of evidence.
03 Preserve Genuinely Useful Information When Merging
Do not mechanically join three old articles into one longer article. First determine whether they serve the same search task, then remove duplication, add missing answers, and unify the conclusion.
The merged page should retain important keywords and the internal- and external-link context of the old pages. Redirect each legacy URL to the new primary page and update internal links.
04 Redirects Must Be One-to-One or Semantically Relevant
Sending many legacy pages to the home page prevents users from finding the original content, and search engines may treat the redirects as irrelevant or Soft 404s. Map every old URL to the most relevant new one.
When no suitable replacement exists, an honest 404 or 410 is generally better than an arbitrary redirect. A custom 404 page can provide search, popular sections, and contact information.
05 Migrate More Than Body Copy
Titles, descriptions, image alt text, structured data, authors, dates, downloads, internal links, canonicals, and hreflang can all affect performance. An inadequate CMS field model can silently lose this information during migration.
Compare before-and-after screenshots and data for high-value pages so the new template does not alter heading hierarchy, body width, or download access.
06 Validate Every Legacy URL After Launch
Check status codes, redirect destinations, canonicals, sitemaps, internal links, and page content. Prioritize URLs with traffic, backlinks, conversions, and brand value.
Monitor 404s, rankings, indexing, crawling, and conversions for several weeks after launch. Add missed mappings quickly instead of waiting for a visible traffic decline.
Frequently Asked Questions
Should an Old Article Receive a New Publication Date?
Update the date only after substantive revision, and preserve the original publication date or explain the update. Changing only the date does not improve old content.
Can Every Page Without Traffic Be Deleted?
No. Also check backlinks, sales use, customer support, and compliance value.
Can an Old URL Be Replaced with a Shorter One?
Yes, with a 301 mapping and updates to internal links, sitemaps, and canonicals. If the old URL performs well and the benefit is small, retaining it may be better.
Should a Deleted Page Return 404 or 410?
Both indicate unavailable content; 410 states permanent removal more explicitly. Choose based on server and maintenance capabilities, but do not return 200 or redirect to an unrelated page.
Must PDFs and Download Files Be Migrated?
Inventory them. Externally referenced or customer-used files need a retained URL or clear replacement, with permissions, versions, and accessibility checked.
| Service | View |
|---|---|
| Related Services | View Service Details |
| Project Inquiry | Contact JVDS Design Studio |
| Design and Website Development Articles | View Service Details |
Link copied
