What to check after a website goes live

Launch day is a starting line

Pushing a site live feels like the finish, but it is really the moment the real testing begins. A local staging site behaves differently from the live one, real visitors do things you never thought to try, and search engines have to find you from scratch. The hours and days just after launch are when small problems are cheapest to catch, so here is what I work through.

Test every way someone can contact you

This is first because it is the one that costs money. Send a real enquiry through every form on the site and confirm it lands in the right inbox, not a spam folder. Click the phone number on a phone and check it dials. Tap the WhatsApp link and check it opens the right chat. If the site takes bookings or payments, run a full test transaction. A broken contact form on a brand new site means every bit of your launch effort leaks straight out of a hole.

Make sure Google can find and read it

A beautiful site nobody can find is a poster in a locked room. After launch:

• Confirm the site is not accidentally blocking search engines. A "noindex" tag left over from development is a classic and painful mistake.
• Set up Google Search Console and submit your sitemap so Google knows the pages exist.
• Check your title and description show sensibly when you search your business name.
• Claim or update your Google Business profile, and make sure the details match the site.

Indexing takes days, not minutes, so do this early and check back rather than panicking on day one.

Check it on real phones

Most of your visitors are on mobile, so open the live site on an actual phone, not just the desktop preview. Look for text that runs off the screen, buttons too close to tap cleanly, images that overflow, and menus that will not open. Try it on both a phone and a laptop, and if you can, on a slightly older Android, since that is what a lot of South African customers are actually using.

Watch the speed

A page that crawled on your fast office wifi will be worse on mobile data. Run it through a free speed tool and look at load time on a mid-range phone. The usual culprit is images: a client uploads a 4MB photo straight off a camera and the page grinds. Compress the heavy ones, and the whole site feels quicker for everyone.

Hunt for the small breakages

Once the big things pass, sweep for the little ones that make a site feel unfinished:

• Broken links, both between your own pages and out to others.
• Missing images or placeholder text left in from the build.
• The 404 page, which should be styled and offer a way back, not a blank error.
• Spelling and real details, like the correct phone number and current prices.

Confirm the safety net

Before you relax, make sure the things that protect the site are on. The SSL certificate should be active, so the address shows a padlock and no "not secure" warning. Automatic backups should be running and, ideally, tested once by restoring them. Knowing you can roll back turns a future disaster into a minor annoyance.

Then watch the real thing

The checks above are technical. The real measure of whether a site works comes in the following weeks: are actual enquiries arriving, and are they the kind you want? If traffic is coming but nobody contacts you, the problem is usually the message or the path to get in touch, not the plumbing. If the wrong enquiries arrive, the copy is not being clear enough about what you do.

This early stretch is exactly what a care plan is for. A lot of small issues only surface once real people are using the site, and having someone watch analytics, speed, and uptime in the first weeks catches them before they cost you. If you would rather hand that part over, that is what ongoing care covers, and you can get in touch to set it up.