Website essentials

A small business website launch checklist you can actually use

Review content, mobile navigation, contact routes, accessibility and ownership before sharing your new business website.

THE KEY IDEA

Test the journey a visitor needs to complete. A launch is ready when the important pages and contact routes work together.

Choose one useful visitor journey

Write one sentence describing what a visitor should achieve: understand your service, read an explanation or contact the right person. Then open the home page as if you have never seen the business before. Can you tell who it serves and where to go next without guessing?

Follow that path all the way through. A “Read the guide” button should open the promised guide; a contact button should lead to a real, monitored contact route. Remove unfinished features and explain what happens after a visitor leaves your website for a service provider.

Check the words and the important links

Read the live version, not just the document used to prepare it. Check the business name, service descriptions, page headings and contact address. Replace sample text and remove unsupported claims about results, customers or partnerships.

  • Open each main navigation item and its submenu.
  • Follow the main button on every service page.
  • Check policy links and return links on article pages.
  • Visit a deliberately missing address to confirm useful recovery links.
  • Ask someone unfamiliar with the site to explain what they think it offers.

Keep a short issue list with the page address, the problem and its owner. Fix a broken contact route before spending time on decorative details.

Use a phone, a keyboard and larger text

Check a narrow phone screen and a wider desktop screen. Long headings, menus and comparison tables should remain usable without hiding the next action. Try larger browser text or zoom and make sure content remains readable.

Put the mouse aside and use Tab to move through links and controls. Check that focus is visible and that menus can be opened and closed with the keyboard. Give meaningful images useful alternative text and make labels explain what form fields request.

W3C’s Easy Checks covers titles, headings, images, contrast, keyboard access and forms. Use it as an initial review; completing a short checklist is not a complete accessibility evaluation.

Test delivery and loading on the live address

Open the published HTTPS address on another device or connection when possible. Check important images, downloads and article links. For a contact form, send a clearly identified test and verify receipt and the confirmation message. For email-only contact, verify both delivery and the ability to reply.

If images slow the page, ask the site maintainer to review their dimensions, compression and loading behavior. Google’s web.dev guidance describes deferring off-screen images and cautions against delaying an important image visible when the page first opens.

Make a handover before promotion

Write down who can publish a correction, who owns the domain account and who responds to enquiries. Save an approved copy of the content and agree how to recover the site if a change fails. Our website backup plan explains what to ask for.

Share one useful page with the audience it serves and invite specific feedback, such as “Was this checklist clear?” Use relevant communities only where sharing is welcome. Keep a simple log of the channel, article and date; review genuine questions to decide what to explain next.

Begin with the online presence guide if the website’s purpose is still unclear. If a visitor reports a problem, collect the page address and expected action through our contact page.

Sources & further reading

Primary references checked 9 November 2026. The checklists and examples are BizGuide’s planning guidance; confirm account-specific instructions with your provider.

General educational information. This checklist does not replace a technical assessment of your own website or provider terms.

Useful? Pass it on.Share by email ↗Follow via RSS ↗
← Back to the journal