FreeA checklist + your phoneAbout 50 min
Run a Launch Checklist That Can Fail
A launch checklist is only worth anything if a box can stay unchecked and stop the launch. You will build one with real tests, not opinions.
Why This Matters
The worst launch is the one where everyone says it looks fine. A site can look fine and have a dead form, the wrong phone number or a page that tells Google to stay away. A pass needs proof, like a screenshot or a received email.
✓ How To Do It
- Make a list with one line per test and a blank for proof. A spreadsheet works.
- Phone test. Tap every phone number on a real phone. It must dial the right line. Save a screenshot of the dial screen.
- Form test. Send every form with your own details. Wait for the email or text. Do not call it done until it arrives.
- Page test. Open every page at the live address. Look for broken images, old text and a placeholder like Lorem ipsum.
- Facts test. Check the name, address, hours and license numbers against your records.
- Search test. Open view source on the home page and look for the word noindex. A building site often has it on and it must come off before launch.
- Secure test. Type the address starting with http, no s. It must jump to https.
- Speed test. Run PageSpeed Insights on the home page and one service page. Save the mobile results.
- Tracking test. Do a test visit and confirm it shows in your reports, as taught in Set Up GA4 and Mark Your Key Event.
- Sign the list. If any line has no proof, the site does not launch. Fix it, test again, and sign.
- After launch, verify the site in Google Search Console, as in Verify Your Site in Google Search Console.
Done WhenSave the signed checklist with a proof file for every line.
Reference List
Sources
Tips & Pitfalls
- Check that the copy you edited is the copy that is live before you push anything.
- Run the list again after every large change, not only the first time.
- Have one person who did not build the site run the phone and form tests.
