Website Redesign Checklist: The Workflows That Break After Launch

Most website redesign projects start with what everyone can see. The site looks dated. Mobile navigation is awkward. Service pages have drifted apart. The company wants a cleaner brand.

Those are valid problems. They are also the easy ones to spot, which is why they tend to fill the whole brief.

The harder part starts after a visitor takes action. Where does a quote request go? Does the CRM know which page produced it? Can a qualified lead book a meeting without three emails? What happens if a payment fails? Can the marketing team tell whether the lead came from search, an ad or a referral?

A redesign that ignores those questions can leave the business with a better-looking website and the same manual work. It can also break the lead tracking the old site had, so nobody can prove whether the new design is performing.

This is a website redesign checklist for that overlooked layer: the forms, CRM records, booking rules, payment outcomes and conversion tracking that turn a visit into revenue. It is written for business owners and marketing leads planning a redesign, and for the developers who have to make those systems talk to each other.

Key takeaway: Before a redesign, list every action a visitor can take, decide which system each action must reach and who owns it, then test every path end to end before launch. Pages are what visitors see. Workflows are what the business runs on.

Map the handoff before designing the form

A contact form is the first handoff between the website and the people who have to respond.

Before rebuilding it, write down what staff need to know. A contractor may need service type, ZIP code and project timing. A law firm may need to separate new matters from existing clients. A property company may need to attach a building or listing ID.

Then decide where that information should go.

For a company using a CRM, a useful website inquiry can create or update a contact, record the source, save the requested service and assign the right person. That is why the form is best designed backward from the CRM record: the fields, required values and hidden source data follow from what the record needs, not from what looks tidy on the page.

This does not require collecting twenty fields. Long forms often make the experience worse. The goal is to capture only the information that changes what happens next.

Calculators follow the same rule. A savings or quote calculator already holds the visitor’s own numbers, so those values should travel into the CRM with the contact details instead of vanishing when the result screen closes. Our walkthrough on building an HSA savings calculator for Canadian business websites shows this in practice, passing the province, team size and estimate into the lead record so the first sales call starts from real figures.

Scheduling rules belong in the build

Adding a calendar widget is easy. Deciding who should see which calendar is more important.

Some businesses can let any visitor book immediately. Others need qualification first. A consultation may be available only in certain territories, require a deposit or need a buffer between appointments. The website should reflect those rules instead of asking staff to fix scheduling mistakes later.

Test calendar sync in both directions, too. If the online booking tool cannot see appointments added directly in a staff calendar, it will sell the same slot twice. And when customers book from a different time zone than the team, confirm that the time shown on the page, in the confirmation email and in the staff calendar all match.

The same applies to phone calls and messaging. A multi-location company may route calls by market. After-hours inquiries may go somewhere different. WhatsApp, SMS and chat need an owner; adding another button without deciding who responds only creates another inbox.

Payments have more than one outcome

When a website takes deposits, consultation fees or full payments, the successful checkout is only one outcome.

A useful redesign accounts for failure, cancellation and refund paths too. The site may need to hold a reservation after payment, release inventory if payment fails, send a receipt, create an account or notify a staff member.

Build those steps on the payment processor’s server-side confirmation, usually a webhook, rather than on the customer returning to a thank-you page. People close tabs, lose signal and hit the back button. If a reservation is only saved when the browser comes back, some customers will pay and still have no booking.

These steps are part of the customer experience even though they happen after the card form disappears.

Inventory every system the website touches

Forms, calendars and checkouts are the visible end of a longer chain. Early in the website redesign process, before anyone opens a design file, list every action a visitor can take and follow each one to where it lands. A shared spreadsheet is enough. What matters is that every path has a destination, an owner and a way to prove it works.

Visitor action	Where it should land	What to verify before launch	Owner
Quote or contact form	CRM contact, deal or ticket	Fields map to the right CRM properties, lead source is saved, lead routing notifies the right person	Sales or operations
Booking request	Staff calendar	Territory, buffer and deposit rules apply, confirmations and reminders send	Whoever owns the calendar
Call, SMS or WhatsApp	Tracking number or shared inbox	Routing by market and business hours, after-hours messages reach a monitored place	Front desk or support
Deposit or payment	Payment processor, then CRM or order system	Success, failure, cancellation and refund each trigger the right follow-up	Finance or operations
Account signup or login	Customer portal or membership area	Welcome email arrives, password reset works, permissions are correct	Support or product
Newsletter or download	Email platform list or segment	Consent is recorded, confirmation email arrives, the right tag is applied	Marketing
Every action above	Analytics, as a key event	Fires once per action with the source intact	Marketing

If a row has no owner, the workflow does not really exist yet. That gap rarely shows up in a design review. It shows up weeks after launch, when someone asks why nobody answered last month’s after-hours messages.

Two details catch many teams out. The first is lead source attribution. Store the landing page, referrer and UTM parameters in hidden form fields so the source travels into the CRM record instead of living only in analytics. The second is how notifications are sent. On WordPress, most form plugins send email through the built-in wp_mail() function, which by default relies on the server’s own mail setup, and a move to new hosting can push those notifications into spam without anyone noticing. Sending through an authenticated SMTP service, with SPF and DKIM records set up for the domain, belongs on the launch plan rather than the bug list.

At Visualmodo, the post-launch support question we hear most often after a theme switch or hosting move is why contact form notifications have stopped arriving even though the form shows a successful submission. In most cases, the cause is an unauthenticated or misconfigured mail setup, and the fix is to configure authenticated SMTP with a verified sender address, then submit a test form to confirm the notification reaches the intended inbox. It takes minutes to check before launch and far longer to untangle once leads have gone missing.

How much of this works out of the box depends heavily on the platform. If that decision is still open, our guide to choosing a website builder that generates inbound leads treats form and CRM integration as a selection criterion rather than an afterthought.

Theme and plugins, or custom website development?

Once the workflows are mapped, the build decision gets easier, because it stops being a question of taste.

A well-built theme with established plugins covers more than many teams expect. Standard contact forms, a single booking calendar, a newsletter signup and a straightforward checkout rarely need custom code. For those sites the priority is a solid foundation, so it pays to know how to choose a WordPress theme for speed, SEO and room to grow before adding anything on top.

The picture changes when the workflow has rules a plugin was never designed around: bookings that depend on territory and deposit status, prices that vary by customer group, orders that must sync with an ERP, or a checkout that needs a second person’s approval. Custom website development earns its cost in those cases because the site has to fit the company’s workflow and data,

The studio linked here is one example of a team that does this kind of work, not an endorsement, and we have no commercial arrangement with them.

A practical test: if one requirement means stacking three plugins that each handle a slice of the same process, or staff are correcting records by hand every week, the tools are shaping the business instead of the other way around. Online stores reach this point often, and the warning signs are covered in our breakdown of when a WooCommerce store needs custom development. Custom work does not have to mean rebuilding everything, either. A focused integration or module can sit alongside an existing theme and handle the one process standard tools cannot.

Measure the business event, not just the pageview

Pageviews are rarely enough to judge whether a redesign works.

A service business may care about qualified leads, calls and booked appointments. A marketplace may care about searches, listing views, account creation and completed transactions. An ecommerce company may need product views, carts, checkout starts and purchases.

Choose those events before launch and test them end to end. A form submission that creates a CRM record but never fires the analytics event creates one version of reality for sales and another for marketing.

In Google Analytics 4, that means creating the events and taking the time to mark them as key events before the new site goes live. Marking an event as a key event only affects reporting from that moment forward and does not rewrite historic data, so a team that waits until after launch loses the clean before-and-after comparison it needed most.

Attribution can break during a redesign as well. New forms, redirects, domains or scheduling tools can strip the source information that once connected a lead to a campaign. That is easier to prevent than to reconstruct months later.

Why leads seem to drop after a website redesign

A sudden fall in conversions after launch is one of the most common redesign scares. Sometimes the new site really is converting worse. Just as often, the leads are still arriving and the conversion tracking broke. Before anyone rolls back the design, separate the two.

Start with the CRM, not the analytics dashboard. If sales is receiving roughly the same number of inquiries as before, the problem is measurement, and the usual causes are predictable:

• The old setup counted a thank-you page view as the conversion, but the new form shows an inline success message, so that page never loads.
• The event fires twice, once from a form plugin and once from the tag manager, or not at all because the tag was attached to a template that no longer exists.
• A new cookie consent banner holds analytics back until visitors accept, which lowers reported numbers without changing real ones.
• Redirects drop query strings, so UTM parameters disappear and email or paid traffic shows up as direct.
• Booking or checkout moved to a third-party domain and cross-domain tracking was never configured.

If the CRM confirms that inquiries really fell, look at what changed on the path to the form: new required fields, a slower mobile page, a phone number that moved below the fold, trust signals that disappeared, or service pages that lost rankings after their URLs changed. Compare page by page rather than site-wide, and compare against the same weeks last year when the business is seasonal.

A launch-day checklist for the workflow behind the site

A redesigned site should be tested with working workflows, not only browser screenshots. Use this as a website launch checklist, run it on the live site (or on staging with production integrations connected), and have the owner of each system confirm the result:

1. Submit every form with realistic data, then check the CRM record, field mapping and staff notification.
2. Call each tracking number and send a test SMS or WhatsApp message, during and after business hours.
3. Book an appointment for each location or service type, then cancel one.
4. Run a successful, a failed and a refunded payment in the processor’s test mode.
5. Confirm that each key event fires once, with the traffic source intact.
6. Check that notification and confirmation emails land in the inbox, not in spam.
7. Complete a form on a phone over a slower connection.
8. Crawl the old URLs and confirm important pages redirect to their true replacement, not the homepage.
9. Confirm the staging noindex setting did not carry over to production.

If URLs are changing, the redirect step needs its own plan. Our SaaS website redesign guide walks through URL mapping, 301 redirects and post-launch monitoring, and the same process applies well beyond SaaS.

This is also when someone should watch for unexpected effects from the production marketing stack. Chat tools, ad pixels and third-party scheduling scripts can change performance after launch. Keep watching for at least the first two weeks, because some failures, like reminder emails and refund notifications, only surface once real customers reach those steps.

Scope the workflow, not just the pages

Visitors experience pages, menus, forms and checkout screens. Employees experience lead records, notifications, calendars, payment status and reporting. A redesign has to connect those two views.

A simple brochure site may need little more than reliable forms and clean analytics. Once a website becomes a meaningful source of leads or revenue, the workflow behind the interface belongs in the project scope. If you plan a website redesign this year, write the workflow inventory before the design brief. It will change what gets designed.

What breaks after a website redesign launch, and how to catch it