Before you launch: start with the visitor journey
A website can look finished in a design preview and still fail on its first working day. A contact form might not deliver messages. The main button might disappear on a small screen. A service page might contain a placeholder paragraph, or a search setting might accidentally hide the whole site from Google.
A good pre-launch review catches those problems before customers encounter them. You do not need a large quality-assurance team. You need a repeatable process, a few realistic visitor tasks and a clear decision about which issues must be fixed before launch.
Quick answer: Before launching a business website, review the content, navigation, mobile experience, working links, enquiries, accessibility, performance, search settings, security and analytics. Test the critical customer journey end to end, then record any remaining issues with an owner and a deadline.
1. Decide what the website must help a visitor do
Start with the purpose of the site rather than the appearance of the homepage. A local service business may want visitors to understand the offer, examine past work and send an enquiry. A consultant may need visitors to compare expertise and book a call. An online shop has a different critical journey: finding a product, checking the details and completing checkout.
Write down three visitor tasks before you test anything. For a creative agency, those tasks might be: find website design services, view relevant examples in the portfolio, and reach the enquiry form. Ask someone unfamiliar with the website to complete each task without hints. Their hesitation often reveals problems that the project team has learned to ignore.
2. Check the message on the homepage and service pages
Read the website as if you knew nothing about the business. Can you tell what it does, who it helps and what comes next? Confirm that the headline is specific; service descriptions explain outcomes; real contact information is correct; and temporary design copy such as “Lorem ipsum,” “Coming soon,” or dummy client names has been removed.
For businesses with several offers, make sure the services are grouped around customer needs. A visitor looking for a logo should not have to guess which abstract menu category contains logo design. Check that portfolio descriptions are accurate and that claims about clients, experience and results can be supported.
3. Test navigation and every important next step
Click through the header menu, footer links, service cards, portfolio buttons and breadcrumb links. Check the destination rather than merely noting that something is clickable. A “See our work” button should show examples; a “Request a quote” button should lead to a real enquiry path.
Keep button language clear and honest. The guide on calls to action that feel clear rather than pushy explains how wording helps people predict the next step. On a mobile device, make sure menus open, close and remain usable with touch or keyboard controls. Avoid links that unexpectedly open empty or unrelated pages.
4. Review the layout on actual phones, not only a desktop preview
Look at a narrow phone screen and a tablet or laptop. Read the first screenful, scroll through long sections and complete the main visitor task on each. Watch for overflowing headings, tiny text, cramped buttons, horizontal scrolling and images that crop important information. Check both portrait and landscape when the interface changes meaningfully.
Mobile readability is about more than shrinking desktop columns. Shorter headings, understandable section breaks and enough spacing can help customers scan without losing context. Use the practical checks in making a website easier to scan on mobile for a more detailed review.
7. Measure speed and visual stability
Test a few important pages on a real mobile connection, then use a tool such as PageSpeed Insights or Chrome Lighthouse to find likely slowdowns. Look particularly at large hero images, video embeds, heavy scripts and unexpected movement as the page loads.
For context, Google's Core Web Vitals guidance focuses on loading performance (LCP), interaction responsiveness (INP) and visual stability (CLS). Tools can help prioritize improvements, but one lab score is not a guarantee of every visitor's experience. Fix obvious blockers first, especially when they interfere with reading or submitting an enquiry.
9. Check SEO basics before search engines visit
Every important page should have a descriptive title, a useful meta description and a sensible heading structure. Check that its URL is readable and that it points to the correct canonical version of the site. Make sure a staging-only noindex rule has not accidentally remained on pages intended for public search.
Review robots.txt and the XML sitemap, and include the pages you actually want Google to discover. Google's sitemap documentation explains that a sitemap communicates preferred URLs but does not guarantee indexing. Do not add duplicate articles or keyword-stuffed pages simply to increase the page count. A clear website design service page should answer a visitor's question better than several nearly identical alternatives.
10. Confirm security, privacy and business ownership
Visit the website using its public HTTPS address and confirm the browser does not report certificate problems. Check that the primary domain is used consistently, including in email links, social profiles and canonical tags. Verify that admin-only pages are protected and that public forms do not display private submissions or secrets.
Review the accuracy of the privacy notice, contact details and any required consent settings. Ask who controls the domain, website source, hosting account, analytics property and business email. A launch should not leave the business dependent on an unknown password or a single contractor's personal account.
11. Confirm analytics and follow-up processes
If you use Google Analytics or Search Console, confirm the correct property and domain are configured. Check that page views and meaningful conversions can be measured in a privacy-conscious manner. Avoid firing duplicate analytics scripts or treating every button click as a confirmed enquiry.
Agree who receives incoming requests, who answers them and how quickly. A website that generates leads but fails to deliver or respond to them still has a business problem. If the site supports several services, pass the selected service or enquiry context to the person replying whenever appropriate.
12. Run the final go/no-go test and schedule a post-launch check
Do one final end-to-end pass in a fresh browser session. Start on the homepage, select a service, open an example, send a test enquiry and confirm the result. Repeat the key task on a phone. Record each problem with its severity and an owner.
Use a simple launch decision:
Go/no-go launch decision by issue severity| Severity | Example | Decision |
|---|
| Launch blocker | Contact form fails; important page is missing; private data is exposed | Fix and retest before launch |
| High priority | Mobile menu unusable; main service button goes to the wrong page | Fix before launch when it blocks the key visitor journey |
| Improvement | Minor spacing issue; optional illustration could be clearer | Assign an owner and review after launch |
After publishing, reopen the live site rather than trusting the development preview. Recheck the contact form, sitemap and important pages. Then review genuine search impressions and user feedback over the following weeks, allowing time for crawling and data collection.
A practical 15-minute final checklist
Before signing off, ask one person outside the project to check these items:
- Can they understand what the business offers within a few seconds?
- Are the main service and portfolio links correct?
- Does the navigation work on a real phone?
- Can they read the text without zooming or horizontal scrolling?
- Does a test enquiry actually arrive at the intended inbox or lead system?
- Are there no placeholders, broken images or obviously broken links?
- Are keyboard focus, form labels and error messages usable?
- Are the main page titles, canonical URLs and sitemap reasonable?
- Does the public HTTPS site load without warnings?
- Is someone responsible for responding to enquiries after launch?
Frequently asked questions
When should a small business do a website pre-launch review?
Run an initial review as soon as the main pages and forms work, then repeat the important tests before launch. Check the live production site again immediately after publishing because environments, redirects and integrations may behave differently.
Do I need to achieve a perfect performance score before launch?
No single score guarantees a good experience. Prioritize broken journeys, accessibility barriers and major loading problems. Use performance tools to identify changes worth testing rather than chasing a perfect number for its own sake.
Does submitting a sitemap mean my pages will appear on Google?
No. It helps discovery, but Google decides whether and when to crawl and index individual pages. A sitemap is one part of a wider process involving useful content, reachable URLs and technical accessibility.
Should I launch with unfinished pages?
That depends on what is unfinished. A minor optional enhancement can wait. A broken enquiry path, misleading service information, security concern or critical missing page should be resolved before inviting customers.
Final thought
The purpose of a website launch checklist is not to create paperwork. It is to protect the moments when a visitor decides whether a business looks trustworthy enough to contact. Test real tasks, fix the issues that block them and make one person responsible for what happens after the site goes live.
If you are planning a launch, begin with a clear understanding of your website design requirements, then use this checklist to review the finished site together with your developer or team.