Small business website launch checklist.

1. Confirm the goal, scope, and owners

A launch is easier to control when everyone knows what “ready” means. Write down the website's main audience, the primary action you want a visitor to take, and the pages included in this release. Move unfinished ideas to a later-work list instead of quietly adding them on launch day.

• Name the person who can approve content, design, technical changes, and the final launch.
• Confirm the production domain, hosting account, DNS provider, email provider, website platform, and who owns each account.
• Keep a secure record of administrator access and recovery methods. Do not place passwords in a public checklist or ordinary email.
• Agree on the launch window, change freeze, rollback decision maker, and how the team will communicate.
• List paid fonts, images, plugins, themes, software, and other licenses that must remain valid after handoff.

2. Read the website like a customer

Review the live-looking version on a phone and a larger screen. Begin at the homepage, then try to complete the most important task without using the project plan as a guide.

• Check that every page has one clear main heading and that later headings describe the sections beneath them.
• Confirm business name, service descriptions, prices, locations served, email addresses, team names, legal links, and dates against approved facts.
• Test navigation, footer links, buttons, breadcrumbs, downloads, and links inside the content.
• Remove placeholder copy, sample clients, stock testimonials, empty categories, draft prices, and unfinished pages from public navigation.
• Proofread on the rendered page. Look for awkward line breaks, clipped text, inconsistent punctuation, and instructions that assume too much.
• Check useful alternative text for informative images and empty alternative text for decorative images.
• Use the keyboard to reach every interactive control, see the focus indicator, open menus, complete forms, and dismiss any panel.
• Zoom the page, increase text size, and check narrow screens for horizontal scrolling or controls that are hard to tap.

Test every form as a real visitor

Submit valid details and common mistakes. Confirm labels, required fields, error messages, consent text, success and failure states, duplicate-submission protection, and the destination mailbox. Never assume a successful browser message proves the email arrived.

3. Check the search foundations

Search optimization starts with a useful page and a crawlable website. It is not a promise of rankings. Give each indexable page a distinct purpose and make sure the visible copy supports its title.

• Review the page title, meta description, canonical URL, robots directive, language, and social-sharing title, description, and image.
• Use permanent redirects from replaced URLs to the closest useful new page. Avoid redirect chains and sending every removed page to the homepage.
• Generate an XML sitemap from approved, indexable canonical pages only, then reference it from the robots file.
• Keep private, duplicate, thin, unfinished, and unapproved pages out of the sitemap and apply the intended indexing rule.
• Make internal links descriptive and ensure important service pages can be reached through normal navigation.
• Validate structured data against the visible page. Do not mark up reviews, prices, locations, people, services, or FAQs that the visitor cannot verify on the page.
• Check the production site in the search engine tools you actually use after launch; local validation cannot confirm public crawling or indexing.

4. Complete the technical and safety checks

• Confirm HTTPS works on the preferred hostname and that alternate HTTP or hostname versions redirect once to the canonical URL.
• Check the certificate, security headers, cache rules, compression, error handling, 404 response, and protection of environment or configuration files.
• Test current versions of the major browsers your audience uses at phone, tablet, laptop, and desktop widths.
• Measure representative pages on a production-like server. Review large images, render-blocking files, unused code, layout shifts, and slow server responses.
• Confirm images have suitable dimensions and formats, fonts load without hiding text, and scripts are deferred when they do not need to block rendering.
• Run a link check, HTML validation, automated accessibility scan, and manual keyboard review. Record accepted exceptions instead of silently ignoring them.
• Verify production backups, restore access, update responsibility, logging boundaries, and a safe way to share credentials when access is needed.

A perfect lab score is not a permanent property of a site. Hosting load, third-party services, devices, and later content can change the result. Save the test conditions and date with every measurement.

5. Follow a short launch-day runbook

1. Take the agreed pre-launch backup and record where it is stored.
2. Apply the change freeze, confirm the launch approver, and note the start time.
3. Publish the approved build or switch traffic using the agreed hosting and DNS method.
4. Check the homepage, one service page, navigation, a redirected old URL, the 404 page, robots file, sitemap, and one important form on the public domain.
5. Confirm the form message reached the intended mailbox without exposing the visitor's information in logs or error screens.
6. Check HTTPS, canonical URLs, indexing directives, structured data, and key response headers from outside the local development environment.
7. Record issues, owners, decisions, and whether the rollback threshold has been reached.

6. Finish the handoff and first follow-up

Launch is a milestone, not the end of website ownership. The handoff should identify who controls the domain, hosting, email, website, analytics or search tools, backups, licenses, and future updates.

• Provide the approved page list, redirects, account ownership record, license list, backup location, and restore instructions.
• Explain how enquiries are received, who monitors them, and what happens when delivery fails.
• Schedule checks for forms, errors, indexing, performance, and unexpected traffic changes after launch.
• Move non-urgent improvements into an owned maintenance list with a priority and review date.