Before sending people to a campaign landing page, test the complete journey: the message that brings them there, the page itself, the enquiry form and the response they receive. A page can look finished while a broken form or unclear promise prevents a useful enquiry. The following checklist is a practical release review for a small campaign team.
Check that the page delivers the advertised offer
Place the promotional message beside the landing page. Compare the product or service, audience, price, included items and deadline. If the promotion offers a beginner workshop, the page should make its prerequisites and learning activities clear. A reader should not have to guess whether it is the same offer.
Replace broad claims with details you can substantiate. Show what is included, what is optional and what the next step involves. A testimonial should have permission for its intended use and an accurate attribution. Remove placeholder logos, sample customer names and results that cannot be checked.
Make the main action understandable
Choose a primary action that matches the reader’s readiness. “Request the workshop outline” and “Pay for a place” are different commitments. The button and nearby explanation should say which one applies. Keep essential qualifications close to the action, including whether the reader is making an enquiry or a confirmed booking.
For a hypothetical consultation page, the explanation might say: “Send your project outline. We will review the scope and contact you to discuss availability. Submitting this form does not confirm a booking.” Only use this wording if it reflects the actual process.
Test the form with both valid and invalid input
Every field needs a clear label. Identify required fields and explain unusual formats before submission. Placeholder text disappears as a person types and should not replace a label. These checks follow W3C’s guidance on form instructions.
Submit a clearly labelled test enquiry using contact details controlled by your team. Confirm that the right inbox receives it and that the confirmation page describes the next step. Then test a missing required field and an invalid email format. The page should identify the problem in text and help the person correct it, consistent with W3C’s form validation guidance. An error should not quietly erase the other information they entered.
Review on a phone and with a keyboard
Open the live page on a small screen. Check that headings, prices and buttons remain readable without sideways scrolling. Test menus, expandable sections and the form. Review any large image that pushes the offer far down the page or delays its appearance.
Use the keyboard to reach the main links and form fields. Make sure the focused control is visible and that you can submit or recover from an error. These are useful release checks, but they do not replace a full accessibility assessment when one is needed.
Record a decision for each release check
| Check | Evidence to keep | Owner |
|---|---|---|
| Offer and claims match | Approved copy and supporting source | Campaign lead |
| Form reaches the right inbox | Test enquiry reference and receipt time | Operations |
| Errors are understandable | Observed missing-field and format-error behaviour | Web editor |
| Mobile and keyboard review | Device or browser used and any unresolved issue | Web editor |
| Enquiry follow-up is ready | Named responder and agreed response window | Sales or support |
Use pass, fail or not applicable for each row, with a reason. Fix a missing delivery route or a materially misleading offer before promotion begins. Give lower-impact improvements an owner and review date so they do not disappear into a chat thread.
Recheck after the first real enquiries
Review whether enquiries reach the team, whether people understand the offer and which questions keep recurring. You can start with a private enquiry log and campaign-specific references; this workflow does not require a particular analytics service. Record uncertainty when a person’s source is unknown. Improve the page based on observed problems, and repeat the form test after changes to plugins, routing or page layout.