A rebuild goes wrong when it starts with design and ends with a panic about redirects. These seven steps run the other way round: you find out what you actually have, you decide how little needs to change, and you protect your search traffic throughout.
Before you start
Make sure you need a rebuild at all. If the site is slow, fragile or costly to change, the platform is the problem. If you're just bored with how it looks, a redesign on your existing stack is cheaper and much safer.
The seven steps
- Inventory. List every URL, unique layout, form and third-party integration. This list is your real scope, and it'll be longer than you expect.
- Decide the stack. Astro suits content sites, Next.js suits anything with logins or dashboards. Keep your CMS if the people using it are happy.
- Rebuild layouts as components. Build one component per unique template, not one per page. Fifty pages might be only eight layouts.
- Migrate content. Export, clean, import. Move images to your new host or a CDN at the same time.
- Map redirects. Send every old URL to its exact new equivalent with a 301. Rankings are kept or lost in this step, so give it real time.
- Cut over. Deploy, switch DNS and keep the old site reachable on a subdomain for a week for reference.
- Monitor. Watch Search Console coverage, Core Web Vitals and 404s for at least a month.
Where people lose time
- Rebuilding the CMS when nobody was complaining about it.
- Starting design before the inventory is finished.
- Changing URLs, platform and content in the same release. Do one big thing at a time, whenever you can.
- Leaving redirects to launch week.
Doing it from the road
A rebuild suits a slow month in one place. Choose a base with reliable internet for the cutover and the week after, and avoid a border crossing or a flight on launch day. You'll want a steady connection for a week of small fixes.
Before you commit, price it with what a rebuild costs, and keep the SEO protection guide open during step five. You can see how this played out on a real project in our case study.