A Pre-Launch Checklist for a New Business Website

"Launch day" can feel like the finish line of a web design project, but a site that looks finished and a site that's actually ready to go live aren't quite the same thing. This guide sets out what's worth checking beyond "does it look right" before pointing a domain at a new site: the content and business details, the technical basics, the search and analytics setup, device testing, a printable checklist you can work through in an afternoon, the order to do it in on launch day itself, and the mistakes that cause most first-week problems.

The short answer: check more than how it looks

A website can look completely finished and still have a wrong phone number, a contact form that silently fails, or a stray line of code blocking it from search engines — none of which show up just from scrolling through the pages. A proper pre-launch check goes beyond visual review into content accuracy, technical basics and search visibility.

Content and business details to confirm

• Every contact method, tested live. Call the phone number, send the contact form, click the WhatsApp button — don't just read them, actually use them.
• Business details across every page. Address, opening hours, pricing and service descriptions should match reality, not an earlier draft or an old website.
• No placeholder text left behind. Draft headlines, dummy filler paragraphs, or "[insert testimonial here]" sometimes survive into a launched site if nobody does a full read-through.
• Legal pages present. Privacy policy, terms, and any disclosures relevant to the business's industry.

Technical checks before going live

An SSL certificate should be active (the padlock icon, not a security warning), every internal link should go somewhere real rather than a 404, and page load speed should be checked rather than assumed — a site that's fast on a good office connection can be noticeably slower on an average mobile connection. It's also worth confirming that a "noindex" tag or password protection used during development has actually been removed; sites have gone live invisible to Google because a leftover setting was never switched off.

SEO basics to have in place before launch

Meta titles and descriptions should be filled in on every page rather than left blank or on placeholder text, images should have descriptive alt text, and an XML sitemap should exist and be ready to submit to Google Search Console. None of this is complicated, but it's easy to skip when the focus during a project is on how the site looks rather than how it gets found.

If the new site replaces an old one, there is a second SEO job: every old address that ranked or was linked to should redirect to its new equivalent, so the search history carries over. Our guide to redesign versus rebuild covers the redirect map, and why a new site is not showing on Google covers what to check if it does not appear in the first weeks.

Analytics and tracking

Setting up Google Analytics and Search Console before launch, rather than after, means visitor data starts recording from day one instead of losing the first days or weeks while tracking gets configured retroactively — data that's useful for understanding how the launch actually performed. Three things are worth confirming specifically, not just assuming the installer worked:

• The tracking code fires on every page, not just the homepage — check the real-time report while clicking through a few inner pages.
• Form submissions register as a conversion, or at least an event, so enquiries can be counted rather than only guessed at from the inbox.
• Search Console is verified for the exact domain the site now lives on, including the www or non-www version actually in use, since the two are treated as different properties.

A worked example: what skipping redirects actually costs

A site relaunches with new page addresses and nobody maps the old ones. For the first week nothing looks wrong — the new site works, visitors typing the address directly land fine. Then the monthly numbers come in: organic traffic is down by a third, and Search Console is showing hundreds of "not found" errors against pages that used to rank.

Every one of those errors is an old link — from Google's own index, from other websites, from bookmarks — now pointing at a page that no longer exists. Each is a lost visitor and, over time, a small loss of the ranking those pages had built up. Mapping even the handful of pages that carried the most traffic to their new equivalents before launch, with a 301 redirect for each, keeps that history instead of starting over. Recovering after the fact is possible but slower: redirects added weeks later still help, but some of the lost ranking by then is gone for good.

Testing across devices

A layout that looks right on the designer's laptop can still break on a phone — oversized images, buttons too small to tap accurately, or text that overflows its container. Checking on at least one phone, one tablet, and one desktop browser before launch catches most of what a single-device review misses. See our guide on mobile-first design for why this matters so much for most small business audiences.

The full pre-launch checklist

Work through this in order. Most items take a minute; the whole list takes an afternoon.

Launch day, in order

1. Take a final backup of the old site, if there is one, and download it.
2. Confirm the checklist above is complete on the staging copy.
3. Remove the noindex tag and any password protection from the new site.
4. Point the domain at the new site, following the migration sequence if hosting is changing.
5. Open the live site on a phone and a desktop, logged out, and click through the main pages.
6. Send a test enquiry through every form and confirm each one arrives.
7. Check that email on the domain still sends and receives, if hosting moved.
8. Submit the sitemap in Search Console and request indexing of the homepage.
9. Confirm your own visit appears in analytics.
10. Update the website link on your Google Business Profile, social accounts and email signatures.

It's normal to keep adjusting after launch

Launch day doesn't mean every detail is locked in forever — small wording tweaks, photo swaps, and minor fixes after real visitors start using the site are completely normal. What a solid launch means is that the core structure, content accuracy and technical basics are handled, not that nothing will ever be touched again.

In the first two weeks, watch three things: whether enquiries are arriving, whether Search Console reports crawl errors, and whether analytics shows visitors leaving one page far faster than the others. Each is a small fix if caught early. After that, a monthly check of the maintenance basics keeps the site in the state it launched in.

Common mistakes

• Reading contact details instead of testing them. A form that fails silently loses enquiries for weeks.
• Leaving noindex on. The most common reason a new site never appears in search.
• Testing only on the designer's screen. Most visitors are on a phone; test there first.
• Launching without redirects from the old site. Years of search history point at pages that no longer exist.
• Setting up analytics after launch. The first weeks' data is gone for good.
• Forgetting the legal pages. A privacy policy is expected by visitors, and by the forms that collect their details.
• Not confirming who owns the accounts. Launch is the last easy moment to check the domain and hosting are in your name; see who owns your website.
• Treating launch as the end. It is the start of the maintenance cycle.

Where Gotka Technologies fits

Every Gotka web design project includes mobile-responsive design, page-speed optimisation, SSL, and basic SEO (meta titles, alt text, an XML sitemap submitted to Google) as standard, so these fundamentals are covered before a site goes live rather than left for the client to catch. An optional Care retainer from RM150/month covers ongoing monitoring and small edits after launch — see the full details on the package builder.

Key terms used in this guide

• Staging site: the private copy of the new site where it is built and checked before going live.
• noindex: a tag that tells search engines not to list a page; used during development and removed at launch.
• Robots file: a small file that tells search engines which parts of a site they may crawl.
• Meta title and description: the page title and summary search engines show in results.
• Alt text: the written description of an image, read by search engines and screen readers.
• XML sitemap: a list of every page on the site, submitted to search engines so they can find them all.
• Search Console: Google's free tool for submitting sitemaps and seeing crawl errors and search performance.
• Redirect (301): a permanent instruction sending an old address to its new one.
• Mixed content: an https page loading an image or script over http, which triggers a browser warning.
• Custom 404 page: the page shown for an address that does not exist, with your branding and navigation.