Before You Publish Your Website: A 15-Minute Small-Business Launch Check

A website can look finished and still fail at the moment that matters. The phone number may not work on mobile. The enquiry form may submit without reaching anyone. A service page may describe the work but never explain the next step. Analytics may record visits while missing every lead.

These problems are easy to overlook because the person launching the site already knows how it is meant to work. A customer does not. Before announcing a new site or major update, spend 15 minutes using it like someone seeing the business for the first time.

What you should take away

A website is ready to launch when a customer can understand the offer, complete the main action on a phone, receive clear confirmation, and reach a monitored destination. Search visibility, accessibility basics, and measurement should be checked before promotion begins, not after leads go missing.

Minutes 1-3: Find the next step on a phone

Open the website on your phone in a private or incognito window. Start on the homepage and answer three questions without using knowledge from inside the business:

• What does this business offer?
• Who is the offer for, or where is it available?
• What should I do next?

The main action might be calling, booking, requesting a quote, buying, visiting a location, or sending an enquiry. It should be visible without hunting through several pages. Tap every important phone number, email address, booking link, and primary button. Confirm each one opens the right destination.

Check the longest page as well as the homepage. Text should remain readable, buttons should fit the screen, and menus should not cover content. Rotate the phone once and increase the text size. These quick tests expose layouts that only work in the designer's preferred view.

Minutes 4-6: Complete the real customer journey

Submit the enquiry, booking, signup, or checkout flow with test details. Do not stop when the button changes colour. Verify the whole chain:

• The form explains required information before submission.
• Errors say what needs fixing and keep information already entered where appropriate.
• The customer receives a clear confirmation on screen or by email.
• The message, booking, or order reaches the correct business inbox or system.
• Someone knows who owns the follow-up and how quickly it should happen.

This is the most important part of the check. A polished form that sends enquiries to an old inbox is worse than an obvious error because the business may not notice the loss.

Minutes 7-9: Check trust and accessibility basics

Read the page once for trust. Confirm the business name, contact details, service area, opening hours, prices or price qualifiers, delivery information, guarantees, and current offers. Remove expired dates and placeholder text. Check that important claims can be supported and that conditions are not hidden.

Then use the keyboard only. Press Tab and make sure you can see where focus moves, open the menu, reach each form field, and activate the main action. Check that form fields have visible labels, images that carry meaning have useful alternative text, headings describe the sections below them, and text has enough contrast to read comfortably.

This is a first review, not an accessibility certification. The W3C's quick checks are designed to reveal common barriers, while a complete assessment requires broader testing.

Minutes 10-12: Check search visibility

Open the browser tab and look at the page title. It should describe the page, not say Home, Untitled, or the name of a website builder. Each important page should have one clear main heading and words customers would use when searching for the service.

Confirm the live site is not carrying a temporary noindex instruction from development. Make sure important pages are linked from the navigation or another crawlable page, and submit an up-to-date sitemap through Google Search Console where appropriate. These steps help discovery, but they do not guarantee ranking or traffic.

Minutes 13-14: Prove measurement works

Visit the site using a test campaign link or a private window, then complete the main conversion. Check that analytics records the visit and the action you care about, such as an enquiry, booking, purchase, or phone click.

Page views alone are not enough. If the business cannot tell whether the website produced an enquiry or sale, it cannot judge whether future advertising, SEO, or design changes helped.

Minute 15: Assign launch ownership

Before announcing the site, write down:

• Who checks forms, bookings, orders, and key pages after launch?
• Who receives website alerts and customer enquiries?
• Where should a problem be reported?
• Who can restore the previous version or contact the developer?
• When will the business review leads, errors, and analytics again?

A useful rhythm is one check immediately after launch, another the next business day, and a broader review after enough real visitors have used the site. The exact timing should match the site's traffic and business risk.

Copy this launch check

• The offer and next step are clear on mobile.
• Phone, email, booking, and primary buttons open the right destination.
• The main form or checkout works from start to finish.
• Confirmation reaches both the customer and the business.
• Contact details, hours, prices, offers, and claims are current.
• Keyboard focus, labels, headings, contrast, and meaningful image text pass a basic review.
• Page titles, main headings, crawlable links, and sitemap are ready for search.
• Analytics records the main conversion, not only page views.
• One person owns monitoring and follow-up after launch.

Takeaway

Do not judge launch readiness from the homepage screenshot. Follow the path a real customer must take: understand, choose, act, receive confirmation, and get a response. Fifteen focused minutes can catch the failures that matter before promotion sends more people into them.

Source note: This article was informed by the public Front-End Checklist, Google Search documentation, W3C accessibility guidance, web.dev performance guidance, and recent technology-newsletter signals. It is original general guidance for small-business owners and is not a complete technical, accessibility, privacy, or legal audit. AI-assisted research and drafting were reviewed, edited, and adapted by Maud & FranFort Technologies.

Further reading: Use the Front-End Checklist for deeper technical checks, Google's Search Essentials for search fundamentals, the W3C's accessibility easy checks, and web.dev's Core Web Vitals workflow.