Testing a mobile landing page before an audio campaign

Test the mobile journey from the spoken address through to a confirmed action. A desktop preview cannot show whether a phone visitor can read the offer, use the form or complete the code path.

Start with the campaign route

In a clean browser, type the address as it will be spoken. Check the spelling and trailing-slash variations the site intends to support. Follow any redirect and confirm the destination matches the ad. Open any companion link separately and check its tracking parameters survive the route.

On the first screen, check that you can identify the advertiser, benefit and next step. Find the key condition before taking action. Enlarge the text, rotate the phone, and check that banners and fixed buttons do not hide the offer or action.

Complete the relevant paths

On a real phone, submit the form, begin checkout or complete the page's main action. Repeat with the keyboard open. Check that inputs have descriptive labels, errors explain what to correct, and the visitor can still understand the offer after an error. W3C guidance calls for labels associated with form controls.

If the ad mentions a code, try an eligible code and any invalid, expired or ineligible states relevant to the offer. Check when the benefit appears, what the final amount shows and what the confirmation says. Follow any hand-off to another domain or app.

Check performance and tracking

For a public URL, PageSpeed Insights can provide Lighthouse lab diagnostics and, where available, mobile field data for the URL or origin. A new or low-traffic page may have no URL-level field data. For a private staging page, use a tool that can access that environment. Lab results can help find issues, but they do not replace completing the journey on a phone.

Check that the intended visit and completion events appear in the analytics setup and that the order or lead system records the outcome.

Confirm that a tagged test link remains tagged. Treat an untagged visit as having an unknown source unless the measurement setup provides reliable evidence otherwise. Keep test orders or enquiries out of campaign results under the team's normal procedure.

Record the result

Record the tested address, page version, device, browser, offer terms, code state, outcome and defect owner. Repeat affected checks after a change to the page, redirect or checkout. The launch record should say which paths worked and which still need attention.