Check the environment
Confirm the production origin, HTTPS, intended robots directives and status codes. Preview noindex settings must be changed deliberately for a public launch.
Inspect representative templates
Check titles, descriptions, headings, canonicals and internal links on home, service, audience and guide pages. Validate the generated output, not just source code.
Complete the visitor task
Navigate on a phone and with a keyboard. Submit only authorized test data to the configured enquiry system and confirm where it arrives.
Put it to work
A practical next step
Record a launch decision with passed checks, unresolved items and rollback ownership.
Keep the evidence with the decision.
Save the baseline, the reason for the change and the person responsible for checking it. This makes the work easier to review later and helps your team distinguish a verified improvement from an untested assumption.
This note provides a planning framework. The right implementation depends on your business model, market, website and available records. Where a decision involves scientific interpretation, clinical services or legal status, use the appropriate qualified reviewer rather than treating marketing guidance as approval.
Related agency support
Website Design ↗
Review the service scope and use the briefing tool to describe your current situation.