Website launch checklist: The five-minute smoke test
Before I publish a site, I run one realistic visitor journey on a phone and desktop. This short smoke test catches visible problems; it’s a starting point for a fuller launch review.
Follow a real request
Starting from the homepage, open a project, pick a service, and contact the studio. Check every link on a phone, including email and WhatsApp, without sending a test to someone else. Check that the link starts the correct action. An email draft is fine if you clearly call it a draft. If the site says it sends a request, test the full workflow in a controlled environment before publishing.
Try the opposite language direction
Use a long title in an RTL language and check navigation, labels, numerals, and text alignment. A mirrored layout should still keep names and contact details legible. In the right-to-left version, check that email addresses, phone numbers and code remain in a readable order. I also test whether the chosen language stays selected after opening a project.
Write down what broke
Record the URL, device, and what you expected to happen. Attach the smallest screenshot that explains the problem, then verify the same path after the fix. Add a short result beside each check: pass, fix, or not tested. A blank checkbox does not tell the next person whether the feature was skipped or failed.
My five-minute route
Minute one: read the homepage and open a service. Minute two: visit a related project and return to the service. Minute three: open the contact path and inspect its target. Minute four: switch to an RTL language at a narrow width. Minute five: tab through the contact page, find the first unclear label, and record exactly how to reproduce it.
Check what a shared link opens
I copy the address from an inner page in a second language and open it in a fresh window. I check the page title, language, lead image and the route back to the blog. Then I try an old bookmarked address. A graceful redirect goes to the closest replacement; an unrelated homepage makes a broken journey look like a working one.
Retest the release, not only the preview
After publishing I open the live address on a phone without the editing session. I check a hero image, a deep article link and the first contact action. I write down the release, the time and the result. If a form needs a real delivery test, I use a designated test recipient so nobody mistakes the message for a client enquiry.

