Website Design
By Website Design Company editorial team · Reviewed 2026-10-14
Check the actual release
Name the version and environment under review. Test the important visitor journeys on desktop and mobile. Verify navigation, forms, errors, confirmation states and keyboard use. Screenshots are useful evidence but do not replace interaction tests.
Verify forms end to end
Submit a clearly labelled test enquiry. Confirm its database record, originating page and notification delivery. Test invalid inputs and provider failures. A mailto link or a successful browser alert is not evidence of server-side delivery.
Verify payment boundaries
Use the provider sandbox first, including cancellation, repeated callbacks and failure states. Confirm orders are priced on the server and payment status changes only after verified provider evidence. Manual invoicing should remain explicitly manual.
Review crawling and content
Check canonical URLs, redirects, robots directives, the sitemap and private page exclusion. Publish only reviewed content. Make sure preview environments are noindexed and production crawl controls are changed deliberately after launch approval.
Plan recovery
Record migration and rollback steps, backup ownership and access recovery. Establish who responds to production errors. Confirm that sensitive records are not copied into a public repository or troubleshooting screenshot.
Make launch approval explicit
Sign off with passed, failed and not-run checks. Performance, live mail, legal text and real-provider payment tests may require separate evidence. If a critical path is unverified, launch a preview rather than announcing production readiness.