Content and trust
Confirm service descriptions, contact details, areas served and permissions for photography and case studies. Remove placeholders and claims that nobody can substantiate.
The enquiry journey
Complete the form with safe test information. Check required fields, invalid input, error messages and actual destination receipt if the site sends enquiries. An email-draft flow must say that the visitor still needs to send it.
Usability and accessibility
Check phone, tablet and desktop layouts. Navigate with a keyboard, verify focus visibility and inspect labels, contrast, touch targets and image alternatives. Test reduced motion and make sure content is available without animation.
Ownership and recovery
Confirm the business controls its domain, hosting and source. Record renewal responsibilities and recovery access without putting passwords in project documentation. Keep a tested rollback path.
Metadata and public access
Review page titles, descriptions, canonical URLs and sharing images. Align sitemap, robots and noindex settings with the launch decision. A private preview or cached social card is not proof of a publicly crawlable site.
Operations after launch
Agree who checks delivery failures, updates dependencies and responds to changes. Revisit the privacy notice when processors or data handling change. Measure real enquiries before deciding what to expand.
A planning guide for discussion. Project commitments, acceptance criteria and operating responsibilities belong in an agreed scope.