Work through your launch checks
Tick an item only after checking the public or intended launch version. A completed checklist records the work you reviewed; it does not certify the website or guarantee search visibility. Download the plain-text version if you prefer to work offline.
YOUR LAUNCH REVIEW
0 of 16 checked
Test the customer’s complete task
Start outside your editor or admin session. Open the intended landing page in a fresh browser and follow the journey through to a meaningful result.
For a booking, confirm that the correct event and time zone are shown and that availability is sensible. For a form, use an authorised test and verify delivery. If testing a store, agree a safe test-payment process with the owner rather than placing an unintended live order.
- Check the important actions from service pages as well as the homepage.
- Make error messages understandable and give visitors a way to recover.
- Check telephone and email alternatives.
- Remove test records and restore any temporary test settings after the agreed checks.
Check the basics of search access
Google’s minimum technical requirements include accessible pages, successful HTTP responses and indexable content. Check that the public pages you want found are available, have useful visible content and are not accidentally marked noindex.
Review unique page titles, descriptions, canonical URLs, the sitemap and internal links. A sitemap or Search Console verification does not guarantee indexing or a position in search results.
Replacing a website needs a migration plan too
If you are changing an existing site, inventory its useful URLs and content before launch. Decide which addresses remain and which need a relevant redirect. Check important old links after the change.
A new-site checklist does not replace the decisions involved in moving an established site. Avoid sending every removed address to the homepage just to make the error disappear.
Make account ownership and ongoing tasks explicit
Record who owns the domain, hosting, business email, booking account and any third-party subscriptions. Confirm who can access them and how the owner can recover access.
Agree who changes business information, installs updates, checks backups and handles a broken booking or contact route. Match those responsibilities to the actual platform and support agreement.
Repeat the important checks after launch
Once the public version is live, repeat the core journeys from its final addresses. Check that any redirects, search settings and contact destinations match the release you intended.
Use available search and enquiry information to spot problems and choose improvements. Keep a short issue list with the affected URL, expected result, actual result and person responsible. Launch is a useful starting point for review, rather than the end of the work.
