A website can look finished long before it’s ready to launch.

The homepage is polished, the colours are right and everything seems fine on the designer’s laptop. But then you try the contact form on a phone and the button doesn’t respond. Or the new site goes live and an old service URL disappears. Or nobody knows whether enquiries are actually reaching the business.

Those are the details worth catching before launch day.

I like to think of a website launch as a series of small checks, not one big dramatic moment. Here’s the checklist I’d use to make sure a business website is ready for real visitors.

Start with the most important question: can customers use it?

Before checking the technical details, walk through the website like someone who’s never seen your business before.

Good launch preparation starts earlier with what to prepare before hiring a website designer.

Can you tell what the company does within a few seconds? Can you find the services, products or information you came for? Is the next step obvious? Does the page give you enough confidence to take that step?

Try a realistic task. Find a service, read about it and submit an enquiry. Or find the business’s location and opening hours. If any part of that journey feels confusing, write it down.

A successful launch isn’t just a site that loads. It’s a site that helps people do what they came to do.

Check every page for content mistakes

Read the website carefully, ideally with someone who didn’t write the copy.

Check the business name, phone number, email address, location, hours, service descriptions and any prices or policies. Look for placeholder copy, duplicated sections, awkward headings and claims you can’t substantiate.

Make sure images are approved for use. Check that testimonials are genuine and that any client names or results can be published. If there are team photos, captions should identify the right people.

Pay special attention to the homepage and contact page. They’re often the most important pages, and errors there can affect trust quickly.

Test the website on real phones

A responsive preview is useful, but I wouldn’t sign off on mobile design without checking actual phones as well.

Test the navigation menu, buttons, text size, spacing, images and forms. Rotate the device. Try long headings. Check whether important information gets buried behind decorative sections.

Try tapping with one thumb. Can you reach key controls comfortably? Does a form field bring up a sensible keyboard? Can you understand error messages without guessing?

Then repeat on a larger screen. The point isn’t to make everything identical. It’s to make each layout usable.

This is easy to rush and expensive to miss.

Check navigation links, calls to action, footer links, download buttons, social links and links inside blog articles. A link shouldn’t lead to an empty page, an unexpected error or the wrong destination.

Submit each form with valid information. Then test invalid or missing information. Does the user get a clear success or error message? Does the enquiry actually arrive at the intended email or system? Is the message legible when it gets there?

If the website has booking, payment or account features, test the complete workflow, including what happens when someone cancels or encounters a problem.

Don’t assume a green success message means a form is working. Verify the receiving end.

Check the basic SEO setup

Good SEO begins with clear pages that search engines can access and people can understand.

The custom website design guide explains how SEO fits into the structure before launch.

Every important page should have a unique, useful title and a meta description that accurately describes what the page offers. Each page should have one clear main heading and descriptive subsections. URLs should be readable and stable.

Check that important pages are included in internal navigation or linked from other relevant pages. Search engines need discoverable links; visitors do too.

If the site should appear in search, confirm that production pages are not accidentally set to “noindex” and that robots settings aren’t blocking the pages you need crawled. Review the XML sitemap and submit or monitor it through Google Search Console where applicable.

A sitemap doesn’t guarantee indexing, and a meta description doesn’t guarantee a particular search snippet. These are fundamentals, not promises about rankings.

Keep existing URLs and redirects in mind

This is especially important when you’re replacing an existing website.

If the project began with a choice between approaches, custom website vs template outlines the longer-term trade-offs.

Make a list of useful old URLs, including service pages and blog posts. If their addresses are changing, plan appropriate permanent redirects to the most relevant new pages.

Don’t redirect every missing URL to the homepage just to avoid a 404. Visitors should reach information that actually matches what they expected.

Check canonical URLs, especially if the site can be accessed with or without “www” or through several domains. Important internal links should point consistently to the preferred addresses.

If a page has genuinely gone away and there’s no relevant replacement, a proper not-found response is better than a misleading redirect.

Check loading and layout stability

A fast website feels better to use, especially on mobile connections.

Look for oversized images, unnecessary video backgrounds, fonts that load slowly and scripts that add little value. Test pages with your real content, not only placeholder images.

Tools such as PageSpeed Insights can help you identify issues. The Core Web Vitals to be aware of are Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). They describe loading experience, responsiveness and unexpected visual movement.

Scores are useful clues, not the whole experience. A page can score well in a test and still be confusing. Fix the problems that affect real visitors.

Check accessibility basics

Accessibility shouldn’t be an optional final polish.

Make sure you can navigate the site using a keyboard, not just a mouse. Check that visible focus states show where you are. Buttons and links should be identifiable. Form fields need understandable labels and helpful errors.

Text should have enough contrast against its background. Headings should follow a logical order. Meaningful images need useful alternative text; decorative ones shouldn’t add unnecessary noise to screen readers.

If a video contains important speech, consider captions. If you use motion or animation, ensure it doesn’t make the interface uncomfortable or prevent someone from completing a task.

A quick automated accessibility checker can catch certain issues, but it can’t replace human testing.

Verify analytics and privacy settings

If you’re measuring enquiries, purchases or bookings, test the tracking before launch.

Check that analytics is connected to the correct property. Confirm that important actions generate the intended events or conversions, and look for accidental duplicate events.

If you use marketing pixels, cookie controls or consent tools, make sure their behaviour matches your actual privacy choices and the requirements that apply to your business. Don’t publish a generic privacy statement that doesn’t describe what you’re collecting.

Keep the measurement plan simple. Useful numbers are better than dozens of events nobody checks.

Confirm domain, hosting and website ownership

Before launch, make sure you know who controls the domain, DNS, hosting and relevant third-party accounts.

Make sure the project scope and ongoing costs are clear; see what a custom website quote should include.

Confirm that HTTPS works on the production domain and that visitors aren’t seeing certificate warnings. Check that the production domain points to the intended site and that temporary preview links aren’t being used as canonical public URLs.

Document who can access the website after launch. If the site has a content editing system, decide who can publish changes and how updates or backups are handled.

For a business, ownership and access aren’t administrative trivia. They’re what allow the website to keep working when people or suppliers change.

Have a simple launch-day plan

You don’t need a complicated launch ceremony, but you do need a clear order of operations.

First, make sure someone has approved the content and design. Save a working copy of the previous site or relevant files where possible. Confirm who is responsible for deployment and who can fix something if it goes wrong.

When the new site is live, check the actual public domain—not just the preview. Visit the homepage, a service page, a blog post and the contact page. Submit a test enquiry. Try the mobile navigation. Check your redirects.

If the site replaces an older one, spot-check important URLs and any advertising landing pages that might still receive traffic.

Keep a short list of issues and prioritize anything that prevents people from contacting, booking or buying.

What to check after launch

Launch isn’t the end of quality assurance.

Over the next few days, confirm that enquiries are arriving, that visitors can use the important pages and that search engines can access the site. Check Search Console for indexing or crawling issues when data becomes available.

Watch for 404 errors, broken integrations, unexpected layouts and customer questions that the website should answer more clearly. Small improvements based on real feedback are more useful than redesigning the site immediately.

If your business changes, keep the service details, contact information and policies current. Publish new articles when you have something helpful to add, not simply to make the blog look active.

A launch checklist you can hand to your team

Before publishing: approve all words and images; check contact details; test phones and desktop screens; click links and submit forms; review accessibility; check titles, headings, indexability and internal links; prepare redirects; verify tracking; and confirm account access.

On launch day: deploy to the correct domain; check HTTPS; inspect real public pages; submit a test enquiry; test old and new URLs; and confirm that the correct people can make updates.

After launch: review enquiries and analytics; monitor crawl or indexing problems; fix broken links and 404s; and collect real customer feedback.

If you’re working with a designer, ask them to show which of these checks are included in the project and which are your responsibility.

The part I’d never skip

If I had to choose one final check, it would be the full customer journey on a real phone.

Start on the homepage. Find the right service. Read enough to understand it. Click the call to action. Complete the form. Confirm that the enquiry reaches the business.

That’s the moment when all the design decisions meet reality. If it works smoothly, you’re in much better shape to launch.

At Cielle Designs, I want a launch to be about a working, understandable website—not just a beautiful screenshot.

Frequently asked questions

How long should website testing take?

It depends on the number of pages and features. A simple informational website needs different testing from one with payments or accounts. Allow enough time for fixes and another round of checks instead of testing only on launch day.

Can a website launch before all its blog posts are ready?

Yes, if the essential pages are accurate, useful and functional. You can publish additional articles as they’re finished. Avoid publishing thin placeholders just to fill a blog grid.

Do I need a sitemap for SEO?

A sitemap helps search engines discover URLs, particularly on some larger or newer sites, but it doesn’t guarantee indexing. Internal links, crawlable pages and good site structure also matter.

Should I change all my old URLs during a redesign?

Usually not without a reason. Stable, useful URLs are worth keeping when possible. If they must change, map relevant old URLs to suitable new destinations and test the redirects.

Is my website finished once it’s live?

The initial project may be finished, but a website still needs accurate content, functioning integrations, security and occasional improvements as the business evolves.

If you would like to talk through what your business website needs, you can book a free consultation with Cielle Designs.