Forms are where redesigns fail quietly. The new contact form looks great, but notifications go to an inbox nobody checks, the CRM connection was never rebuilt, and the analytics event that counted leads no longer fires. Weeks pass before anyone notices that enquiries have dropped. Calls to action suffer a softer version of the same problem: buttons get copied from the old site, or replaced with vague labels, without anyone deciding what each page should ask for.
This article covers the decisions that belong inside a redesign project. For broader techniques that apply to any site at any time, see our in-depth guides to form optimization and CTA optimization.
Inventory Your Current Forms and CTAs First
Before designers touch a single form, write down how the current ones work. This list becomes the specification for the rebuild and the test plan for launch day.
Form inventory
- Every form on the site, including pop-ups, footer forms and forms on old landing pages.
- Where each submission goes: which email addresses, which CRM or job system, which mailing list.
- Any automatic replies sent to the person who submitted.
- Which analytics events or thank-you page URLs count each submission.
- Which spam protection is in place, and whether it works.
- Every CTA button and phone link, with the page it appears on and where it leads.
Choosing the Right CTA for Each Page Type
Not every page should ask for the same thing. Match the primary CTA to what a visitor on that page is ready to do, and keep one secondary option for people who prefer another route.
| Page type | Primary CTA | Secondary CTA |
|---|---|---|
| Homepage | Get a quote or call | Browse services |
| Emergency service page | Call now | Request a callback |
| Planned service page | Request a quote | Call to discuss |
| Location page | Book a visit in that area | Call the local number |
| Booking-led practice | Book an appointment online | Call the office |
| Blog or guide | Read the related service page | Request a quote |
The blog row is deliberate. Someone reading a guide about furnace noises is usually researching, not ready to book, so a link to the matching service page is a more natural next step than a hard sell. Emergency pages are the opposite: a visitor with a burst pipe in a Dallas winter freeze wants a phone number, not a five-field form.
Write the page types and their CTAs into the redesign brief, so designers build buttons and forms for each template instead of improvising page by page.
CTA Wording, Placement and Repetition
A good CTA tells visitors what will happen when they click. Submit and Learn More say nothing; Get My Free Quote, Book a Same-Day Visit or Call Our Office Now set an expectation. Add a short line nearby if the next step needs explaining, such as we reply within one business day, but only if that is true.
- Place the primary CTA where it is visible without scrolling, after key proof, and at the end of the page.
- Repeat the same action rather than adding new ones; three different buttons on one page split attention.
- On mobile, make the phone number a
tel:link and track taps as a key event. - Show the number as readable text too, since desktop visitors may dial it from another phone.
Sticky call bars and other mobile patterns can help or hurt depending on how much screen they cover; our guide to fixing mobile usability problems looks at those trade-offs.
The Form Field Audit: Keep, Remove or Move Each Field
Go through every field and ask one question: do we need this to respond to the first enquiry? If the answer is no, remove it or move it to the follow-up conversation. The table shows a typical result for a service business quote form.
| Field | Decision | Reason |
|---|---|---|
| Name | Keep | Needed to address the reply |
| Phone | Keep | Most service leads are closed by phone |
| Keep or make optional | Useful for written quotes; some people prefer a call only | |
| Service needed | Keep as a dropdown | Routes the lead and qualifies it with one tap |
| ZIP code | Keep if you limit service areas | Filters out-of-area requests |
| Full street address | Move to follow-up | Feels intrusive at first contact |
| Preferred time | Optional | Helpful for booking-led businesses only |
| How did you hear about us | Remove | Better answered by tracking or asked on the call |
| Budget | Optional for large projects | Can qualify leads but deters some visitors |
| Message | Keep, optional | Lets people explain unusual jobs |
When a Multi-Step Form Makes Sense
Multi-step forms split questions across screens. They work when you need several qualifying answers, such as project type, timing and property type, because each screen feels small and the first step can be a simple choice like a button for repair or a button for replacement. Show a progress indicator so people know how many steps remain, and ask for contact details last, once the visitor has invested in the answers.
For a short contact form, splitting it into steps adds clicks without benefit. Campaign pages have their own form-length trade-offs, which our article on landing page redesign covers.
Inline Validation and Error Messages
Errors are where many submissions are lost, especially on phones. The redesign is a chance to replace generic messages and red borders with help that actually gets the visitor to the end.
- Validate a field when the visitor leaves it, not on every keystroke, so people are not warned before they finish typing.
- Put the error message next to the field, in text, and say how to fix it: enter a 10-digit phone number, not invalid input.
- Never clear what the visitor already typed when an error appears.
- Use visible labels above fields rather than placeholder text that disappears when typing starts.
- Use the right input types and autocomplete attributes so phones show the correct keyboard and autofill works.
Labels, error text and keyboard access are also accessibility requirements, which are covered in our accessibility checklist for redesigns.
Thank-You Pages, Tracking and Spam Protection
After a submission, send people to a thank-you page or show a clear confirmation that says what happens next and when. A dedicated thank-you page also gives you a simple way to count leads in GA4, either by page view or by an event fired on successful submission. Pick one method, so each lead is counted once.
Spam protection should be invisible to real people wherever possible. A honeypot, which is a hidden field that only bots fill in, stops a lot of automated spam without asking visitors to do anything. Add server-side checks and rate limits behind it, and use a challenge service such as reCAPTCHA or Cloudflare Turnstile only if spam keeps getting through. Avoid puzzles that frustrate customers on small screens.
Testing That Submissions Actually Arrive After Launch
Launch day often involves DNS and hosting changes, which can break email delivery even when the form itself works. Test on the live site, not just on staging.
- Submit every formUse a real name and a note such as launch test, on desktop and on a phone.
- Follow each leadConfirm it reached every inbox, the CRM and any mailing list, and check spam folders.
- Check the autoresponderMake sure the visitor's confirmation email arrives and has the right details.
- Confirm trackingLook for the key event in GA4 Realtime or DebugView for each submission.
- Check email authenticationSend form email through an authenticated SMTP service with SPF and DKIM set up for your domain, so messages do not land in junk.
- Repeat regularlySchedule a test submission every week or two; forms can break after plugin updates or email changes.
Form and CTA checks should also sit in your staging review, as in our UX checklist for redesigns, and they are one part of the wider process in our guide to raising conversion rates through a redesign. If you would like forms, tracking and CTAs planned and tested as part of the build, that is standard in our conversion-focused websites.