Website Redesign SEO Migration Checklist for Small Businesses

A website redesign needs an SEO migration plan when it changes domains, URLs, page structure or the way important customer journeys work. The essential process is straightforward: inventory the current site, map old URLs to relevant destinations, test the new site, launch carefully and monitor the results.

If you are changing only colours, layouts or imagery while keeping the same URLs and content structure, you may not need a full URL migration. You still need to test forms, analytics, mobile layouts, performance and accessibility. A domain change, URL change, CMS move or large content restructure deserves the fuller checklist below.

1. Decide whether this is an SEO migration

Start by documenting what will change. A redesign becomes a higher-risk migration when it includes one or more of the following:

• A new domain or a change between www and non-www
• A move from HTTP to HTTPS
• New URL paths, file extensions or directory structure
• Renamed, merged or removed service pages
• A new CMS, hosting setup or rendering system
• Changes to location pages, campaign landing pages or ecommerce paths

Google's site-move documentation treats URL changes as a controlled process: prepare and test the new site, create a URL map, configure redirects and monitor both old and new URLs.

2. Build a complete page and asset inventory

Do not rely on the navigation menu alone. Pages can receive search traffic, backlinks, referrals, bookmarked visits or campaign traffic without being prominent in the current design.

Collect URLs from your XML sitemap, analytics, Search Console, server logs if available, backlink tools and advertising platforms. Include:

• Service, product and location pages
• Contact, quote, booking and confirmation pages
• Important blog posts and campaign landing pages
• PDFs, downloads and other indexable files
• Images or resources that receive external links
• Phone, email, booking and payment links

For each item, record its purpose, organic clicks, conversions, referring sources and proposed treatment. Mark it as keep, improve, merge, redirect or retire. This turns a redesign from a visual exercise into a controlled change.

3. Create a one-to-one URL map

Your URL map should be the launch team's source of truth. At minimum, include the old URL, the new destination, the intended response and notes about any content change.

Hypothetical URL-mapping example

Old URL	New destination	Action
/old-service	/services/new-service	301 or 308 redirect
/about-us	/about	301 or 308 redirect
/outdated-promotion	No relevant replacement	404 or 410 response

Send each retired page to the closest relevant replacement, not automatically to the homepage. An unrelated destination creates a poor visitor experience and may be treated as a soft 404. Use a direct server-side redirect where a replacement exists, and avoid chains such as old URL to intermediate URL to final URL. Google's redirect guidance explains when redirects are useful and why the destination should be appropriate.

Keep the map after launch. It helps when an old URL appears in an email, advertisement, social profile or external link months later.

4. Preserve the purpose and signals of important pages

Compare old and new versions of high-value pages before release. Check:

• The page's purpose and search intent
• The main heading, title and description
• Useful service, product and location information
• Internal links to related pages
• The canonical URL
• Structured data that genuinely describes the page
• Image alternative text and surrounding context
• Phone numbers, forms and other conversion actions

Improving weak content during a redesign can be worthwhile, but changing every page, topic and URL at once makes diagnosis difficult. Preserve information that customers already use, then document substantial changes so performance shifts can be investigated later.

5. Keep staging private and testable

A staging site is useful for checking layouts, links and functionality, but it should not become a competing public version of the website. Restrict access appropriately and make sure staging URLs are not intended to remain indexed.

Before production launch, check both environments for accidental staging references. On the live site, remove temporary noindex rules or robots.txt blocks that would prevent crawling, and confirm canonical tags point to production URLs. A visual review is not enough: test actual links, forms, redirects and response codes.

6. Test the customer journey on real devices

Search visibility matters only if customers can complete the next step. Test the main journeys on desktop and mobile:

1. Find a service or product through the navigation.
2. Open the site from a representative old URL.
3. Tap the phone number on a mobile device.
4. Submit every important form using a controlled test address.
5. Confirm the submission reaches the correct inbox or CRM.
6. Check the confirmation message and any follow-up email.
7. Test booking, quote, payment and third-party links where applicable.
8. Open priority pages in more than one browser.

Test old URLs from the inventory individually. A spreadsheet can show the intended destination while the live server produces a loop, chain, incorrect status code or irrelevant page.

7. Complete launch-day checks

Immediately after release, verify:

• The intended production domain loads over HTTPS.
• Priority pages return the expected successful status.
• Old URLs redirect directly to their mapped destinations.
• Important new pages are reachable through internal links.
• The XML sitemap lists the new canonical URLs.
• Analytics and conversion tracking are active.
• Forms, phone links and booking tools work.
• The production site is not accidentally blocked from crawling.
• Images, scripts, stylesheets and fonts load correctly.

Submit the updated sitemap in Google Search Console and use URL Inspection for priority pages. Do not treat an early ranking change as proof that the migration has succeeded or failed; search systems need time to recrawl and reprocess the site.

8. Monitor for several weeks

Review Search Console impressions, clicks, indexed pages and crawl issues alongside analytics and lead records. Compare with a reasonable previous period, while accounting for seasonality, promotions and changes in advertising.

Prioritise problems that affect important pages or real customers:

• A spike in 404 responses
• Redirects leading to irrelevant pages
• Priority pages disappearing from indexing
• Forms, calls or tracking no longer being recorded
• Mobile layout or usability failures
• Slow pages caused by scripts, plugins or oversized media

Leave valuable redirects in place for the long term where practical. For a domain or URL move, Google's site-move guidance recommends keeping redirects for at least one year so users and search systems have time to transition.

When should you bring in a web professional?

A small brochure-site refresh may be manageable with a careful checklist. Get technical help before launch when the project includes a domain change, hundreds of URLs, multiple locations, ecommerce, custom applications, a CMS migration, paid landing pages or business-critical forms.

Certtech describes its web design service as custom and conversion-focused, with mobile-first websites for businesses in Barrie and Simcoe County. Its maintenance service covers ongoing areas such as monitoring, security, backups, performance and broken-link repair. Review the web design service and website maintenance service pages for the current service scope.

If you are still deciding what the redesigned site should improve, Certtech offers a free website mockup. For a project-specific conversation, you can book a 15-minute discovery call.

The practical takeaway

A successful redesign is more than a new homepage. It keeps useful URLs connected, preserves important information, protects contact paths and gives you a way to identify problems after launch.

Start with the inventory, create the URL map, test the customer journey and monitor the live site. These steps reduce avoidable disruption without promising a particular ranking, lead volume or revenue result.

Further reading: Google Search Central: Site moves and migrations and Google Search Central: Redirects and Google Search.