B2B Website Redesign SEO Checklist: Keep Rankings and Leads

Key takeaways

Website redesign SEO is only half the job. A B2B website redesign has two failure modes, rankings and leads, and most teams only staff one. This website redesign checklist covers both, so you can ship without losing rankings or leads, and it doubles as a website migration checklist whenever URLs, templates, or the CMS change.

• Leads need their own owner, their own baseline, and their own Day 0/7/30/90 scorecard, or you'll "win" the SEO migration and quietly lose pipeline.
• Build the redirect map first, with a permanent server-side 301 for every changed URL.
• Keep 301 redirects live for at least a year, ideally forever.
• Write a rollback plan with triggers, an owner, and a decision window before launch day.
• Re-test every form, webhook, routing rule, and scheduler before and after launch.

Definition: Website migration SEO is protecting search visibility when a site changes its URLs, CMS, domain, structure, or templates. A redesign migration is any redesign that changes one of those.

I'm Madhav Bhandari, CMO at Storylane. I've watched teams run clean SEO migrations while demo requests dropped in silence, because nobody owned leads.

Redesign, rebuild, migration, or relaunch: why the difference changes your risk

These four words get used interchangeably in kickoff meetings, and that's where the risk starts. A "refresh" that quietly changes URL slugs is a migration, whether or not anyone called it one. For the design decisions themselves, see our guide to B2B website design; this guide covers what has to survive them.

My rule is simple. If the "What changes" column includes URLs, CMS, or templates, treat the project as a migration.

That means a redirect map, staging QA, and a rollback plan. I would not let a team skip those because the project has a friendly name.

What a bad redesign actually costs: rankings and leads are two different risks

Ranking loss is loud, because Google Search Console shows it. Lead loss is quiet, because a form that looks fine can stop reaching your CRM without any visible error.

Teams watch the loud risk and assume the quiet one is covered. That's why I care as much about making sure your marketing funnel doesn't leak leads mid-migration as I do about redirects.

Example: the cost of one broken thank-you redirect. These numbers are illustrative assumptions, so swap in your own.

1. Your site gets 20,000 organic sessions a month, and 1% fill a form. That's 200 leads a month.
2. A broken thank-you redirect silently drops 30% of submissions for three weeks. That's about 45 of roughly 150 leads.
3. At 20% lead-to-opportunity, those 45 leads become about 9 opportunities.
4. At a 25% win rate and a $30,000 ACV, that's roughly 2 lost deals and $60,000 in closed-won revenue.

None of that shows up in your SEO report.

Why protecting leads requires a separate plan from protecting rankings

SEO migration plans are built around URLs, crawlers, and indexation. Lead protection is built around forms, hidden fields, webhooks, routing rules, and calendars. Those systems have different owners, failure signals, and tools, so one checklist can't cover both.

Buyers already feel these as separate worries. A website marketing executive at an enterprise software company, in the middle of a big migration, put it this way:

"And the traffic is probably going to drop even further a little bit because I'm imagining that the organic traffic is probably going to drop a little bit from search engines because it just usually happens that way."
- [website marketing executive, enterprise software]

Their deeper concern was pipeline. With lower traffic, they couldn't build the business case for anything new they launched on the site.

Name a lead-continuity owner in marketing ops or RevOps, with authority to block launch. Give them their own baseline and their own rows in the scorecard.

Website redesign SEO audit: baseline everything before anyone touches the site

You can't prove a migration worked without a before picture. The audit also surfaces the forgotten forms and scripts that break first.

1. Export 12 months of performance data so seasonality doesn't fool you later.
2. Crawl the full site and list every live URL, including orphaned pages.
3. Inventory every embedded asset, including forms, chat, demos, and schedulers, and give each one a named owner.
4. Map every conversion path from landing page to CRM record.
5. Freeze the baseline in a shared sheet that nobody edits after sign-off.

Step 3 is the one teams skip. Knowing who owns each form, chat widget, and demo, and where its leads go, is cheap to answer before a migration and expensive after one.

SEO baseline: rankings, traffic, top pages, and backlinks

Your SEO baseline answers one question after launch: did we lose anything, and where? Save exports as files, because dashboards and properties often change during a migration.

• Pull your top 20 non-branded keywords and their average position from Google Search Console.
• Export organic sessions and conversions by landing page from GA4 for the last 12 months.
• Crawl the current site with Screaming Frog and save titles, meta descriptions, H1s, canonicals, and status codes.
• Flag the pages that drive most of your organic traffic and organic leads. These get the most QA attention.
• Export linking domains and the exact URLs they point to, so each one gets a redirect.
• Record your indexed page count from the Search Console page indexing report.
• Note Core Web Vitals for your top templates so you can compare speed after launch.

I'd rather over-export here than under-export. Storage is cheap, and rebuilding a pre-launch baseline from memory is impossible.

Lead and conversion baseline: form fills, demo requests, and lead-source tagging

Almost nobody builds this baseline, yet it tells you whether the redesign paid off. Measure it page by page, because a sitewide average hides the one broken form. If you're rebuilding key pages anyway, our guide to building a high-converting landing page is a useful reference.

There's a second reason to take it seriously: a relaunch resets your conversion baseline. New layouts, copy, CTAs, and forms all change at once, so a post-launch conversion rate can't be compared cleanly with the old one. Before launch, note which lead-capture points will survive the redesign unchanged. Those become your control, the one number you can still compare like for like.

Expect surprises. A head of growth marketing at a data platform company checked live during a call:

"I'm just pulling up Google Analytics. It's much lower than that. We just don't have a high volume of inbound like form fills."
- [head of growth marketing, data platform]

How you can implement it:

• Record form fill rate and demo-request rate for each top page.
• List every form, including campaign and event forms, with its ID and destination.
• Confirm every lead has a CRM source value, and note how many arrive blank.
• Document your UTM parameters and the hidden fields that capture them.
• Record MQL-to-meeting rate by source so you can spot routing breaks later.

Stakeholder sign-off checklist for marketing, SEO, dev, and RevOps

Redesigns fail at the seams between teams. SEO assumes dev tested the forms, dev assumes marketing ops checked the webhooks, and RevOps finds out when reps complain. A written sign-off closes those seams.

Give security its own calendar time. New scripts, embeds, and vendors often need a security review, and that review can easily outlast a tight launch window.

My opinion: if someone can't produce the evidence in the right-hand column, they haven't signed off.

The URL and redirect map: the one document that prevents most disasters

The redirect map lists every old URL and where it goes. Google's guidance is to use permanent, server-side redirects, such as a 301 or 308, when URLs change (Google Search Central, site moves documentation). Map each old page to its closest equivalent, because blanket homepage redirects throw away the relevance you built.

Copy this template and fill in one row per old URL:

Sort by organic sessions and linking domains, then QA from the top down. Collapse every redirect chain so each old URL reaches its final destination in one hop.

I'd add the "Conversion path on page" column even if your agency doesn't ask for it. It turns the SEO map into a lead-protection map.

How long to keep redirects live, and why it actually matters

Google recommends keeping redirects for as long as possible, generally at least one year (Google Search Central, site moves documentation). I'd go further and keep them permanently. The mechanics explain why.

Why a year is the minimum: Google only sees a 301 when it recrawls the old URL and follows the redirect. Low-traffic pages get recrawled rarely, so their signals can take months to transfer. Remove the redirect early and some old URLs never pass their signals to the new page.

Backlinks are the bigger reason to keep redirects forever. Other sites linked to your old URLs years ago, and almost none of them will update those links. The redirect is the only thing connecting that authority to your new page.

Referral traffic follows the same logic. Old URLs live in partner sites, email signatures, and sales decks, and each one can still send you a lead. Keeping a 301 costs almost nothing, while removing it turns every stray link into a 404.

Website migration checklist: staging QA before cutover

Staging is where problems are still free to fix. Put it behind authentication, then crawl it like production.

• Crawl staging with Screaming Frog and confirm every old URL returns a single 301 to its mapped destination.
• Compare titles, H1s, and canonicals against your baseline export.
• Submit a test lead through every form and confirm it lands in the CRM with the right source.
• Test every scheduler and router handoff end to end.
• Measure page speed with every embedded chat, demo, and scheduler widget loaded.
• Confirm GA4 conversion events fire on the new thank-you pages.

Give the scheduler handoff extra time. If your routing lives in custom template code, a new template can silently remove it.

Your rollback plan: write this before you launch, not after

A rollback plan is a decision made calmly in advance, so nobody makes it in a panic. Keep the old site deployable for two weeks, and rehearse this once.

1. Roll back if form and demo-request submissions fall below half of baseline for 24 hours, or if key pages return server errors.
2. Give one named person, usually the web lead, authority to make the call. Marketing and RevOps are consulted, but they don't vote.
3. Set the decision window at the first 72 hours. After that, fix forward, because Google has started crawling the new URLs.
4. Freeze content publishing and CRM changes the moment a trigger fires.
5. Point DNS back to the old environment, and restore the old redirect rules.
6. Confirm test leads from your top five forms reach the CRM and route correctly.
7. Recover submissions captured during the outage from form logs, then tell sales which leads were affected.

I would not launch without steps 1 to 3 agreed in writing.

Protecting lead capture and CRM routing through the migration

Every lead travels a chain from campaign click to booked meeting, and a redesign can break any link without touching rankings. Test it on staging and after launch.

1. A visitor lands on a page with campaign UTM parameters.
2. The form or embed stores those UTMs in hidden fields.
3. The visitor submits, and the thank-you page fires the GA4 conversion event.
4. A webhook or native sync creates the CRM lead with its source.
5. Routing rules assign an owner by territory.
6. The scheduler offers the right rep's calendar, and the meeting books.

How you can implement it:

• Keep form IDs unchanged, since reports and workflows reference them.
• Verify UTM parameters survive every redirect.
• Plan webhook re-validation with your CRM owner early.
• List all custom form-to-scheduler code before templates get rebuilt.
• Decide whether new lead-capture elements launch before or after cutover, then A/B test them against baseline.

See our guides on embedding an interactive demo to keep capturing leads during the transition and deciding how to gate your lead-capture assets.

Example: a sync gap that broke routing. A legal tech CRO described this:

"And then all of the territory data doesn't live in HubSpot. It lives in Salesforce, which is syncing with HubSpot, but it doesn't sync territory information."
- [CRO, legal tech]

HubSpot couldn't route leads until the sync was fixed, so check which fields each routing rule needs.

Keeping a conversational layer live while pages and forms change

Full disclosure: this is us, so weigh my view accordingly.

Forms live inside page templates, so a redesign rebuilds them. A conversational layer installed across the site works differently: it sits on top of the pages instead of inside any one template, so it can keep capturing and qualifying visitors while forms and layouts change underneath it. Because it stays constant across the old and new site, it also gives you a cleaner comparison point when the relaunch resets every other conversion baseline.

RepX, our AI sales agent, is built for this job. It greets website visitors with a conversation, runs discovery, qualifies leads on your criteria, and turns chats into meetings, with qualified leads and conversation summaries piped to HubSpot, Salesforce, or Slack.

One check still applies: confirm the install snippet is carried into the new templates and loads on every page, then run a test conversation on staging and confirm it reaches the CRM with the right source, exactly as you would for a form.

Here's where it doesn't fit. A conversational layer won't fix broken redirects or replace a form audit. If routing is broken inside the CRM itself, no front-end tool saves you, and low-traffic sites should fix their baseline first.

Website redesign checklist for launch day

Launch day should be boring. If the redirect map is done, staging is signed off, and the rollback plan is rehearsed, today is mostly verification. Launch early in the week, never on a Friday, so the full team is around for the first 72 hours.

• Freeze content publishing and CRM configuration changes 24 hours before cutover.
• Confirm the rollback environment is ready.
• Switch DNS or deploy, then confirm every top page loads.
• Remove staging authentication and any noindex tags from production.
• Spot-check your top 50 old URLs for single-hop 301s.
• Submit the new XML sitemap in Google Search Console.
• Submit test leads through every top form and confirm CRM records, routing, and bookings.
• Check GA4 real-time reports for conversion events.
• Record Day 0 values in the scorecard before end of day.

I'd also put one person in a shared channel with sales for launch day. Reps often notice missing leads before dashboards do.

The Day 0/7/30/90 recovery scorecard: track rankings and leads side by side

Rankings and leads sit in one table here, so nobody can declare victory on traffic while demo requests slide. Fill the baseline before launch.

Day 7 catches silent breaks like a dead webhook. Day 30 is the first fair read on rankings and attribution reporting, and Day 90 shows whether the redesign paid off.

Budget and timeline planning ranges for a B2B website redesign

The timelines and budgets below are illustrative scoping assumptions, not sourced benchmarks. Use them to sanity-check a plan, then replace them with your own agency or internal estimates.

Two line items get underestimated in almost every B2B website redesign plan I've seen: security review time and RevOps time to re-validate webhooks and routing. Timelines slip, so plan a phased launch. Ship your highest-traffic templates first, then roll out the rest.

Common mistakes that tank both SEO and lead flow

Most of these mistakes share one root cause: assuming someone else checked. An associate director of product marketing at a veterinary software company found stray lead forms scattered across their demos, sending leads nobody knew about.

"We need to understand all the leads that we didn't know existed. We need to delete all of these. We need to fix the experience."
- [associate director of product marketing, veterinary software]

They wanted stray forms removed and one standard form enforced. A redesign is the moment to do the same.

• Redirecting every old URL to the homepage instead of its closest equivalent.
• Removing 301s after a few months.
• Launching without a lead baseline, so nobody can prove leads dropped.
• Changing form IDs and breaking the workflows that reference them.
• Letting redirects strip UTM parameters, which turns campaign leads into direct traffic.
• Skipping the scheduler handoff test because the form itself submitted fine.
• Declaring success at Day 7 on traffic alone, before checking attribution reporting.

Frequently asked questions

How long does SEO take to recover after a redesign?

Expect rankings to wobble for a few weeks while Google recrawls old URLs and processes redirects. Day 30 is the first fair read, and Day 90 shows where you've settled. If rankings are still sliding at Day 30, check your redirect map and indexation first.

Will a redesign hurt my SEO?

It can, but most damage comes from preventable causes: missing redirects, rewritten top pages, blocked indexing, or slower templates. A redesign that keeps URLs and top-page content stable carries far less risk than a full migration.

How long should you keep 301 redirects in place?

Google recommends keeping them as long as possible, generally at least one year (Google Search Central, site moves documentation). I recommend keeping them permanently, because backlinks keep pointing at the old URLs. A 301 costs almost nothing to maintain.

How do I protect leads during a website migration?

Give lead continuity its own owner, baseline, and scorecard, separate from SEO. Test every form, webhook, routing rule, and scheduler on staging and within an hour of launch. Then track form fill rate, demo-request rate, and leads by source at Day 0, 7, 30, and 90.

Should I hire an agency for a website migration?

Hire one if your team lacks technical SEO or development capacity, or if the site is large. Keep CRM routing ownership in-house, because agencies rarely own your CRM. Whoever you hire, make the redirect map, staging crawl, and rollback plan required deliverables.

Conclusion: run your B2B website redesign without losing rankings or leads

A B2B website redesign puts two things at risk, and they fail in different ways. Rankings fail loudly, with dashboards and alerts. Leads fail quietly, in a webhook or a thank-you page that nobody retested after launch.

The fix is staffing both workstreams. Give website migration SEO its redirect map, staging crawl, and Google Search Console checks. Give leads their own owner, their own baseline, and their own rows in the Day 0/7/30/90 scorecard.

If you do one thing this week, build the baseline. Export your Search Console and GA4 data, and crawl the site with Screaming Frog. Then list every form on the site with its CRM destination and owner.

Then work through this website migration checklist in order: audit, redirect map, staging QA, rollback plan, lead-capture testing, launch, and scorecard reviews. That's how you ship without losing rankings or leads, and still have the pipeline numbers to prove the redesign worked.

Sources

• Google Search Central, Site moves with URL changes (accessed September 2026)

Want a lead-capture layer that doesn't depend on your page templates? Book a demo of Storylane RepX to keep qualifying and routing inbound leads while your site changes.