Small Business Website Launch Checklist: What to Test Before Going Live

Launching a small-business website is more than publishing the final design. A contact form can appear to work while sending messages to the wrong inbox; a page can look polished on a laptop but be difficult to use on a phone. A short, structured check before launch helps you catch problems while they are still straightforward to fix.

Use this small business website launch checklist as a final pass, not as a substitute for planning and testing during the build. If you are still shaping the pages, start by planning your website sitemap. Then work through the checks below on the actual site, ideally on more than one device.

1. Check the site’s essential information

Make sure visitors can understand what you do

Open the homepage as if you have never heard of the business. Within a few seconds, can you tell what is offered, who it is for and what to do next? A local accountant, for example, might make its service area and appointment option clear without asking visitors to read several paragraphs first.

Check that your business name, services, location or service area, opening hours and contact details are accurate wherever they appear. Confirm that prices, delivery information and availability are current. If you use a temporary offer or launch announcement, set a reminder to remove or update it.

Review the key pages and links

Visit every page from the navigation, footer and in-text links. Look for missing pages, links that lead to the wrong place, and labels that do not explain what happens next. “Contact us about a quote” is more useful than a vague “Learn more” when the action is specifically to request a quote.

Check that your privacy information is easy to find wherever you collect personal details. The UK Information Commissioner’s Office explains what organisations should cover in privacy information for people whose data they collect. Make sure the notice reflects what your business actually does with enquiry or booking details; do not simply copy a template without checking it.

2. Test the actions that bring in business

Submit every form yourself

Test contact, booking, newsletter and quote forms from start to finish. Use a real address you can check, and confirm that both sides of the process work: the visitor sees a clear confirmation, and the business receives the submission. Check the destination inbox, including spam or junk folders.

Try a realistic entry, then test what happens when a required field is left blank or an email address is entered incorrectly. Error messages should identify the problem and explain how to correct it. If a customer submits a form on a phone, the fields should be easy to tap and the keyboard should suit the information requested—for example, an email keyboard for an email field.

Also check any phone number, email address, booking link or payment route. On a phone, tap the number to see whether it starts a call. For payment or booking, use the provider’s test mode if available; do not make a live purchase merely to check the page.

Check what happens after someone gets in touch

Ask yourself who will respond, how quickly, and what the visitor has been told to expect. A small business may not reply immediately outside working hours. A brief confirmation such as “We’ll respond within two working days” sets a clearer expectation than a generic success message.

3. Test mobile layout, browser behaviour and speed

Use a phone, not only a desktop preview

Open important pages on a real phone if possible. Check that text is readable without zooming, buttons are not crowded together, and the main call to action is visible without an awkward hunt. Look at the menu, forms, image crops and any table or pricing comparison. A layout that technically fits a narrow screen can still be frustrating if a button is difficult to reach or a heading wraps into an unclear shape.

Test at least one other browser if you can, particularly if your site relies on embedded booking, maps or payment content. You do not need to test every device model. Focus on the pages and actions that customers use most, and fix anything that prevents them from completing a task.

Check loading and media

Load the homepage and a few key pages using a normal mobile connection. Notice whether the main text and action appear promptly, or whether a large image or video delays everything. Resize oversized images before uploading and avoid autoplaying video unless it has a clear purpose. If a page feels slow, investigate the largest images and third-party embeds first; they are often easier to address than a full redesign.

4. Check accessibility and readability

Accessibility means making the site usable by people with different abilities and ways of browsing, including keyboard users and people using screen readers. It also tends to make everyday tasks clearer for everyone. The W3C’s Web Content Accessibility Guidelines (WCAG) provide an established framework for checking web accessibility, though a quick launch review is not a formal conformance audit.

• Use the Tab key to move through links, buttons and form fields. You should be able to see which item has keyboard focus.
• Check that text and background colours have enough contrast to read comfortably. Do not use colour alone to communicate an error or status.
• Give meaningful images descriptive alternative text. If an image is purely decorative, it usually does not need a written description.
• Use headings in a sensible order, and write link text that makes sense when read on its own.
• Make sure form fields have visible labels, not just placeholder text that disappears when someone starts typing.

Read the copy aloud or ask someone unfamiliar with the business to review it. Replace internal jargon, explain necessary specialist terms, and break up instructions that combine too many actions.

5. Check search and sharing basics

Make important pages discoverable

Give each important page a clear, specific title and a heading that describes its subject. A page titled “Our services” may be less helpful in search results than one that identifies the actual service and, where relevant, the area served. Write a short description for key pages that accurately explains what a visitor will find. Google’s SEO Starter Guide covers the fundamentals of helping search engines understand site content; it does not promise a particular ranking.

Check that the site is not accidentally set to discourage search engines from indexing it. During development, a site may be password-protected or marked as noindex; make sure the intended public pages are available after launch. If you have a sitemap or analytics setup, confirm it reflects the live site rather than a staging address.

Preview links shared with others

Send a page link to yourself or a colleague and check how it appears in a messaging app or social platform. Confirm the page title, description and image are sensible. This is especially useful for a campaign or product page that customers are likely to share.

6. Confirm security, backups and ownership

Before launch, check that the live site uses HTTPS and that the browser does not show a security warning. Confirm that any third-party booking or payment page also uses a secure connection. Use strong, unique passwords for the website and hosting accounts, and enable two-step verification where it is available.

Know how the site can be restored if an update goes wrong. Check whether backups are running, where they are stored and how you would restore one. A backup you have never checked may not contain what you expect. Also confirm that the business—not only a former freelancer—has access to the domain registration, hosting, website platform and important account email addresses.

7. Make a simple launch-day plan

Write down who is responsible for publishing, testing the live domain and responding to enquiries. After the site is live, repeat the most important checks: open the homepage and contact page, submit a test enquiry, check the mobile menu and confirm that the domain resolves without a warning.

Keep a short list of anything that can wait, such as a minor wording improvement, separate from anything that blocks a customer task. This prevents a small imperfection from delaying a useful launch, while still making sure broken forms, inaccurate prices or inaccessible key information are fixed first.

A launch is the beginning of maintaining a website, not the end of the work. Review enquiry flow, page accuracy and customer questions in the first few weeks. Those real-world signals will help you decide what to improve next.

Frequently asked questions

How long before launch should I start testing?

Test as features are built, then do a final pass on the live site before announcing it. Leave enough time to fix issues found in forms, payments or important content rather than treating launch day as the first test.

Do I need to test every browser and device?

Not every model. Check a representative phone and desktop, and another browser if your audience or site features make that useful. Prioritise pages and actions customers rely on.

What should I test first if I only have an hour?

Start with the tasks that can lose a customer: submitting an enquiry, calling the business, booking or paying. Then check the homepage and contact page on a phone, followed by key links and the live domain.

Can I launch if some pages are unfinished?

It may be reasonable to launch without non-essential content, provided unfinished pages are removed from navigation and do not mislead visitors. Do not publish broken links, placeholder copy or incomplete information about prices, safety or terms.

Should I submit a test enquiry after launch?

Yes. A form can behave differently on the live domain than it did in a preview. Submit a clearly identifiable test, confirm it arrives, then remove or label it appropriately in your records.