Website Redesign Planning Checklist: Protect SEO, Content, and Conversions

Overview

Redesigning a business website is more than replacing a theme or rearranging page sections. A redesign may change URLs, navigation, page titles, structured content, forms, analytics, hosting, DNS settings, and the way visitors complete important tasks. Treat it as a controlled change to a working system rather than a purely visual project.

Before work begins, define what must be preserved and what should improve. Important items usually include organic landing pages, contact forms, phone links, booking flows, product or service pages, business email, conversion tracking, accessibility, and page performance. Record the current state so the new site can be compared against something concrete.

Use this checklist for a visual refresh, CMS change, theme replacement, domain change, or migration to new hosting. Keep one shared working document with an owner, status, notes, and verification date for each task.

Checklist by scenario

Before any redesign

• Define the scope: Record whether the project changes the design, CMS, hosting, domain, URL structure, content, forms, or all of these.
• Capture a baseline: Save recent analytics, search performance reports, top landing pages, conversion numbers, page-speed observations, and uptime notes. Use a consistent date range when comparing the old and new site.
• Inventory the site: Export or manually list every indexable URL, including service pages, blog posts, location pages, downloads, images that receive traffic, and useful legacy pages.
• Record ownership and access: Confirm access to the domain registrar, DNS provider, hosting account, CMS, analytics, search tools, tag manager, email platform, SSL settings, and backup system.
• Create a backup: Keep a tested copy of the database, files, media, configuration, and any custom code. A backup that has never been restored should not be treated as the only recovery plan. See the website backup and restore testing guide.

When changing URLs or content

• Classify each old URL: Mark it as keep, update, merge, redirect, or retire. Base the decision on relevance, links, traffic, conversions, and whether the content still serves a real need.
• Build a redirect map: Create a table with the old URL, new URL, action, reason, owner, and verification status. Redirect each changed page to its closest useful replacement, not automatically to the homepage.
• Review page purpose: For every important page, identify its target audience, primary question, call to action, title, heading structure, internal links, media, and contact details.
• Protect valuable content: Do not remove a page solely because it is old or visually outdated. First decide whether it should be refreshed, combined with another page, or redirected to a genuinely relevant resource.
• Check internal links: Update navigation, breadcrumbs, calls to action, related content, image links, downloadable files, and canonical references after the new URL structure is final.

Before launch on staging

• Prevent accidental indexing: Keep the staging environment private or use an appropriate noindex approach while testing. Remove temporary restrictions only as part of the launch procedure.
• Test key journeys: Submit contact forms, complete bookings or purchases, click phone and email links, download files, use menus, search the site, and test any account or quote workflow.
• Check responsive layouts: Review representative pages at narrow and wide viewport sizes. Look for clipped text, overlapping controls, hard-to-tap buttons, unreadable contrast, and menus that cannot be closed.
• Review accessibility basics: Check keyboard navigation, visible focus, heading order, form labels, alternative text, link purpose, contrast, error messages, and motion settings where relevant.
• Verify technical settings: Confirm the preferred domain, HTTPS, canonical URLs, robots directives, XML sitemap, redirects, 404 behavior, favicon, metadata, and structured content where used.
• Compare performance: Test important templates rather than only the homepage. Compress oversized media, remove unnecessary scripts, and confirm that caching and hosting settings work as expected. Use the website speed optimization workflow for a repeatable review.

At launch and immediately after

• Take a final backup of the old site and the release candidate.
• Apply redirects and confirm the live DNS, hosting, SSL, and email configuration.
• Remove staging-only restrictions and submit the live sitemap through the site’s normal search-management workflow.
• Test forms, notifications, tracking events, analytics, payment or booking paths, and important links from a clean browser session.
• Inspect a sample of old URLs and new URLs manually. Confirm that changed addresses resolve to the intended destination and do not create redirect chains.
• Monitor uptime and errors during the first several days. A written incident review process can help identify patterns; see the small business uptime monitoring guide.

What to double-check

URL and redirect mapping: The redirect spreadsheet is one of the most important redesign documents. Look for old URLs that return errors, redirect to unrelated pages, point to another redirect, or lose important path information. Check both pages that receive traffic and pages linked from external sources.

Analytics continuity: Confirm that the same measurement property or an intentionally documented replacement is installed on every relevant template. Compare visits, landing pages, form submissions, phone clicks, purchases, and other primary events using comparable periods. A redesign can make numbers look lower simply because a tag or event stopped working, so investigate tracking before interpreting performance.

Search controls: Review titles, descriptions, headings, canonical references, robots directives, sitemap entries, and internal links. Ensure that staging settings have not reached production and that production settings do not block important pages. Search visibility may take time to settle, but technical errors should be addressed immediately.

Forms and notifications: Send test submissions through every form and confirm delivery to the correct mailbox or CRM. Test validation, required fields, confirmation messages, spam protection, and mobile use. Check that business email remains operational when DNS or hosting changes are part of the redesign. The DNS troubleshooting guide covers common website, email, and SSL checks.

Conversion paths: A clear design is not enough if visitors cannot take the next step. Test calls to action from landing pages, navigation, footer links, contact details, and service pages. Record the expected result for each path, such as a thank-you page, confirmation email, calendar entry, or completed transaction.

Common mistakes

• Starting with design before inventory: This makes it easy to overlook useful pages, downloads, integrations, and high-value entry points.
• Redirecting everything to the homepage: A broad redirect can remove context and make it harder for visitors to find the information they requested. Map pages to the closest relevant destination.
• Testing only the homepage: Errors often appear in templates for forms, posts, product pages, location pages, or mobile menus. Test representative examples from every important template.
• Forgetting non-visual assets: Check PDFs, images, feeds, scripts, webhooks, APIs, tracking tags, email notifications, and embedded services, not just visible page content.
• Launching without a rollback plan: Keep a restorable backup, document the previous configuration, and decide who can revert changes if a critical issue appears.
• Comparing unlike data: Use consistent date ranges and account for seasonality, campaigns, tracking changes, and differences in consent or measurement settings before drawing conclusions.
• Leaving maintenance until later: Update the site’s maintenance schedule, backup checks, security reviews, and ownership records once the redesign is complete. The website maintenance checklist can provide a recurring framework.

When to revisit

Revisit this checklist before every major redesign, rebrand, CMS migration, hosting move, domain change, or theme replacement. It is also useful before seasonal campaigns when landing pages, forms, offers, or tracking are likely to change. Review the inventory when a key service is added, removed, renamed, or moved to a new URL.

Tools and interfaces change, so confirm that your analytics, search-management, hosting, backup, and accessibility workflows still match the current setup. Do not rely on an old checklist without checking whether account permissions, deployment steps, DNS records, or testing environments have changed.

For a practical final pass, assign each task an owner and due date, complete the URL map, take and test a backup, run staging tests, record baseline measurements, and schedule post-launch checks for the first day, first week, and first regular reporting cycle. Keep the completed document with the site’s technical records. It will make the next redesign safer, faster, and easier to verify.