A successful website redesign starts before anyone chooses colors or opens a design tool. First preserve the pages, enquiries and information that already work. Then agree on how the new experience should help customers and how the team will verify it at launch. This 24-point checklist is written for small-business owners, marketing managers and the agency responsible for delivery.
Still deciding whether you need a refresh, redesign or full rebuild? Read our redesign vs. rebuild decision guide first. This guide assumes you have chosen to move forward and need a practical process, a shared handoff list and a way to avoid losing valuable search visibility or customer enquiries.
Before the redesign: document what you cannot afford to lose
Start with a snapshot of today's website. The goal is to record facts before your new design changes the baseline. One spreadsheet can hold the URL inventory, assigned owner, action, redirect destination and test result.
- Write down the business outcome. Define the action the website should make easier: qualified calls, estimate requests, appointment bookings or purchases. Add a measurable baseline instead of an unverified promise to “increase conversions.”
- Export the current URL list. Include service, location, pricing, blog and landing pages. Gather URLs from the CMS, XML sitemap, analytics and Google Search Console, not just the visible navigation.
- Identify valuable existing pages. Mark pages that receive organic clicks, backlinks, enquiries or meaningful referral traffic. Those URLs deserve deliberate retain, improve, consolidate or redirect decisions.
- Record search and enquiry baselines. Save recent Search Console queries, landing-page impressions and clicks; note form submissions, phone clicks and booked appointments where your tracking supports them. Compare like-for-like periods later.
- Inventory forms and integrations. Record the exact destination for each enquiry: email address, CRM pipeline, calendar, webhook or shared inbox. Note who owns access and who will test it.
- Assign content and approval owners. Decide who supplies service descriptions, legal statements, photos, testimonials with permission, pricing, logos and final sign-off. Missing content can block a launch long after the design is complete.
While planning: design around the questions customers actually ask
Website design is not just a homepage exercise. A person searching for a specific service may enter on an interior page, compare price or timing, then decide whether to contact you.
- Map the important visitor journeys. For each priority service, write the questions visitors need answered, the trust signals they can verify and the most natural next action.
- Agree on an information architecture. Decide which pages are essential and how people will reach them from navigation and contextual links. Avoid creating near-duplicate city pages simply to expand a sitemap.
- Preserve useful content. Keep accurate answers, project proof and established explanations while rewriting confusing copy. A shorter page is not automatically a better page if it removes information customers rely on.
- Design the mobile experience first enough to test it. Check readable typography, line lengths, menu behavior, tap targets, form inputs and sticky elements on narrow devices, not only an oversized desktop mockup.
- Check accessible navigation and forms. Use keyboard navigation, visible focus, meaningful labels, readable contrast and understandable form errors. The W3C accessibility quick checks provide a useful manual starting point; an automated score alone is not a complete accessibility review.
- Define each conversion event. Decide what counts as a successful enquiry and where it will be recorded. If the business uses a CRM, specify the owner, routing rules, notifications and test-submission procedure before development.
Before launch: validate technical SEO, performance and functionality
These checks belong on a private preview or staging environment. Work through them as an acceptance test, then verify them again on the actual production pages.
- Prepare a URL disposition and redirect map. Leave valuable URLs unchanged where practical. If a path must change, send it with a relevant server-side permanent redirect to its closest replacement. Google warns against funneling unrelated old pages to a generic homepage; use its site migration documentation when mapping changes.
- Check titles, headings and canonical tags. Every published page needs a distinct purpose, a readable title, one primary heading and the intended canonical URL. Avoid redirect chains and conflicting canonical signals.
- Validate internal links, images and structured data. Check menus, CTA buttons, breadcrumbs, image loading, sitemap entries and any schema against the visible page facts. Do not carry fictional ratings, addresses or office locations into the new site.
- Test loading, interaction and layout stability. Use Lighthouse for repeatable lab tests and Search Console field data where it exists. Google's Core Web Vitals guidance focuses on loading, responsiveness and visual stability; check both mobile and desktop.
- Run end-to-end lead tests. Submit a real test request from a mobile device. Verify that the email arrives, CRM contact is created, correct pipeline is selected, automation does not duplicate messages and the thank-you state displays correctly.
- Check indexability separately on staging and production. Private preview pages should not accidentally enter search results. Just as importantly, a staging noindex rule, password gate or robots restriction must not carry onto the live pages intended for indexing.
Launch and the following 30 days: measure the handoff
A successful deployment is the beginning of the observation period. It is not proof that traffic, indexing and forms are working as expected for every visitor.
- Verify live critical pages. Open the homepage, highest-value service pages, key location pages, pricing, contact and several articles from a phone and a desktop browser. Check page titles, images, menu items and CTA links.
- Test every changed URL and redirect. Confirm old URLs point to the right new page without a loop or chain. Check that pages removed intentionally return an appropriate status rather than a misleading soft 404.
- Inspect the sitemap and production indexing settings. The XML sitemap should list current canonical URLs; production pages meant to rank should not remain noindexed. Inspect representative URLs in Search Console.
- Verify analytics and lead attribution. Compare your event list to actual test events. Confirm you can distinguish organic search visitors and their enquiries from paid traffic where consent and analytics settings allow it.
- Monitor Search Console and customer reports. Review indexing, important queries, landing-page trends, redirects and the leads your team actually received. Some ranking fluctuations can happen during substantial migrations; avoid drawing conclusions from a single day's position.
- Keep a post-launch issue log with an owner. Record broken paths, unexpected layout behavior, missed form notifications, accessibility issues and CMS training questions. Prioritize problems that block customers before cosmetic changes.
The one-page website redesign handoff checklist
Before marking the project complete, request evidence—not just a statement that the design is finished. This short handoff table gives owners and agencies a common definition of “ready.”
| Deliverable | What to request | Who verifies it |
|---|---|---|
| Page inventory | Current and new URLs, retained content, deleted pages and redirect destinations | Website owner + developer |
| Search protection | Canonical checks, sitemap, production indexability and Search Console access | SEO owner + developer |
| Customer journey | Mobile menu, service pages, form labels, contrast and main CTAs tested | Marketing owner + QA |
| Lead delivery | Successful end-to-end form, booking and CRM test submissions | Sales owner + developer |
| Ownership | Domain, hosting, CMS, analytics, backups, licenses and admin access documented | Business owner |
| Follow-up | Named issue owner and 7-day / 30-day review checkpoints | Project lead |
What a website redesign should include in the proposal
Ask for a written scope that identifies the pages, templates, content migration, mobile states, SEO preservation work, form integrations, test responsibilities, launch plan and post-launch support. A redesign may be lighter than a full rebuild, or more involved if the current site has complex integrations or an extensive content history.
For a starting point on custom project investment, see Tide & Type's published website design packages. Those are package starting prices, not an automatic quote for every redesign or SEO migration. If you need a partner for both the experience and implementation, explore our website design and development services and our technical SEO approach. The final scope should reflect your actual website rather than a generic checklist.
Ready to plan a redesign? Share your current website and book a discovery conversation. We can work through what to keep, what needs improvement and what a realistic launch handoff should cover—without claiming guaranteed search positions or lead volume.
