Check content, mobile journeys, forms, domains, search visibility, and recovery, with clear criteria for launch blockers and follow-up work.
A homepage loading successfully is only one launch check. Readiness means customers can understand the offer and complete the intended action, while your team can receive the result and handle failures. Keep one checklist recording the test, owner, outcome, and unresolved issue. Test the release you intend to publish, then repeat essential checks on the public address.
Verify the journeys the business depends on
Choose three relevant journeys, such as requesting a quote, sending a message, and purchasing when checkout is in scope. Follow each from the first page through to the responsible person's view of the result. A success message alone is insufficient. Confirm that the correct request arrives and that repeated clicks do not create unwanted duplicates.
For payment websites, coordinate a controlled test with the payment owner using the provider's agreed verification process. Include cancellation, failure, and the return to the website. The order's financial state must reflect payment confirmation, rather than merely the visitor arriving back from the provider.
Check content as a first-time customer
- Verify the business name, services, coverage areas, telephone numbers, email, and addresses.
- Replace demonstration copy and temporary images; confirm approval and usage rights for supplied material.
- Review the homepage, service or product pages, frequently asked questions, contact details, and approved policies.
- Open language URLs directly, then switch languages and inspect text, buttons, and messages.
- Follow navigation, footer, download, and legacy links to their intended destinations.
Have someone fluent in each language review commercial terminology, numbers, and contact instructions. Compare photographs with the offer: could a customer reasonably interpret the image as something you do not supply?
Use a phone and a keyboard
On a real phone, open the menu, enlarge text, and complete the form with the keyboard visible. Check Arabic direction and long numbers. Navigate with a keyboard and close open menus. W3C's Easy Checks offers an initial review, while noting that basic checks cannot establish complete accessibility conformance.
Try heavier pages on a mobile connection and record the conditions for later comparison. Use the mobile website speed guide when loading problems need investigation.
Verify the public address and search settings
Check that the address variants you intend to advertise reach the correct website over HTTPS without certificate warnings. Confirm domain ownership and renewal responsibility. Review titles, descriptions, canonical URLs, and the sitemap, alongside the intended restrictions for private pages.
A staging restriction can remain accidentally. Google's noindex documentation explains that a crawler needs access to a page to read that directive. Review public-page rules individually. A sitemap helps discovery but does not guarantee indexing or ranking.
Assign recovery and make the launch decision
Confirm a recoverable backup and identify who restores service if publication fails. Review your agreed hosting coverage, renewal responsibilities, and safe storage of access details. Test restoration so the recovery procedure is understood.
Delay launch for a broken primary action, exposed sensitive information, or incorrect prices and payment states. A small cosmetic improvement can have a named owner and scheduled follow-up. After publication, repeat essential journeys on the public address and review errors and incoming requests during the first days. Move recurring work into a maintenance and security plan.