A website rebuild creates permission to improve almost everything. That freedom can also remove the quiet assets the existing site has built over time: useful pages, external links, familiar URLs and content that answers a specific question well.
The right approach is not to preserve every old page. It is to understand what has value before deciding what changes.
Inventory the current site
Export a list of indexable URLs and group them by type: services, products, articles, case studies, locations, policies and system pages. Add page titles, status codes, canonical settings and available performance data.
This reveals duplicates and forgotten content, but it also prevents important pages from disappearing simply because they were not in the main navigation.
Add evidence to the decisions
Use Search Console and analytics to identify pages that receive impressions, visits, enquiries or links. Talk to staff about pages they send to customers and resources that support sales or service.
Low traffic alone is not a reason to delete a page. A specific technical article may help a small number of highly qualified visitors. A policy page may be operationally necessary. The decision should reflect purpose.
Map every old URL
For each page, choose one outcome:
- keep the URL and improve the content;
- move it to a new URL and add a permanent redirect;
- consolidate it into a stronger related page;
- remove it because it has no replacement or value.
Avoid redirecting everything to the homepage. A redirect should lead to the closest meaningful destination. Preserve query parameters where they carry campaign or product information.
Retain meaning in the new structure
Design teams sometimes replace descriptive headings and navigation with short, stylish labels. Make sure the new experience still tells people and search engines what each page is about.
Carry across useful title tags, descriptions, headings, image alt text and structured content, then improve them where the page has changed. Do not copy metadata blindly onto a different topic.
Treat content migration as production work
Migration involves formatting, internal links, images, downloads and reusable fields. Decide what can be imported and what needs editorial handling.
Use a checklist for each content type. A case study may need client, services, outcome, gallery and related links. Structured migration prevents the new site becoming a collection of differently formatted pages.
Test before changing DNS
Crawl the staging site and compare it with the URL map. Check redirects, canonical URLs, robots settings, XML sitemaps and metadata. Test important forms and conversions as well as content.
Ensure the staging site is not indexed, but remove those restrictions at launch. This small detail has caused more than one avoidable search problem.
Monitor the weeks after launch
Submit the new sitemap, review indexing and watch for crawl errors or redirect gaps. Compare search queries and conversions rather than reacting to normal daily variation.
Keep the redirect map. Old URLs can continue receiving visits from bookmarks, documents and external websites for years.
Improve without erasing history
A rebuild should make the site clearer, faster and easier to manage. Preserving what works is not caution for its own sake; it gives the new website a stronger starting point.
Web Paste plans content structure, migration and measurement as part of website redesign and development. If you are considering a rebuild, the most useful first step is an inventory of the current site, not a blank homepage canvas.
