A website is ready to launch when a visitor can understand your business, complete the task they came for and contact you successfully. A polished homepage helps, but a working enquiry form and a recoverable backup are just as important.

This checklist is for small businesses, freelancers and first-time website owners. Work through it before sharing your address on social media, business cards or paid adverts.

1. Decide what the website must do

Choose one main visitor action: request a quote, book an appointment, buy a product or read your work. Make that action easy to find on the homepage and relevant service pages.

Write down your minimum launch pages. A service business might need Home, Services, About and Contact. A shop also needs clear product, delivery and returns information. Replace sample text and test contact details. Only publish testimonials and images you have permission to use.

Try this: ask someone unfamiliar with the business to explain what you offer after looking at your homepage for ten seconds. If they cannot, make the headline more specific.

2. Match the hosting to your website

Confirm that the plan supports your website software, storage needs and expected use. A static brochure site, WordPress shop and custom application have different requirements. If you cannot maintain a server yourself, ask exactly which maintenance tasks the provider handles.

Before buying, record the amount due today, contract length, renewal price and charges for email, backups or support. Check whether the advertised monthly price requires several years of payment upfront. Keep a copy of the order summary. Compare plans using the same period and the same essential features.

Ask the host: “Can you support my software, explain the resource limits, and show me how to restore a backup?” A clear answer is more useful than a long list of features you may never need.

3. Keep control of your domain and accounts

Use a business-controlled account for the domain registration and hosting. Keep recovery details current and enable multi-factor authentication where available. If a designer sets things up, agree who owns the accounts and how you will regain access if that person becomes unavailable.

Record renewal dates, payment details and a backup contact method securely. An account recovery email that depends entirely on the same domain can be inconvenient if the domain stops working. Never put passwords in a shared launch checklist.

4. Check HTTPS on the real address

Open your site using HTTPS and check that the browser reports no certificate warning. Test the main domain and any www address you intend to support. Confirm that old HTTP links reach the intended HTTPS pages.

Ask whether the host installs and renews certificates automatically. Let's Encrypt explains that many hosting providers manage this process for customers, sometimes through an option that needs enabling. HTTPS protects the connection; it does not prove that a business is trustworthy or that every part of a website is secure. [1]

5. Test the complete customer journey

Do more than click the homepage. Submit a genuine test enquiry and confirm that it arrives in the correct inbox. Check the reply address, confirmation message and spam folder. A success message alone does not prove that the email was delivered.

For a shop, use your payment provider's supported test mode to check checkout, order confirmation, delivery charges and failed payments. Check bookings and account creation if you offer them. Remove test content afterwards and confirm the intended live configuration before launch.

6. Make the site usable on a phone and keyboard

Open important pages on a real phone. Check menu buttons, text size, image cropping and form fields. Try a slower mobile connection as well as Wi-Fi. Large photographs can be resized and compressed before upload; retain an original copy separately.

Use the Tab key to move through links and controls. The focused item should be visible, and important tasks should work without a mouse. Give form fields clear labels, use readable colour contrast and provide appropriate text alternatives for meaningful images. W3C's Easy Checks is a useful starting point, although passing a few checks is not a complete accessibility assessment. [2]

7. Prepare for discovery and recovery

Give each main page a descriptive title and useful content. When the production site is ready, check that temporary launch restrictions are removed from pages you want people to find. Keep private test sites protected.

Use Google Search Console to inspect your homepage and submit a sitemap if your platform provides one. Google says crawl requests do not guarantee indexing, and discovery can take time. Repeated requests do not make the same URL crawl faster. [3]

Create a backup and confirm how it would be restored before launch. Assign someone to check enquiries, updates, renewal notices and backup results afterwards. A launch is the start of maintenance.

Final launch checklist

  • The offer and main action are clear.
  • Domain and hosting access belong to the business.
  • Renewal costs and dates are recorded.
  • HTTPS works without browser warnings.
  • Contact forms and important transactions have been tested.
  • The phone layout and keyboard navigation are usable.
  • Public pages are available to search engines as intended.
  • A backup exists and someone knows how to restore it.

Frequently asked questions

Do I need an expensive hosting plan to start?
Not automatically. Choose a plan that fits the actual website and support you need. Upgrade when measurements or a clear requirement justify it, rather than buying capacity for an imagined future problem.

Why is my new site not appearing in Google?
Check that it is publicly accessible and not unintentionally marked noindex. Search Console can help diagnose problems, but publication and sitemap submission do not guarantee inclusion. [3]

What should I do first today?
Run one full enquiry or purchase test from a phone, then confirm the result at the receiving end. This often reveals issues a visual review misses.

Sources and further reading

[1] Let's Encrypt — Getting Started: https://letsencrypt.org/getting-started/

[2] W3C WAI — Easy Checks: https://www.w3.org/WAI/test-evaluate/preliminary/

[3] Google Search Central — Ask Google to recrawl your URLs: https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl

Guidance checked: 9 November 2026. Provider features and prices can change; verify the details before purchasing.