Dilawar Malik
Published
5 min read
A redesign launch is judged by how it looks, but its success is decided by what still works. The most expensive redesign failures are rarely visual. They are the enquiry form that stops sending emails, the tracking code that disappears, and the phone number that changes without anyone noticing. Visitors arrive at a beautiful new site and cannot contact the business, and nobody knows for weeks because the measurement that would have revealed it is gone too.
Preserving forms and tracking through a redesign is a matter of inventory, testing, and a calm launch day. None of it is difficult. All of it is easy to skip when the focus is on design approval and deadlines. The checklist below treats the launch as a handover, where every working part of the old site must be accounted for on the new one.
Inventory everything that collects or measures
Before any development starts, list every form, every tracking tag, and every integration on the current site. Include contact forms, quote forms, newsletter signups, booking forms, chat widgets, call tracking numbers, analytics, advertising pixels, and consent banners. For each one, note where it appears, where its submissions go, and who receives them.
This inventory becomes the test list for the new site. If an item is not on the list, it will not be tested, and it may not be rebuilt. The inventory should also record the email addresses and tools that receive form submissions, because a form that submits successfully but sends its emails to an old address is as broken as one that does not submit at all.
Test forms on staging as a visitor would
Test every form on the staging site, not just the main contact form. Submit each one with realistic details, check that the confirmation message appears, and confirm that the notification arrives in the right inbox and the right tool. Test the failure cases too: a missing required field, an invalid email address, and a very long message should all produce clear, helpful errors.
Check the form on a phone as well as on a desktop. A form that works with a mouse can fail on a phone when fields are too small, the keyboard covers the submit button, or the date picker does not open. Most enquiries now arrive from phones, so mobile testing is not optional.
Audit tracking before it goes live
Use your analytics and tag tools to record what fires on the current site: page views, form submissions, phone clicks, file downloads, and any custom events. Then check the same events on staging. Tracking that is missing or duplicated on staging will be missing or duplicated after launch, and the data lost in between cannot be recovered.
Pay particular attention to consent. If the site uses a consent banner, test that tracking respects the visitor’s choice on the new site, including when consent is refused. A redesign is a good moment to fix consent handling, and a bad moment to discover it was never working.
Keep URLs, redirects, and internal links intact
When page URLs change, old links from search results, guest posts, and bookmarks break. Map every old URL to its new equivalent, and set up redirects before launch. Test the redirects on staging, including the most important landing pages and any page that receives links from other websites.
The same care applies to the technical checks that protect a launch. The article on technical SEO checks to run before publishing a guest post covers the checks that catch broken pages and missing elements before visitors do, and the same discipline applies to a whole site launch.
Plan launch day in advance
Launch at a quiet time, with the people who can fix problems available and the old site’s backup ready. After the switch, run the test list again on the live site: submit every form, check every notification, and confirm the analytics are recording. Check the site on a phone, on a slow connection, and in a second browser.
- Submit a test enquiry through every live form.
- Confirm notifications arrive in the right inboxes.
- Check analytics and tag firing on key pages.
- Test the main redirects from old URLs.
- Check the contact details on every page, including the footer.
Frequently asked questions
What is the most common thing lost in a redesign
Form notifications are the most common loss, followed by analytics and advertising tags. Both fail quietly: the form looks fine, but its emails go to the wrong address, or the tracking code is present on the home page but missing from the pages that matter. An inventory and a staging test catch both.
Should forms be rebuilt or copied to the new site
Either approach works, as long as the rebuilt form is tested end to end. Rebuilding is often cleaner, because it removes old fields and outdated logic. Copying is faster, but it can carry over problems. Whichever you choose, test it as a visitor would, on staging and again after launch.
How long should I keep the old site available
Keep a full backup, and keep the old site accessible in staging for at least a month, so you can compare behaviour and recover anything that was missed. Do not delete the old site or its data until the new site has been checked thoroughly and the first reporting cycle is complete.
What if tracking stops working after launch
Check the tag setup and the consent banner first, since those are the most common causes. Compare what fires on the live site with the staging test record, and fix the tags before making any other changes. The data lost during the gap cannot be recovered, so treat tracking as a launch-day priority, not a later tidy-up.
Who should sign off the launch
The person who owns enquiries should sign off the forms, and the person who owns reporting should sign off the tracking. A design sign-off alone is not enough. The launch is ready when the people who rely on the site’s working parts have tested them and confirmed they work.
A redesign should improve how a business looks without breaking how it works. Inventory the forms and tracking, test them twice, and launch with a plan, and the new site will earn enquiries from its first day.
