Before a small business website launches it must clearly state the service and audience, contain real content rather than placeholder text, have a tested contact path that reaches the right inbox, load fast and work on a phone, be crawlable by search engines, use a branded domain and email, and have a documented handover covering domain and hosting ownership. Launching with gaps in any of these costs enquiries and trust.

A launch is not the moment a website goes online. It is the moment a website becomes the public face of the business. If the launch happens before the basics are ready, the site quietly loses enquiries, looks less credible than the business actually is, and has to be repaired in public.

This checklist is the no-excuses version. It is built from the recurring questions small business owners ask when a launch goes wrong, and it covers content, clarity, contact, technical setup, search visibility, email, accessibility and ownership. Work through it before launch day, not after.

The launch mindset

Most launch problems come from one misunderstanding: treating the website as a design object that needs to look finished, rather than a business tool that needs to work.

A page can look polished and still fail at its job. Placeholder text, an untested contact form, a missing mobile check, or a domain registered in someone else’s name are all invisible in a screenshot and fatal in practice.

The checklist below treats launch readiness as functional readiness. Each item answers a question the visitor or the business will actually ask.

Section one: clarity and content

The first screen and the first paragraph carry more weight than any other part of the site. If they are wrong, the rest does not get a fair reading.

Clarity checklist

  • The first screen states what the business does in plain language.
  • The intended audience is identifiable within seconds.
  • The main offer is specific, not a generic slogan.
  • The primary call to action is visible without scrolling.
  • Headings describe the section that follows.

Content checklist

  • All pages contain real content, not Lorem Ipsum or placeholder text.
  • Service descriptions explain scope, not just category names.
  • About page identifies the founder, team or company behind the business.
  • Contact details match the business identity.
  • Images are real, licensed or properly attributed, not random stock placeholders.
  • Copy has been proofread on the actual page, not only in a document.

Placeholder content is the most common launch failure. A site that goes live with “Add your content here” in a heading is telling every visitor that the launch was rushed.

Section two: the contact path

A contact form that does not deliver is worse than no form at all, because the business believes enquiries are arriving when they are not.

Contact checklist

  • The form or email link is easy to find.
  • The form has been submitted from a phone and a desktop browser.
  • The submission reaches the intended inbox, not spam.
  • Required fields are clearly marked.
  • Labels remain visible when fields are filled.
  • Error messages are specific and correctable.
  • A confirmation appears after submission.
  • Telephone and email links open the correct app on mobile.

If the contact path is untested, do not launch. Every other item on this checklist exists to bring a visitor to this point; if the point fails, the journey fails. The web.dev forms guidance is worth reading for the testing detail most teams skip.

Section three: technical performance

A clear message still has to arrive reliably. Slow pages, broken mobile layouts and unstable elements turn interested visitors into lost ones.

Performance checklist

  • The site works on a phone, not only on a desktop.
  • The largest visible image or text block loads promptly.
  • Images have sensible dimensions and compression.
  • Layout does not shift noticeably while loading.
  • Buttons and links respond promptly.
  • No obvious console errors on load.

You do not need to optimise the site into visual blandness. The goal is to remove technical delay while keeping the visual system distinctive. Read the first article in this series for the conversion-side reasoning behind why speed and clarity belong together.

Section four: search visibility and crawlability

A website that search engines cannot read will not appear in results regardless of how good it looks. Most crawlability problems are basic and avoidable.

Search checklist

  • Each page has a unique, descriptive title.
  • Each page has a meta description.
  • URLs are readable, not random strings.
  • Headings follow a logical H1 to H2 to H3 order.
  • Internal links use normal <a href> tags.
  • A sitemap exists and is reachable.
  • Robots.txt does not accidentally block important pages.
  • The site is registered in Google Search Console.

Google’s SEO Starter Guide covers these fundamentals in detail. They are not optional extras; they are the baseline that lets a site be discovered at all.

Section five: domain, email and identity

A free email address and a domain registered in a designer’s name are credibility and ownership problems that surface later, usually at the worst time.

Identity checklist

  • The domain is registered in the business’s name, not the designer’s.
  • The business uses branded email (for example [email protected]), not a free Gmail or Yahoo address.
  • The domain matches the brand name reasonably well.
  • HTTPS is active with a valid certificate.
  • Old or alternate domains redirect to the new one.

Branded email matters for both trust and deliverability. A business that sends quotes and invoices from a free address is signalling smallness and fragility, and is more likely to land in spam. The reasoning behind this is covered in the dedicated article on why business emails land in spam.

Section six: accessibility basics

Accessibility is not a separate launch phase. It is part of building a site that real people can use, including people on phones, in bright light, with slow connections, or using assistive technology.

Accessibility checklist

  • Images have descriptive alt text where it adds meaning.
  • Text has sufficient contrast against its background.
  • The site can be navigated by keyboard.
  • Form fields have associated labels.
  • Animation respects reduced-motion preferences.
  • The page language is set in the HTML.

The W3C WAI accessibility introduction explains why these matter for real users, not only for compliance. Accessible sites also tend to be more crawlable and more usable on mobile.

Section seven: analytics and measurement

You cannot fix what you cannot see. A site that launches without measurement is a site whose performance is invisible.

Measurement checklist

  • Google Analytics (or an equivalent) is installed.
  • The primary enquiry action is tracked as an event or conversion.
  • Google Search Console is connected and verified.
  • Spam and bot traffic are filtered where possible.
  • Someone knows how to read the basic reports.

Measurement is not the same as obsession. A few honest signals, tracked consistently, are more useful than a dashboard nobody opens.

Section eight: ownership and handover

The most expensive launch mistakes are the ones discovered months later, when the business tries to update the site, move hosting, or change providers and discovers they do not control their own presence.

Handover checklist

  • The business owns the domain registration account.
  • The business owns or controls the hosting account.
  • The business owns the analytics and Search Console accounts.
  • Login details for every account have been handed over in writing.
  • There is a written note of annual renewal dates and costs.
  • There is a written note of what to do if something breaks.

If any of these answers is “the designer holds it,” the launch is not fully complete. The site may be live, but the business does not yet own its digital presence. This single issue causes more disputes than any other in small business web design.

How to use this checklist

Do not try to complete every item in one pass. Use the checklist in this order:

  1. Two weeks before launch: resolve content, clarity and the contact path. These are the items most likely to delay the date.
  2. One week before launch: complete technical performance, search and accessibility checks.
  3. Three days before launch: verify analytics, ownership and handover documentation.
  4. Launch day: submit the form from a real phone, confirm the enquiry arrives, and check that the site appears in Search Console.

Treat anything left unticked as a known risk, not a finished item. A launch with three unchecked items and a plan to resolve them is honest. A launch declared complete with ten unchecked items is not.

What IDJoy includes at launch

The IDJoy working method treats launch as a handover, not a handoff. Each package is built so that the business owns its domain, hosting, analytics and email accounts after launch, with annual costs stated upfront rather than discovered later.

This matters because a checklist is only useful if someone is accountable for it. A clear handover means the business is accountable for its own presence, with the designer available for support rather than holding the keys.

The conclusion

A ready-to-launch small business website is one where the message is clear, the content is real, the contact path works, the technical setup is sound, search engines can read it, the identity is branded, accessibility is handled, measurement is in place, and ownership is documented.

Work through every section before launch day. The items left unticked are the items that will cost enquiries, trust and money after launch, when they are harder and more expensive to fix.

If you are preparing a launch and want a second pair of eyes on the checklist, describe the project and we will tell you which items need attention before the site goes live.