LANDING-PAGE ENQUIRY CHECKLIST 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: ____________________ Service / audience: ____________________ Reviewer: ____________________ Review date: ____________________ Preview or production: ____________________ MESSAGE AND FIT 01. [ ] The headline names the actual service rather than making a vague growth promise. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 02. [ ] The ad or referring message and the destination describe the same offer. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 03. [ ] The page identifies who the service is for and any meaningful exclusions. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 04. [ ] Coverage reflects the real location, region or travel radius; no invented offices. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 05. [ ] Scope, conditions and maintained availability are clear before an enquiry. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ EVIDENCE AND EXPECTATIONS 06. [ ] Every photograph, logo and example is owned or authorized for this use. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 07. [ ] Claims, credentials and customer quotations are accurate and permission-backed. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 08. [ ] No fabricated ratings, guarantees, deadlines, scarcity or performance numbers appear. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 09. [ ] The contact action says what happens next without implying a confirmed booking. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 10. [ ] A response owner, real answering hours and fallback route are documented. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ CONTACT AND FEEDBACK 11. [ ] Each required field has a necessary purpose; optional fields are identified. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 12. [ ] Every form control has a visible associated label and useful instructions. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 13. [ ] Empty required fields and invalid email input show specific corrective text. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 14. [ ] Errors are identified in words and can be found with keyboard and assistive technology. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 15. [ ] Confirmation reflects verified system state; failures never display success. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ MOBILE AND ACCESSIBILITY 16. [ ] A narrow-screen review shows no overlapping content or lost essential actions. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 17. [ ] At 200% zoom, text and controls remain readable and usable. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 18. [ ] Keyboard users can reach every action, see focus and leave each control. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 19. [ ] Headings follow a meaningful hierarchy; link text identifies its destination. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 20. [ ] Text and control contrast are checked; meaning does not depend on colour alone. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ DELIVERY AND MEASUREMENT 21. [ ] Phone links use the verified business number and work on a phone, if present. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 22. [ ] An authorized fictional test reaches the real destination, or delivery is clearly disabled in preview. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 23. [ ] A delivery-failure test exposes an honest retry or fallback path without losing necessary context. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 24. [ ] Click, accepted enquiry and booking events have distinct documented meanings; tests are excluded. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ 25. [ ] Collection notices, access, retention and any measurement activation have an accountable reviewer before launch. Status: __________ Owner: __________ Date: __________ Notes / evidence: _____________________________________ Next action / retest date: ____________________________ REVIEW DECISION Ready for the intended next step / Blocked / Further review required: __________ Open blockers and accountable owner: ____________________ Next review date: ____________________ READ WITH /resources/guides/local-service-landing-page-checklist/ /resources/guides/track-leads-and-booked-jobs/ REFERENCE GUIDANCE (opened 17 October 2026) W3C forms: https://www.w3.org/WAI/tutorials/forms/ W3C notifications: https://www.w3.org/WAI/tutorials/forms/notifications/ WCAG 2.2 reference: https://www.w3.org/WAI/WCAG22/quickref/