A website redesign should bring in more qualified inquiries, yet plenty of companies watch three years of organic traffic disappear the week a new site goes live. Keeping search rankings through a rebuild takes methodical engineering across URLs, HTML parity, paid-ad links, and launch-day monitoring.
Work through these four phases in order so every page that earns traffic today carries its authority straight into the new build.
Phase 1: Benchmark what earns traffic before sketching a sitemap
Never redesign site navigation without reading your live data first. Pull four exports from the existing site before touching wireframes:
- Twelve months of Google Search Console top pages and queries, so seasonal winners are never deleted by accident.
- A full site crawl capturing status codes, titles, meta descriptions, H1s, canonical URLs, trailing-slash format, and internal links.
- External backlink targets, including older guides or PDFs that third-party sites link to directly.
- Active paid-search and social ad landing URLs, plus GA4 conversion events and Google Business Profile links, so launch day never burns paid ad spend on 404s.
Every URL carrying organic clicks, paid traffic, or credible backlinks belongs in your migration plan.
Phase 2: Preserve strong URLs and test one-to-one 301 redirects
The safest SEO choice during a rebuild is keeping strong URLs unchanged. If /services/commercial-roofing already sits on page one, keep that exact path.
Where site cleanup genuinely requires moving routes, map every legacy URL to its exact replacement and run an automated list-mode redirect check against staging before DNS cutover:
| Legacy URL type | Correct migration rule | Mistake that leaks authority |
|---|---|---|
| Active service page changing slug | Single-hop 301 straight to the matching new service page | Redirecting to the homepage or using a 302 |
http:// or non-www hostnames | Single-hop 301 straight to canonical https://www. | Multi-hop http → https → www redirect chains |
Trailing-slash variants (/about/ vs /about) | Normalize consistently across canonicals, sitemaps, and edge redirects | Serving duplicate 200 URLs or triggering extra hops |
| Linked PDF or brochure asset | Keep path live or 301 to the updated HTML guide | Letting external backlinks hit a 404 |
| Retired temporary promo page with zero links | Return a true 404 or 410 | Forcing unrelated junk onto live service pages |
Phase 3: Protect on-page SEO, HTML rendering, and AI crawler parity
Redesigns often drop in rankings even when every URL stays intact because new visual templates strip out the concrete copy search engines ranked the page for. Run four parity checks on staging before launch:
- Preserve topic depth on ranking service pages. Tighten the layout and writing without deleting the exact service terminology, specifications, and FAQs buyers search for.
- Keep core copy, headings, tables, and structured data in pre-rendered static HTML rather than client-side JavaScript. That protects both Googlebot and AI search retrieval, as covered in our guide on how Google AI Overviews and ChatGPT pick B2B vendors.
- Verify
robots.txtand edge firewall rules allowGooglebot,OAI-SearchBot,Claude-SearchBot, andPerplexityBot, and confirm no stagingnoindexmeta tags orX-Robots-Tagheaders leak into production. Updatellms.txtalongsidesitemap.xmlso every canonical URL matches. - Confirm GA4 tags, CRM webhooks, and form inbox delivery fire identically on staging, and keep your previous hosting snapshot warm as a clean rollback option during the first week.
Phase 4: Launch-day DNS cutover and 28-day Search Console watch
Lower DNS TTL to 300 seconds one to two days before launch so DNS updates quickly. Immediately after cutover:
- Spot-check SSL, canonical tags,
robots.txt, and the live XML sitemap for200 OK. - Verify your twenty highest-value 301 redirects return single-hop
301→200 OK. - Update any changed landing URLs in Google Business Profile and active paid-ad campaigns.
- Submit the new sitemap in Google Search Console, run URL Inspection on the homepage and top revenue pages, and submit every contact form yourself on desktop and mobile.
Expect minor ranking movement for two to six weeks while Google re-indexes the new HTML. Watch Search Console's Page Indexing report weekly during that window so any stray 404 or canonical mismatch gets fixed within hours rather than months.
If you are moving off WordPress specifically, pair this playbook with our WordPress to static site migration guide and our small business website cost guide.
LifeVen rebuilds websites for small and mid-size B2B companies on Astro or Next.js static architecture and Cloudflare edge hosting, backed by senior Big-Tech engineering and CS/AI research. You get a fixed written quote, full ownership of your domain and source code, and an SEO-safe migration built for Google Search and AI recommendations. Share your live URL on our website service page to start with a crawl audit.