Check a new website on a phone before it goes live, using a phone that is not logged into the design tool. The layout can look finished on a wide monitor and still hide the phone number, the menu, or the form on the device your customers actually use.
Use a normal phone on a normal connection
Open the preview link in a phone browser, not in a stretched desktop window. Do it once on wifi and once on cellular if you can. Ask someone who did not build the site to hold the phone. They will tap what a customer taps.
Check the homepage, one service page, and the contact page. Those three catch most launch problems.
Walk this list from top to bottom
- The headline is readable without pinching to zoom.
- The phone number is visible and tapping it opens the phone app with the right number.
- The menu opens, every item can be tapped, and it can be closed.
- Buttons are large enough that you do not hit the wrong one.
- Text does not run off the edge of the screen.
- Photos load and are not stretched or cut through a face or a finished job.
- The form fields are big enough to type in, the keyboard does not cover the submit button permanently, and a test message arrives in the inbox you will watch.
- Nothing important sits under a chat bubble, a cookie bar, or a sticky header.
- The page still makes sense if you turn the phone sideways, or the layout stays usable in portrait, which is how most people hold it.
Read the words out loud
On a phone, long lines of small gray text get skipped. If a sentence is hard to read aloud, shorten it. Confirm the city names, the hours, and the service list match the Google listing. A launch is a bad time to discover the site says “open Sunday” and the listing says “closed.”
Fix blockers before announcing the site
A typo in a paragraph can be fixed after launch. A form that does not send, a phone link that fails, or a menu that traps the visitor should block the launch. Send the test lead, then call the number yourself.
When those pass, remove any “coming soon” banners and point the domain at the new site. Keep the old addresses that people already use, and send them to the matching new pages.
Have someone who did not build it try to call
The person who built the site already knows where the button is. Hand a phone to someone in the office who was not in the design meetings. Ask them to find what you do, where you work, and how to reach you, without hints. Watch where they hesitate.
Common stalls are a menu that uses internal names, a form that asks for a budget before a name, and a chat window sitting on top of the call button. Fix those before you announce the site. A launch email will not repair a path the staff cannot complete.
If the test fails because the page is simply too long, shorten it using how to write a service page a local customer can scan.
Sierra Social Marketing runs this check before we publish a Reno business website. Send a preview link if you want a second person to try it on a phone before you announce it.
