Small Business Website Relaunch Checklist

A website relaunch is a change to a live customer and search system. It can improve clarity and conversion, but it can also break forms, remove useful pages, lose analytics, or publish inaccurate information if launch work is treated as a final design handoff.

Use this checklist to define what must be protected, what should improve, and how the team will verify the new site.

Set the relaunch goals

Write the outcomes before choosing a template or design direction. Goals may include faster pages, clearer services, stronger mobile conversion, easier content editing, a new booking flow, an integration, or a change in brand.

Choose measurements for each goal. “Modern” is a design preference; “more completed booking requests with the same response quality” is an outcome.

Inventory what exists

Collect current URLs, titles, descriptions, analytics, Search Console data, forms, redirects, external links, PDFs, images, integrations, domains, hosting, and account owners. List pages that receive traffic, leads, links, or customer questions even if they are not in the navigation.

Mark each item keep, improve, combine, redirect, archive, or remove. Do not delete a page merely because it looks old; determine whether it still serves a useful purpose.

Protect ownership and access

Before launch, confirm that the business can access the domain registrar, DNS, hosting, code, analytics, Search Console, email, forms, CRM, payment, booking, and third-party accounts. Record recovery contacts and remove former users.

A relaunch is a good time to correct ownership gaps, but do it deliberately so DNS and email are not interrupted.

Plan the URL and redirect map

Keep useful URLs stable when possible. For changed URLs, map each old page to the closest useful new destination. Avoid sending every old page to the home page or creating chains of redirects.

Check canonical tags, internal links, XML sitemap coverage, robots rules, and redirect behavior before launch. The guide on website migration without losing SEO covers the search side of this work.

Rebuild the conversion path

Every form, phone number, chat, booking, quote, purchase, and download should have an owner, destination, confirmation, and test. Carry page, service, product, source, and customer context into the record when it helps the response.

Test the full path with a real or safely masked request. Verify the browser, server, notification, CRM, assignment, follow-up, analytics, and staff view. A new thank-you page is not enough.

Review content and proof

Make the new site accurate about services, hours, pricing, policies, locations, staff, photos, and response expectations. Remove copied or expired content. Link related pages so the customer can continue from an explanation to the next decision.

Test mobile, accessibility, and speed

Review the site with keyboard navigation, a screen reader where possible, a slower connection, small screens, large text, and zoom. Check labels, focus, contrast, headings, alt text, error messages, touch targets, and form completion.

Measure performance with real media and third-party tools enabled. Image galleries, chat, maps, booking widgets, and analytics can change the page materially.

Run a staging acceptance test

• Every important page loads at the expected URL.
• Navigation, search, internal links, redirects, and downloads work.
• Forms deliver the correct context to the correct owner.
• Analytics and conversion events are present once, not multiple times.
• Metadata, sitemap, robots, canonical, and structured content are correct.
• Broken, empty, expired, sold, or unavailable states are honest.
• Backups, rollback, monitoring, and launch contacts are ready.

Launch with monitoring

Choose a launch window when someone can monitor forms, calls, bookings, errors, DNS, email, search coverage, and important pages. Keep the previous site or a recoverable deployment available until the new site proves stable.

Review the first days and weeks with evidence. Watch for lost leads, 404s, crawl changes, performance regressions, tracking errors, and customer confusion.

Document the new normal

Give the business a short runbook with content owners, account access, form tests, update process, support contacts, backup and rollback instructions, and the date of the next review.

A successful relaunch is not only a better-looking site. It is a site the business can own, operate, measure, and improve without losing the assets that already work.