Quick answer
Launch approval should cover content and customer journeys. A polished homepage is one part of that review; forms, links, mobile layouts, search settings, and recovery arrangements also need attention.
Before you begin
Use the agreed preview address and confirm it represents the proposed release. Prepare approved contact details, service descriptions, policies, and important customer tasks.
What to do
- Review key pages for accurate names, prices where applicable, opening hours, service areas, spelling, image permissions, and meaningful links.
- Test navigation and primary actions on phone and computer. Check menus, dialogs, forms, downloads, and included booking or checkout handoffs.
- Submit coordinated test forms and confirm intended recipients and systems receive them. Agree first on tests that send real messages or create orders.
- Confirm the launch domain, redirects for old URLs, and removal of temporary search restrictions. Keep private staging areas protected.
- Review the backup, rollback, launch window, and support contact. Record limitations and approve the exact release rather than an earlier screenshot.
How to check the result
Keep an acceptance record with tested URLs, devices, results, and unresolved items. Repeat important checks on the public domain after launch because DNS, caches, HTTPS, and integrations can behave differently there.
If you need help
If a critical task fails, report exact steps before approving launch. Separate launch blockers from later improvements. Do not assume test payments, emails, or submissions are harmless without coordinating their effects.
Related help
- Check website and email behavior after a migration
- Check website layouts on phones, tablets, and computers
- Check that website integrations continue to work
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
