Insights
Planning a website rebuild without losing what already works
How to protect useful content, URLs and search visibility when you rebuild a website, with a practical checklist for inventory, redirects and launch.
A new website is a chance to fix years of accumulated problems. It is also an easy way to lose things that were quietly working: pages that rank in search, links partners rely on, and content your customers actually read. The difference usually comes down to planning done before design starts.
Begin with an inventory
Before discussing layouts, list what exists. Crawl the current site and export every URL, along with its title, description and, if you have analytics, its traffic over the last year. Add the pages that are linked from emails, printed materials, partner sites or ads.
For each page, decide one of four things:
- Keep. The page is useful and the URL stays the same.
- Rewrite. The topic matters but the content needs work. Keep the URL if you can.
- Merge. Several thin pages become one stronger page. The old URLs redirect to the new one.
- Retire. The page has no ongoing value. Let it return a proper “not found” response.
This list becomes the backbone of the project. It keeps conversations concrete and makes the redirect plan almost automatic.
Keep the URLs that matter
Search engines and people both remember addresses. Whenever a page’s purpose is unchanged, keep its URL exactly, including the spelling and structure. When a URL must change, redirect the old address permanently to the single most relevant new page.
Avoid two common shortcuts. Do not redirect every old page to the homepage, and do not set up a catch-all rule that sends everything unknown to one place. Both look tidy but they confuse visitors and are often treated by search engines as if the page had disappeared.
Carry over what search engines read
Titles, meta descriptions, headings and image descriptions are part of the content, not decoration. Bring the good ones across, improve the weak ones, and make sure every page still has one clear main heading. If the old site had structured data, such as organization details or article information, keep an equivalent on the new site.
Set the canonical address of each page to its preferred production URL, so copies on preview or staging domains are never mistaken for the real thing. Keep staging sites out of search results entirely until launch.
Design the editing experience too
Many rebuilds fail slowly. The launch goes well, but within a year the content is stale because updating it is awkward. Plan the content model alongside the design: which fields each page type needs, which ones editors should be able to change, and which should stay locked to protect the layout. Include fields for SEO titles, descriptions and social sharing images so your team can manage them without a developer.
Rehearse the launch
A week before launch, walk through the plan with real data:
- Test every redirect from the inventory, not just a sample.
- Check that forms deliver messages to the right inbox.
- Confirm analytics and any tracking you have intentionally chosen are in place.
- Review pages on a phone, with a keyboard and at slow connection speeds.
- Make sure the sitemap lists only the pages you want found and that robots rules allow indexing on the production domain.
On launch day, submit the new sitemap, watch for errors and not-found reports, and fix gaps quickly. The first two weeks are when small mistakes are cheapest to correct.
A useful rule of thumb
If a page earns traffic, links or leads today, it deserves a deliberate decision. Write that decision down, and the rebuild will keep what works while you fix what does not.
