Version 1.0 | Authored 17 October 2026 | 25 checks
Use this worksheet before sending traffic to a service page. Record Pass, Fix, Not applicable (with reason), or Not verified for each check. Give every Fix or Not verified item an owner, action and date. Retest delivery, misleading claims and unusable controls before launch. Use fictional test details; do not add customer information. This is a practical preflight, not an accessibility, security or legal certification. For an unpublished preview, disabled delivery should be explicit; preview success does not pass a production delivery check.
- Page URL
- Record the page being checked.
- Service / audience
- Name the intended service and visitor.
- Reviewer / date
- Record who checked the page and when.
- Preview or production
- State which environment was tested.
Message and fit
The headline names the actual service rather than making a vague growth promise.
Record: status; owner; date; notes / evidence; next action / retest date.
The ad or referring message and the destination describe the same offer.
Record: status; owner; date; notes / evidence; next action / retest date.
The page identifies who the service is for and any meaningful exclusions.
Record: status; owner; date; notes / evidence; next action / retest date.
Coverage reflects the real location, region or travel radius; no invented offices.
Record: status; owner; date; notes / evidence; next action / retest date.
Scope, conditions and maintained availability are clear before an enquiry.
Record: status; owner; date; notes / evidence; next action / retest date.
Evidence and expectations
Every photograph, logo and example is owned or authorized for this use.
Record: status; owner; date; notes / evidence; next action / retest date.
Claims, credentials and customer quotations are accurate and permission-backed.
Record: status; owner; date; notes / evidence; next action / retest date.
No fabricated ratings, guarantees, deadlines, scarcity or performance numbers appear.
Record: status; owner; date; notes / evidence; next action / retest date.
The contact action says what happens next without implying a confirmed booking.
Record: status; owner; date; notes / evidence; next action / retest date.
A response owner, real answering hours and fallback route are documented.
Record: status; owner; date; notes / evidence; next action / retest date.
Contact and feedback
Each required field has a necessary purpose; optional fields are identified.
Record: status; owner; date; notes / evidence; next action / retest date.
Every form control has a visible associated label and useful instructions.
Record: status; owner; date; notes / evidence; next action / retest date.
Empty required fields and invalid email input show specific corrective text.
Record: status; owner; date; notes / evidence; next action / retest date.
Errors are identified in words and can be found with keyboard and assistive technology.
Record: status; owner; date; notes / evidence; next action / retest date.
Confirmation reflects verified system state; failures never display success.
Record: status; owner; date; notes / evidence; next action / retest date.
Mobile and accessibility
A narrow-screen review shows no overlapping content or lost essential actions.
Record: status; owner; date; notes / evidence; next action / retest date.
At 200% zoom, text and controls remain readable and usable.
Record: status; owner; date; notes / evidence; next action / retest date.
Keyboard users can reach every action, see focus and leave each control.
Record: status; owner; date; notes / evidence; next action / retest date.
Headings follow a meaningful hierarchy; link text identifies its destination.
Record: status; owner; date; notes / evidence; next action / retest date.
Text and control contrast are checked; meaning does not depend on colour alone.
Record: status; owner; date; notes / evidence; next action / retest date.
Delivery and measurement
Phone links use the verified business number and work on a phone, if present.
Record: status; owner; date; notes / evidence; next action / retest date.
An authorized fictional test reaches the real destination, or delivery is clearly disabled in preview.
Record: status; owner; date; notes / evidence; next action / retest date.
A delivery-failure test exposes an honest retry or fallback path without losing necessary context.
Record: status; owner; date; notes / evidence; next action / retest date.
Click, accepted enquiry and booking events have distinct documented meanings; tests are excluded.
Record: status; owner; date; notes / evidence; next action / retest date.
Collection notices, access, retention and any measurement activation have an accountable reviewer before launch.
Record: status; owner; date; notes / evidence; next action / retest date.
Review decision
Record: ready for the intended next step, blocked, or further review required. List open blockers, their accountable owner and the next review date. Do not treat a completed worksheet as proof of production delivery or full accessibility conformance.
Use the landing-page readiness guide and enquiry-to-booked-work guide for context.
Use it as a working record.
A completed checkbox records your own review. It does not certify accessibility, platform compliance or future results. Get permission before testing a live contact route, use synthetic details and keep customer information out of this checklist.
This page and its download do not collect your answers. Make a local copy if you want to record notes.
Explore landing-page services