A small business website redesign should improve the customer experience without making a working search presence disappear. The safest approach is to treat the redesign as both a design project and a controlled site migration: inventory what exists, decide what deserves to stay, map every changed URL, test the new build, and monitor search data after launch.

That work is less glamorous than choosing colors. It is also what separates a better-looking website from a redesign that quietly loses indexed pages, backlinks, form tracking, or local visibility.

The short version: protect meaning before changing appearance

Search engines do not rank a visual design. They crawl URLs, interpret page content, follow links, process structured data, and observe whether a page appears to satisfy a searcher’s intent. A redesign can alter all of those signals at once.

Google’s site-move documentation recommends preparing the new site, creating an old-to-new URL map, implementing redirects, checking canonicals and robots rules, testing, and submitting the new sitemap. Even when the domain stays the same, the same discipline is useful whenever page paths or site structure change.

Use the checklist below to keep those changes controlled.

Before the redesign: establish what you already have

1. Record the search baseline

Open Google Search Console and record the last three to six months of:

  • Clicks and impressions by page
  • Queries that produce meaningful visibility
  • Pages with strong click-through rates
  • Indexed and non-indexed URL counts
  • Core Web Vitals or HTTPS issues
  • Sitemap status and crawl errors

This is not busywork. Without a baseline, a normal post-launch fluctuation can look like a crisis—or a real loss can go unnoticed.

Search Console’s Performance reports let you filter by query, page, country, device, and search type. Export the data before launch so the old-site view is easy to compare later.

2. Build a complete URL inventory

Do not rely on the navigation menu. A website may contain landing pages, old articles, campaign URLs, PDFs, thank-you pages, and orphaned pages that are absent from the main navigation but still receive links or search visits.

Combine several sources:

  • The current XML sitemap
  • A crawl of the public website
  • Search Console’s indexed-page data
  • Analytics landing pages
  • Backlink reports, if available
  • URLs in active ads, email sequences, social profiles, and business listings

Give every URL a disposition: keep, improve, merge, redirect, or retire with a true 404/410.

3. Identify pages with value before cutting content

A page may look dated and still carry search value. Before removing it, ask:

  • Does it receive organic visits or impressions?
  • Does it rank for a relevant query?
  • Do other websites link to it?
  • Does it answer a customer question better than another page?
  • Is it part of an important conversion path?

Preserve the useful purpose of the page even if the design, wording, or URL changes. Combining overlapping pages can be sensible; deleting them because they are visually inconvenient is not a strategy.

4. Map old URLs to the most relevant new URLs

Create a simple redirect sheet with four columns:

Old URL New URL Action Reason
/old-service/ /services/current-service/ 301 redirect Same service, improved page
/two-thin-pages/ /complete-guide/ 301 redirects Consolidated intent
/expired-event/ None 410 or 404 No relevant replacement

Avoid sending every retired page to the homepage. Google explicitly warns against irrelevant bulk redirects because they confuse visitors and may be treated as soft 404s.

5. Preserve business-critical evidence

Capture the content and context that establishes trust:

  • Accurate service descriptions
  • Staff and founder information
  • Licenses or credentials that can be verified
  • Original project photographs
  • Review-source links
  • Policies, guarantees, and service-area details
  • Contact information and hours

A redesign should clarify real proof, not replace it with generic claims or fabricated counters.

During the build: make the new site understandable

6. Give every important page one clear search purpose

A page should answer a recognizable customer need. A service page about roof repair, for example, should explain repair situations, the service process, local constraints, and the next action—not divide attention between every service the company offers.

Use one descriptive H1, a logical heading hierarchy, concise title text, a unique meta description, and internal links that explain where they lead. Google’s SEO Starter Guide emphasizes making content easy for both people and search engines to understand.

Navigation is only one part of internal linking. Connect related pages in context:

  • Service pages to relevant service-area pages
  • Articles to the service they support
  • Case studies to the capability they demonstrate
  • About and proof pages to contact or preview paths
  • Broad guides to more specific explanations

Use descriptive link text. “Learn about our website care plans” communicates more than “click here.”

8. Keep the mobile experience complete

Do not hide essential proof, service detail, or contact options simply to make the mobile page shorter. Reorder and simplify instead.

Check at minimum:

  • Mobile navigation and dropdowns
  • Heading wrapping
  • Image crops
  • Forms and validation
  • Tap targets
  • Sticky elements
  • Tables and long URLs
  • Horizontal overflow
  • Footer and legal links

9. Build performance into the design

Large hero images, multiple font families, autoplay video, and unnecessary JavaScript can make a polished page feel slow. Set image dimensions to prevent layout shifts, use modern formats, lazy-load below-the-fold imagery, and keep interactive code proportional to the job it performs.

Performance is not a reason to make a bland website. It is a reason to make every asset earn its cost.

10. Carry measurement and form behavior forward

Confirm that the redesign preserves or intentionally replaces:

  • Analytics and tag-manager configuration
  • Form destinations and notification emails
  • Phone and email link tracking
  • Thank-you pages
  • Ad conversion events
  • Cookie or consent behavior, where required
  • Search Console verification

Submit test forms from desktop and mobile. A form that looks finished but never delivers the lead is a launch-blocking defect.

At launch: verify the technical handoff

11. Test redirects before changing the domain or production build

Every changed URL should return one clean permanent redirect to a relevant, working destination. Look for:

  • Redirect loops
  • Multi-hop redirect chains
  • Redirects to missing pages
  • HTTP-to-HTTPS inconsistencies
  • Old internal links that still rely on redirects

Redirects protect external links and saved bookmarks, but your own navigation should point directly to the final URLs.

12. Check canonicals, indexing rules, and the sitemap

Staging sites are often protected with noindex. That protection must not survive the production launch.

Verify that:

  • Each indexable page has a self-referencing production canonical
  • No important page carries an accidental noindex
  • robots.txt does not block required content
  • The XML sitemap contains the preferred canonical URLs
  • Retired or redirected URLs are absent from the new sitemap
  • The sitemap uses the correct HTTPS production domain

Google recommends using fully qualified canonical URLs in sitemaps and submitting the sitemap through Search Console when appropriate.

13. Crawl the production site as a user would experience it

Test every meaningful route after launch. Check status codes, headings, images, links, forms, mobile overflow, console errors, and metadata. Then inspect representative pages visually; source-code validation cannot tell you that a mobile heading has become unreadable or an image crop obscures the subject.

14. Submit and monitor—without repeatedly changing everything

Use Search Console’s URL Inspection tool for a small number of important changed pages and submit the new sitemap. Google’s recrawl guidance notes that crawling can take days to weeks and that requesting a crawl does not guarantee immediate inclusion.

Monitor:

  • Indexed-page changes
  • Important query and landing-page performance
  • 404 and redirect errors
  • Branded versus non-branded visibility
  • Form and phone conversions
  • Page experience issues

If a priority page declines, compare the old and new intent, content, internal links, metadata, and redirect behavior before making broad changes.

A practical redesign launch checklist

  • Export Search Console and analytics baselines
  • Inventory all public URLs and important assets
  • Classify every URL: keep, improve, merge, redirect, or retire
  • Map every changed URL to a relevant destination
  • Preserve verified proof and business information
  • Assign one primary purpose to each important page
  • Rebuild contextual internal links
  • Test mobile layouts, forms, and navigation
  • Confirm analytics and conversion tracking
  • Validate redirects, canonicals, robots rules, and sitemap URLs
  • Crawl and visually inspect the production build
  • Submit the sitemap and monitor priority pages

When should a small business get help with a redesign?

Outside help is useful when the existing site has years of content, meaningful search traffic, multiple service areas, paid campaigns, or no reliable URL inventory. It is also useful when the person leading the redesign cannot independently test the build.

BizScribe’s website design work treats search preservation, content, and conversion as parts of the build—not post-launch add-ons. If you are still deciding whether the current site needs a reformat or a full rebuild, see a free homepage preview before committing to a direction.

Common questions about redesign SEO

Will a website redesign always hurt rankings?

No. A redesign can improve visibility when it creates clearer content, faster pages, stronger internal links, and a better experience. Risk rises when URLs, useful content, metadata, or crawl rules change without a migration plan.

Should every old page be redirected?

Only when there is a relevant replacement. Redirect useful legacy URLs to the closest equivalent. Let truly obsolete content return a proper 404 or 410 instead of misleading visitors with an unrelated destination.

How long should permanent redirects remain?

Google recommends keeping site-move redirects for at least one year and notes that keeping them longer can continue to help users. For stable business URLs, leaving relevant redirects in place indefinitely is often the simpler choice.

How can I tell whether Google indexed the new pages?

Use Search Console’s Page Indexing report for the site-wide view and URL Inspection for a specific page. A site: search can be a quick directional check, but Search Console is the better diagnostic source.