Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Checklists

Landing Page Checklist

A landing page checklist before traffic goes live: message match, headline and offer, call to action, form, proof, speed and mobile, and tracking.
Checklistbeginner7 min readUpdated

When to run this checklist

Run it before any campaign sends traffic to a page for the first time, whether the page is new or an old one being pointed at by a new ad. Run it again after a redesign, because templates change behaviour in places nobody looked at, and after any change to the form or its destination. The diagnostic case is a campaign whose click-through rate (CTR) is healthy while its conversion rate (CVR) is not: the ad is doing its job and the page is where the leak is, and this list finds the leak faster than a redesign. It is also worth a pass when a page that used to convert stops doing so with no change in traffic, since the usual cause is something that broke rather than something that was never right: a form endpoint, a consent banner update, a script that slowed the page on mobile. The list covers one page; when the leak could sit anywhere between the advert and the confirmation, an expert review of the conversion journey walks every step against criteria from the same guides and sends what it finds for verification.

Before you start

  • The ad, listing or email that will send the traffic, with its exact words and image. The message group is a comparison between that creative and the page, and it cannot be ticked from memory.
  • The brief: the one action the page exists to produce, who the visitor is, what they already know, and what happens after they act. Pages built to serve several audiences fail the message group by design.
  • A mid-range phone on a mobile connection, not the office wi-fi, for the speed and mobile group.
  • Access to the tag container and analytics, so the tracking lines can be checked by firing the conversion rather than by assuming the template's tag is present.
  • The form's destination: the inbox, the customer system or the sheet where submissions land, with someone able to confirm a test submission arrived.
  • The accessibility baseline the organisation follows; the W3C guidelines in the sources list are the usual reference, and the anatomy guide describes the elements the structure lines refer to.

The checklist

Go through the page as the visitor would, starting from the creative and ending at the thank-you state, and only then open the tag container and the accessibility tools. Lines in the first four groups are judgements rather than measurements, so make them with the creative open beside the page and ask a colleague who has not seen the page to make them too. The last four groups are checks with a definite answer, and a line is ticked only when the check was made on the live URL, not on a preview.

0/33

Message

Structure

Form

Proof

Speed and mobile

Tracking

Accessibility

After launch

If an item fails

Fix tracking and form failures before traffic starts, whatever else is outstanding, because a page that converts without recording it, or that loses submissions, wastes every click until it is fixed. Message and structure failures are the next priority; they are the ones that decide whether the page works at all, and they are cheap to correct in copy. Speed failures are often a template problem rather than a page problem, so a failed line here is worth raising with whoever owns the site rather than patching once. The Core Web Vitals guide explains what the Core Web Vitals measure and which fixes move many pages at once. Proof and accessibility failures should not delay a launch on their own, but they go on the backlog with a date, because "after launch" has a habit of meaning never. The guide to accessibility as conversion work shows how to find those barriers along the whole journey and why they are fixed as bugs rather than tested. For paid search traffic, remember that the page is also part of the auction: the Quality Score guide explains how landing page experience is rated.

Group that failedWhere the fix is explained
Message, structure, proofAnatomy of a landing page and the landing pages hub
FormLanding page forms
Speed and mobileSpeed and mobile and Core Web Vitals
TrackingThe tracking verification checklist and naming conventions and UTMs
AccessibilityThe W3C guidelines in the sources list
After launchThe campaign launch QA checklist, which covers the campaign side of the same launch
Illustrative example — not a real result

A dental clinic's implant consultation page

A dental clinic builds a page for a paid search campaign offering a free implant consultation. The ads promise "free implant consultation, no obligation"; the headline on the page reads "Advanced dental care for the whole family", so the message group fails on its first line. The form asks for 9 fields including date of birth and insurance provider, and a test submission goes to an inbox nobody has opened since the practice manager left. On a mid-range phone over a mobile connection the page takes 7.4 seconds to show its main content because of an uncompressed hero image of 3.1 MB. The clinic rewrites the headline to repeat the ad's promise, cuts the form to name, phone and preferred time, routes submissions to the reception inbox, and compresses the image. In the first three weeks the page converts 11.2% of visitors against 2.9% for the version that would have launched.

Common mistakes

  • Checking the page without the ad beside it. Message match is a comparison; judged alone, every page looks like it matches.
  • Testing the form by looking at it. The field list is fine; the submission goes to a dead inbox, a disconnected integration or a spam folder, and nobody finds out for a fortnight.
  • Reviewing speed on the office network. The page that loads instantly on a laptop over fibre is the same page that loses most phone visitors before the headline appears.
  • Treating proof as decoration. Unattributed quotes and generic logos placed at the bottom of the page are seen by nobody at the moment of decision.
  • Launching a campaign to the homepage. The page passes most lines in isolation and fails the only one that matters: it does not carry the visitor to the single action the ad promised.
  • No record of versions. The page changes three times in the first week and the conversion rate cannot be attributed to any of them.
  • Accessibility as a final polish. Low contrast and unlabelled fields are conversion problems for every visitor, not compliance problems for a few.

The checklists library holds the campaign and tracking lists that pair with this one on launch day.

Terms used on this page

Where this page is used

Also related

Sources

  1. Web Content Accessibility Guidelines (WCAG) — W3C

Related