A Redesign Is a Lead-Flow Migration, Not a Design Project
Most local businesses treat a website redesign as a design project: new look, new copy, new photos, launch. Then the phones go quiet. Rankings sag for two months, form submissions fall, and nobody can say why — because nobody treated the existing site's lead flow as an asset that had to be moved intact. We architect sales engines, not brochures, so we run every redesign as a migration project. The design is the visible half; the invisible half is what protects your pipeline while the visible half changes. This is the playbook we run before, during, and after every rebuild.
Audit what generates leads today
Before a single mockup, document what the current site actually produces. Pull all of it into one spreadsheet — the lead-source audit:
- Top landing pages by lead: In Google Analytics 4, pull engaged sessions by landing page and cross-reference with conversion events. Your top five lead-producing pages are the pages that matter; everything else is secondary.
- Ranked pages: Export query and page data from Google Search Console. Any page ranking on page one for a money keyword is a revenue asset. Changing its URL, title, or content without a plan risks losing that position.
- Forms and their conversion rates: List every form — quote request, contact, financing application — the page it sits on, and its completion rate. A form converting at a healthy rate tells you something about the page around it; replicate the structure, not just the form.
- Call volume per page: In your call-tracking platform, filter calls by landing page. In our experience, a handful of service pages drive most of a contractor's calls.
- GBP link destinations: Check where your Google Business Profile website link and appointment link point. If they deep-link to pages you plan to delete or rename, you've found the leak before it happens.
Build a URL inventory and redirect map
Every URL on the current site goes into a master inventory — the redirect map — with four columns: old URL, action (keep, rewrite, merge, retire), new URL, and owner. The rules:
- Keep: URLs that rank, earn links, or convert. Don't touch them unless the build demands it — and even then, keep the slug identical.
- Merge: Thin or duplicate pages get consolidated. The old URL 301-redirects to the strongest survivor so link equity flows instead of evaporating.
- Retire: Pages with no rankings, no traffic, and no leads can die — but confirm that against the audit before deciding a page is worthless.
Most retired or renamed URLs should get a one-to-one 301 to the closest equivalent — blanket redirects to the homepage should be avoided. Grouped redirects dilute relevance and can drag down rankings for pages that were earning calls. Test the full map in a spreadsheet before launch, then verify each redirect returns a 301 (not a 302, not a 404, not a chain) the day the site goes live. Screaming Frog's list-upload mode will check hundreds of URLs in minutes.
Preserve on-page SEO equity
Rankings live in the details developers copy right over. For every keep-or-rewrite page, migrate deliberately:
- Title tags and meta descriptions: Copy the ones that earn clicks verbatim unless the rewrite is intentional, and track changes in a column.
- Body content: Rewritten copy is fine — often necessary — but keep the primary keyword, the headings that match search intent, and the local signals (service area, licensing, city names) intact.
- Internal links: Crawl the old site, export every internal link, and rebuild the important ones. Orphaned pages lose crawl priority and conversions.
- Schema markup: LocalBusiness, Service, and FAQ schema should carry over, then validate again in Google's Rich Results Test.
Keep Lead Capture Live During the Build
A redesign takes weeks. Your leads don't pause. The discipline that protects them is staging isolation: the new site lives on a staging subdomain with noindex applied, separate from the live domain. Forms on the live site stay active and tracked. Avoid pointing DNS at an unfinished build, even briefly, because "it's almost done" is exactly how live sites break on a Friday afternoon; use a controlled cutover. If stakeholders need to review, password-protect staging or walk them through it over a screen share. We've seen businesses lose two weeks of emergency HVAC calls because a developer flipped the A record on a Friday afternoon to "test." Don't be that story.
Also freeze content changes during the build window, or sync them daily. If your office manager updates pricing or service pages on the live site while the redesign copies old content, you launch stale and wrong.
Baseline, Soft Launch, Iterate
Set the baseline before anything changes
You can't prove the redesign didn't hurt without a "before" snapshot. Record, for at least the trailing 90 days: total calls and calls per key page, form submissions, booked jobs attributable to the website, organic sessions per key page, and Search Console impressions for your top queries. Store it in a shared doc — the launch-metrics baseline — with the date range noted. This is the document you compare against for the next quarter.
Run soft-launch checks before going live
On launch day, don't flip the switch and walk away. Run checks in this order:
- Verify every 301 in the redirect map resolves correctly and that no internal link 404s.
- Confirm tracking: phone numbers swap correctly through your call-tracking script, form events fire into GA4, and conversions still record in your CRM.
- Submit the new XML sitemap in Search Console and confirm the old URLs are discovered as redirected.
- Test one real form submission and one call per key page, end to end, into the CRM pipeline your office manager actually works.
Iterate after launch — the redesign isn't done at launch
For the first four weeks, watch the baseline daily: calls, forms, organic sessions on key pages, Search Console coverage. Expect a wobble — rankings often dip temporarily after a migration, then recover within weeks if redirects and content were preserved. A dip past four weeks often means something in the map or content migration needs review; go back to the audit and compare page by page. Then keep iterating on conversion: A/B test the headline and form length on your top landing page, because the new design is a hypothesis, not a verdict.
Actionable steps
Start this week, before any designer opens a mockup:
- Open GA4, Search Console, your call-tracking dashboard, and your Google Business Profile; export top landing pages, ranked pages, forms, call volume per page, and GBP link destinations into one audit spreadsheet.
- Build the redirect map: every current URL with a keep, rewrite, merge, or retire decision and its target URL.
- Copy every title tag, meta description, and internal link for keep-and-rewrite pages into a migration doc.
- Stand up a password-protected, noindexed staging environment, and write "never point DNS at staging" into the project brief.
- Record the 90-day baseline: calls, forms, booked jobs, organic sessions per key page, top queries.
- Write the launch-day checklist — redirect test, tracking test, sitemap submission, live form test — and assign an owner before launch week.