FreeA phone + your live siteAbout 30 min
Prove It Works by Using It
Verifying means using the thing the way a customer would. Send the real form. Call the real number. A green check from a tool is a hint, not proof.
Why This Matters
A form on this very course site sent every case study submission into a 405 error after a host move. Nothing was captured and the visitor saw no error. The page loaded fine and a status check said 200. Only a real submission would have shown it.
✓ How To Do It
- Make a short list of everything that must work. Include each form, each phone number, each booking link and each payment page.
- Submit each form from a phone on mobile data, not your office wifi. Use a clearly marked test name and your own email.
- Check that the message arrived where it should. Look in the inbox, the lead system and the alert. If any one is missing, the form is broken.
- Call each number and listen. Check the greeting, the ring and who picks up. If you use a tracked number, check the call shows up in the log.
- Click every button on the first screen of your most visited pages. A dead call button costs real money.
- Test after every host move, domain change, plugin update or deploy. Those are the moments things break.
- Look at what the visitor sees too. A form that fails silently is the worst kind. It should show a clear error or a thank you.
- Do not trust a 200 alone. A page can return 200 and still show an error, as the form lesson explains.
- Record the date, the tester and the result in a log. Keep it simple, one row per check.
- Run the list again once a month, and set a calendar reminder so it does not depend on memory.
Done WhenEvery form and number on the list has a logged test with the date, the result and a screenshot or a note.
Reference List
Sources
Tips & Pitfalls
- Delete test leads afterward so they do not reach a real follow up.
- Do not send test texts to real customers.
- If you cannot test something safely, say so and ask the owner to run it with you.
