A redesign is the moment your site is most exposed. For a small US B2B firm that depends on Google to bring in quote requests, the risk isn't only lost traffic. It's broken search paths: the URLs, internal links, and crawl signals that let Google find and trust your service pages. This website redesign seo checklist walks through what to capture before you touch the design, what to map while you build, and what to verify after launch. It won't promise that rankings stay exactly where they are. No honest checklist can. What it will do is reduce the number of avoidable ways a rebuild can cost you visibility.

Start With a Baseline You Can Compare Against

You can't tell what a redesign broke if you never wrote down what worked. Before anyone opens a design tool, capture the current state of your search presence.

Pull a crawl of the existing site. A free crawler will do for a site under a few hundred pages. Export the list of URLs that return a 200 status, plus titles, meta descriptions, and H1s. Save it as a spreadsheet; you'll use it as your source of truth later.

Then layer in performance data. In Google Search Console, export the last 12 months of queries, pages, and clicks. Sort by clicks and note your top 20 landing pages. These pages already attract search visits; check your inquiry data before calling them the pages that earn leads. Give them careful treatment in the migration.

Also note which pages attract links. If you use a backlink tool, export referring domains per URL. If you don't, at least list the pages you know other sites cite — a supplier directory, a trade association, a partner's resource page.

One more thing: decide what "working" means for you. A small B2B site might run on 40 pages, with 6 service pages and a handful of case studies. That's a manageable scope, and it means you can be thorough rather than selective.

Set Realistic Objectives Before You Brief Anyone

Redesign projects drift when the goal is "make it look better." Give the project measurable targets so you can judge whether the migration held up.

Reasonable objectives for a small B2B firm:

  • Maintain crawlable, working URLs or relevant redirects for service pages, then monitor their indexing status.
  • Compare post-launch organic sessions for important landing pages with a documented pre-launch baseline; investigate material changes.
  • Improve page experience signals on the pages that already convert.
  • Monitor crawl errors and resolve persistent new ones.

Notice what's missing: a promise to rank higher after launch. A redesign is a technical change, not a content strategy. If you want more traffic, that's a separate job, and it's worth treating it as one. If you're planning a broader search program alongside the rebuild, see our notes on SEO services for how content and technical work usually split.

Phase 1: Pre-Launch Audit and URL Inventory

This is the phase most small teams skip, and it's the one that saves them.

Build a full URL inventory

Crawl the live site and record every indexable URL. For each one, add four columns: current URL, page type (service, case study, blog post, contact), monthly organic clicks, and referring domains. This becomes your migration map.

Identify your money pages

Mark the pages that generate inquiries. On a B2B site these are usually service pages, capability pages, and a contact or request-a-quote page. These get priority in redirect mapping and post-launch checks.

Flag thin or duplicate pages

If you have three near-identical pages about the same service, consolidation is reasonable during a redesign. But consolidation means deciding where the old URLs should point, updating internal links to the surviving URL, and checking for orphaned references, not just deleting pages. A removed page with no redirect is a dead end for both users and crawlers.

Check what's crawlable now

Confirm your current internal links use real anchor elements. Google's guidance on link best practices is blunt about this: Google generally can only follow a link if it's an <a> element with an href attribute. If your navigation relies on JavaScript click handlers, fix that in the new build rather than carrying the problem forward.

Phase 2: Map Old URLs to New Ones

The redirect map is the single most important artifact of the whole project. Build it in a spreadsheet before development starts, and hand it to whoever configures the server.

Old URL New URL Page type Redirect Priority
/services/cnc-machining /services/cnc-machining/ Service 301 High
/capabilities.html /capabilities/ Capability 301 High
/blog/2019-old-post /blog/updated-topic/ Blog, if the content genuinely replaces it 301 Review
/contact-us.php /contact/ Contact 301 High

A few rules that keep the map clean:

One hop only. Point every old URL directly at its final destination. Chains like A → B → C add hops and make debugging harder.

Redirect to the closest match. If a page has no equivalent, send it to the most relevant surviving page, not the homepage. A sitewide "everything to home" pattern tells Google nothing about where the content went.

Use permanent redirects for permanent moves. Google's documentation on redirects explains that permanent redirects signal the target should be treated as canonical, while temporary ones keep the source page in search results. For a redesign, you want the permanent kind.

Keep the map after launch. You'll want it when you audit 404s in week three.

Phase 3: Prepare the Staging Environment

Your new site will live somewhere before it goes live. Make sure that somewhere can't be indexed.

Protect staging with a password where possible. If the staging pages must be public for review, use a noindex directive on each page and verify it in the HTML response. Do not rely on robots.txt alone to prevent indexing: as Google explains in its noindex guidance, a blocked URL can still be known to Google, and a crawler blocked from the page cannot see its noindex tag. Document how staging controls will be removed from the live build. The classic failure is blocking the staging site correctly, then forgetting to remove the block when the site moves to the live domain — or the reverse, where a noindex tag ships to production and quietly removes your pages from search.

Test on staging before launch: internal links resolve, forms submit, the redirect map works against a test hostname, and the mobile layout holds up. If you're working with a developer or an agency, hand them the URL map and the crawlability requirements in writing. Vague briefs produce vague migrations. Our website design page explains the buyer questions and website scope to discuss before a build.

Phase 4: Launch Day

Launch is a sequence, not a single switch. Work through it in order.

  • Remove any noindex tags and staging blocks from the production build.
  • Deploy the redirect map and test a sample of 20–30 old URLs with a redirect checker.
  • Confirm the preferred domain and HTTPS version resolve consistently.
  • Verify the new site in Google Search Console as a property. For a domain move, follow Google's full site-move checklist, including Change of Address when applicable; property verification alone is not a migration plan.
  • Submit the new XML sitemap.
  • Check robots.txt on the live domain — it should allow crawling and reference the sitemap.
  • Confirm analytics is firing on the new pages before you need the data.

If you're changing domain and design at the same time, consider splitting the work. Google's guidance on site moves with URL changes recommends changing one thing at a time and timing the move to coincide with lower traffic periods. For a small B2B site with seasonal inquiry patterns, that's practical advice, not theory.

If the domain changes, check Google's domain-move instructions to see whether the Change of Address tool applies to your move. Include that step in the migration plan rather than assuming every redesign needs it.

Phase 5: Post-Launch Monitoring

Problems can surface after launch as the new URLs are crawled. Schedule repeated checks over the following weeks; watch these areas.

Index coverage. In Search Console, check the Pages report at launch and again as crawling progresses. New "Not found (404)" entries usually mean a redirect is missing. "Excluded by noindex" means a tag shipped by mistake.

Redirect health. Re-crawl the new site. Any internal link pointing at an old URL should be updated to the new URL directly, not left to bounce through a redirect.

Performance data. Compare clicks and impressions with a pre-launch baseline over a comparable period. If a prior-year period is available and seasonal demand matters, use it as another reference; do not draw a conclusion from a single week.

404 log. Review server logs or Search Console reports for 404s on a regular schedule. Fix the ones that matter — pages with incoming links or prior traffic.

Site search and forms. Confirm inquiry forms still deliver. A working search presence with a broken contact form is a worse outcome than a small ranking dip.

Expect some fluctuation. Google's documentation on site moves notes that crawling and indexing take time to settle, and that larger moves take longer to process. There is no fixed recovery window, and anyone quoting one is guessing.

Common Mistakes That Cost Small B2B Sites Traffic

  • Redirecting everything to the homepage instead of mapping pages individually.
  • Leaving redirect chains that force crawlers through three hops.
  • Shipping noindex tags from staging to production.
  • Deleting thin pages without redirects.
  • Changing the domain, the CMS, and the design in one weekend.
  • Forgetting to update internal links, so every menu click passes through a redirect.
  • Losing the old analytics property, which makes before-and-after comparison impossible.

Most of these are process failures, not technical mysteries. A written checklist prevents them.

Frequently Asked Questions

How do I redirect old URLs to new ones without losing SEO value?

Build a one-to-one map from every old URL to its closest new equivalent, then implement permanent redirects. Google's documentation explains that permanent redirects tell Google the target should be treated as canonical, which is what you want when a page has genuinely moved. Avoid chains and avoid sending unrelated pages to the homepage. Test a sample of URLs after deployment. You can reduce loss, but you can't guarantee rankings transfer exactly — Google still needs to recrawl and reprocess the new URLs.

What should I check in Google Search Console after a redesign?

Verify the new property, submit your sitemap, and watch the Pages report for new 404s and unexpected noindex exclusions. Check that the preferred domain and HTTPS version are consistent. Monitor the Performance report against a documented pre-launch baseline over a comparable period, accounting for seasonal demand where relevant. Fluctuation is normal in the first weeks while Google recrawls.

How long does it take for SEO to recover after a website redesign?

It varies with site size, crawl rate, and how much changed. Google's site move guidance notes that the process takes time and that larger moves take longer to process. Even with a clean redirect map, the time needed to recrawl and process changed URLs varies. There is no reliable fixed recovery timeline. Track trends, not daily numbers.

Do I need to keep my old content on the new site?

Review any page with organic traffic or inbound links before removing it, even if the design feels dated. Audit each page for clicks and referring domains before deciding. If an equivalent or genuinely relevant replacement exists, redirect to it and update internal links. If there is no useful replacement, a true 404 or 410 is more honest than an unrelated redirect.

How do I set up a staging site without it being indexed?

Use password protection where possible. For publicly accessible staging pages, use noindex and verify the directive can be crawled. A robots.txt disallow by itself does not guarantee that the staging URL stays out of search results. Make removal of staging controls an explicit launch-day check. The most common error is leaving a noindex tag in place after the site goes live.

Sources

If you'd rather hand the migration to someone who does this regularly, our website design and SEO work covers both sides of a rebuild — the build and the search paths that keep it findable.