What to keep from your old website when you redesign
Keep the URLs, pages and words that earn traffic, links and enquiries, and drop the rest with redirects. How to decide page by page, with a decision table.
By Sohail Hussain21 November 20265 min read
Keep anything that earns something: pages that bring search traffic, URLs that other sites link to, copy that turns visitors into enquiries, and the integrations and records the business depends on. Drop pages that nobody visits, links to or needs, but redirect them rather than deleting them silently. Make the decision page by page from data, not from what looks old.
The rest of this guide is the decision table we use, then the things people forget to keep because they are not pages. It is the second stage of the website redesign process, and the place most website redesign and migration projects either protect their traffic or lose it.
Which pages should you keep?
Start from an inventory of every URL with twelve months of Search Console clicks and the number of sites linking to it. How to audit your current website explains how to build it. Then give every row one of these actions:
| What the page has | Action | URL |
|---|---|---|
| Search clicks or enquiries | Keep and improve | Same URL if at all possible |
| Links from other sites, little traffic | Keep, or merge into a stronger page | Same URL, or 301 to the merged page |
| A topic covered by another page too | Merge into the stronger one | 301 to the merged page |
| Outdated content that still ranks | Update it | Same URL |
| No traffic, no links, still needed by visitors (legal, careers) | Keep as is | Same URL |
| No traffic, no links, not needed | Remove | 301 to a close, relevant page, or 404 or 410 |
Two rules sit behind the table. First, traffic and links decide, not taste. A plain, wordy page that brings in thirty enquiries a year is worth more than the stylish one you are proud of. Second, removing a page is fine; losing its URL is not. Every removed URL either redirects to something relevant or returns a deliberate 404 or 410. Redirect mapping has the template.
Should you keep the same URLs?
Yes, wherever you can. Every changed URL is a redirect Google must process and a small risk that something is lost. A redesign is not a reason to change URLs on its own.
Change a URL only when it causes a real problem: dates in blog URLs that make content look stale, .html or .php endings tied to an old platform, ID-based URLs like ?page_id=42, or a structure that no longer matches your services. When you change one, redirect it, and update the internal links to point at the new URL directly.
Which words should survive the rewrite?
For pages that rank, keep the parts that match what people searched for:
- The title tag and H1. If a page ranks for "warehouse racking installation Pune", the heading that says so is doing its job. Keep it close to the original.
- The paragraphs that answer the query. The definition, the process, the specifications, the prices. Rewrite around them, not over them.
- FAQs and specific details. Product dimensions, service areas, certifications, named standards. These are often what matched a long search query.
Rewrite freely: vague introductions, outdated claims, copy written for a service you no longer sell, and sentences that say nothing ("We are a leading provider of innovative solutions").
A practical check: paste the old and new text of each top page into the diff checker before launch. If most of what matched the page's top queries has disappeared, put it back. The meta length checker catches titles and descriptions that grew or shrank too far in the rewrite.
What else needs to carry over besides pages?
The things that break quietly after a redesign are usually not pages.
| Asset | Why it matters | What to do |
|---|---|---|
| PDFs and downloads | Other sites link to them; some rank on their own | Keep the URL or redirect it |
| Images with search traffic | Image search sends visitors | Keep file names and alt text where possible |
| Existing redirects | Old links still point at them | Copy into the new redirect map, pointed at final URLs |
| Structured data | Rich results depend on it | Rebuild every type the old site output |
| Analytics property | Years of history | Keep the same GA4 property; install it on the new site |
| Search Console property | Comparison data | Keep it verified; nothing changes if the domain stays |
| Form routing and CRM fields | Enquiries must still arrive | Test every form to its real destination |
| Email templates and notifications | Customers see them | Rebuild and send test messages |
| Tracking and conversion events | Marketing reports depend on them | Recreate the same event names |
The last three are not SEO, but losing them costs the business more than a ranking dip. A contact form that sends to a former employee's inbox looks fine on launch day and costs you every enquiry until someone notices.
What should you let go of?
Some things look like assets and are not.
Pages built for an old SEO playbook. Dozens of near-identical "web design in [city]" pages with the city name swapped are what Google's spam policies call doorway pages. Merge them into real service and location pages with distinct content, and redirect the rest.
Features nobody uses. Homepage sliders, news tickers, a blog last updated four years ago, a chat widget nobody answers. Check analytics before keeping any of them.
Duplicate and thin pages. Tag archives, print versions, near-empty category pages. Merge or remove them, with redirects for any that have links.
Copy written for the business you used to be. If the site still sells a service you stopped offering, retire the page and redirect it to the closest current one.
How do you record the decisions?
Add three columns to the URL inventory: action (keep, improve, merge, remove), new URL, and owner. The owner is the person who writes or approves that page. The finished sheet becomes the content plan for the new site and the first draft of the redirect map, so the work is done once.
Review it with someone who knows the sales side. They will know which page a large client mentioned in the first meeting, which no analytics report shows. If you are still deciding whether the site needs rebuilding at all, redesign vs refresh is the place to start.
Was this guide useful?