Website Launch Checklist: What to Check Before, During, and After Go-Live

A quick click-through feels responsible, but it's usually done by the person who built the site. They already know where everything is. Real visitors don't.

A checklist forces you to test like a stranger. On a phone, on patchy data, with a typo in their email, landing on a service page from Google.

It also protects the money you've already spent. If the enquiry path is broken on day one, every visitor you send there is walking up to a shop with the door locked.

Content delays more launches than code does. Pages sit half-written, photos arrive late, and the About page gets one more pass. Start here.

The privacy policy deserves a moment. A contact form collects personal information, and in New Zealand that sits under the Privacy Act 2020. A template copied from someone else's site is better than nothing, but only just.

One more test. Read the homepage out loud. If it sounds like a brochure written by committee, it reads like one too. Our guide on what makes a website convert covers the copy and layout decisions worth fixing before launch rather than after.

This is the most important section on the list. A website can survive a slightly wonky image. It can't survive a contact form that sends enquiries into the void.

Clicking submit once and seeing a thank-you message proves the form submitted. It proves nothing about whether anyone received it. Test it properly:

1. Submit every form on the site with realistic details, including a phone number and a message.
2. Check the enquiry lands in the inbox you'll actually monitor, and not in spam.
3. Hit reply on the test enquiry and confirm it goes to the customer's address, not back to your website.
4. Submit with a mistake (a missing field, a badly typed email) and check the error message makes sense.
5. Tap every phone number on a mobile and confirm it opens the dialler with the right number.
6. Tap every email link, map link, and booking button too.

If you take bookings or payments, make a real test booking or low-value purchase, then cancel or refund it. Payment settings have a talent for staying in test mode.

Then click every button and menu link on every page. For layouts that make enquiring easier in the first place, see these contact page examples.

For local trades and clinics especially, phones bring in a big share of visits. You reviewed the desktop version. Customers meet the mobile one.

Then open it in Chrome, Safari, Firefox, and Edge on a laptop, looking for anything broken or overlapping.

If a visitor has to zoom, scroll sideways, and tap three times to find your phone number, they're not being nurtured. They're being tested. Our guide to responsive web design services goes deeper on what good mobile behaviour looks like.

A slow site loses people before your copy gets a chance to work. If the page loads slower than the customer's patience, the design is no longer the problem.

Google measures real-world page experience with three Core Web Vitals. The targets below are the "good" thresholds Google publishes on web.dev.

Run your key pages through PageSpeed Insights before launch: the homepage, your main service page, and your contact page. Focus on the mobile results.

You don't need a perfect score. You need a site that feels quick on a mid-range phone on mobile data.

This is where launches go wrong without anyone noticing. Everything looks fine to humans while search engines are politely being told to go away.

The classic culprit is a noindex setting left over from staging, like WordPress's "discourage search engines" checkbox. Forget to untick it and the new site can sit invisible for weeks.

Once the site is live, verify it in Google Search Console and submit the sitemap. Google's own guide to building and submitting a sitemap covers the steps. Then run the URL Inspection tool on your homepage and main service pages.

Indexing isn't instant, and it isn't guaranteed. If pages still aren't showing after a few weeks, our walkthrough on fixing Google not indexing your pages covers the usual causes. And if you'd rather have search built into the site from the start, read our guide to SEO website design.

Brand new business on a brand new domain? Skip ahead. Replacing an existing website? This section matters more than almost anything else here.

Your old site has pages Google already knows, some of which rank or have links pointing at them. If those URLs disappear without a redirect, visitors hit a 404 page and search engines lose the trail.

A redesign that wipes out your Google rankings turns a fresh new website into a very expensive reset button.

1. Export every URL on the old site, using its sitemap, Search Console, or a crawler tool.
2. Map each old URL to the most relevant page on the new site.
3. Set up permanent (301) redirects for every URL that changes.
4. After launch, test a sample of old URLs to confirm they land in the right place.
5. If you're moving domains, keep the old one registered. Letting it lapse throws the redirects away.

Don't redirect everything to the homepage. It dumps visitors somewhere they didn't ask to go, and search engines often treat it like a missing page. Our guide to website migration costs explains why the redirect map is where cheap migrations most often cut corners.

If you can't measure enquiries, you'll end up judging your new site by how it feels. That's a terrible way to judge a sales tool.

Test each tracked action after launch. Tracking that silently fails hands you confident numbers that are wrong.

If you're buying traffic, this matters twice as much. Google Ads can't optimise toward conversions it can't see.

The Web Content Accessibility Guidelines (WCAG) from the W3C are the standard reference. You don't need to memorise them, but a handful of checks catch most of the obvious problems:

• Text has strong contrast against its background.
• Images have meaningful alt text, and purely decorative images are marked that way.
• The whole site can be used with a keyboard alone.
• Form fields have visible labels, not placeholder text that vanishes when you type.
• Links say where they go. "Click here" tells nobody anything.

For security, the SSL certificate should be active on every page, admin logins should use two-factor authentication where offered, and backups should be running, which a regular website maintenance checklist keeps on track after launch.

Finally, trust. Does a stranger have reasons to believe you're real? Genuine reviews, real photos, credentials, a service area, and an obvious way to reach a human. These website trust signals examples show what solid proof looks like on different page types.

Launch day should be boring. Boring means it worked.

Pick a morning early in the week when your builder is around. Launching late on a Friday is a bold strategy if you enjoy weekend emergencies.

1. Take a full backup of the old site (if there is one) and the new one.
2. Confirm final content is approved and nothing is still sitting in draft.
3. Point the domain or update DNS, and allow time for the change to spread.
4. Check the SSL certificate is active on the live domain.
5. Switch search engine visibility on and confirm no noindex tags remain.
6. Re-test every form, phone link, and booking flow on the live domain.
7. Try a handful of old URLs to confirm redirects work.
8. Submit the sitemap in Search Console and inspect your key pages.
9. Check analytics is recording live visits.
10. Update your Google Business Profile, social profiles, and email signatures with any new URLs.

Step six catches people out. Forms that worked on staging can break on the live domain because email settings were tied to the staging address. Test again. It takes five minutes.

Going live is the start of the job. The first month tells you whether the site is doing what you built it to do.

Expect some movement in search after a redesign. Small dips often settle. A big, sustained drop usually points to missing redirects or indexing problems.

Also ask a few real customers where they got stuck. Three honest conversations beat a month of staring at dashboards.

Most launch problems fall into a few familiar buckets. None need technical genius to avoid, just someone checking.

If your site is already live and you suspect a few of these are hiding in it, our list of signs your website is costing you customers is a sensible place to start.

We treat launch as part of the build, not a task tacked onto the final invoice. A beautiful site with a broken form is still a broken site.

We're a young studio, so we'd rather show you how we work than wave a wall of case studies around. If you're about to launch, or you launched recently and something feels off, get a free website audit and we'll check your site against this list and tell you what to fix first. If you'd rather hand the whole thing over, compare our website packages and pricing. For a look at how a build runs from brief to go-live, read about our 48-hour website build process.

A website launch checklist won't make an average site brilliant. What it does is stop a good site from being undermined by small, avoidable mistakes on day one.

Start two weeks out and finish content first. Test forms like a sceptic, check mobile on real phones, switch search visibility on, map your redirects, and confirm tracking works before you spend a cent sending traffic. Then watch the first 30 days closely.

The goal is a launch so uneventful nobody remembers it. The enquiries should be the exciting part. If you want a second pair of eyes before you go live, start with a free audit.