A website launch is more than making a new design visible. Customers need to be able to find the right information, contact your business, and complete important tasks without confusion. Before you share the link, check the live website as a customer would—not only as the person who built it.
This practical website launch checklist helps small businesses review content, mobile usability, enquiries, search visibility, and ongoing management. Use it for a first website or a replacement site, and record who is responsible for each check.
1. Confirm your business information
Review your business name, phone number, email address, opening hours, and service area on every important page. Check that contact details match the information your team actually uses. Click phone and email links to confirm that they open the intended destination.
Read service descriptions carefully. Remove placeholder text, sample prices, unfinished pages, and claims you cannot support. If you show customer testimonials or project photographs, make sure you have permission to use them.
Give each page a clear purpose. A visitor should understand what you offer and what to do next without having to search through several screens. Ask someone unfamiliar with the project to review the site; they may notice confusing language that your team has stopped seeing.
2. Test on a phone and a desktop
Open the live website on more than one screen size. Check the navigation menu, page headings, images, forms, and main buttons. Look for text that is cut off, content that requires sideways scrolling, and controls that are difficult to tap.
If your website includes light and dark themes, review both. Text, icons, input fields, and buttons should remain readable in either mode. Also check that a sticky header does not cover page content or make navigation difficult.
Do not stop at the home page. Visit your service pages, contact page, and any booking or checkout screens. A good first impression matters, but the complete customer journey matters more.
3. Send a real test enquiry
Submit each public enquiry form using an email address your team controls. Label the message clearly as a test so it is not confused with a real customer request. Check required fields, helpful error messages, and the confirmation shown after submission.
Confirm that the enquiry reaches the correct inbox or dashboard and that the submitted phone number and project details are included. If you promise a customer confirmation email, verify that it arrives and that its wording is accurate. Check the spam folder as well.
Test what happens when something goes wrong. A failed submission should not display a success message. Customers need a clear way to retry or contact you through another channel. Avoid promising an automatic WhatsApp notification unless that notification has actually been configured and tested.
4. Check links and key actions
Click your main navigation links, footer links, social links, and call-to-action buttons. Confirm that each one leads to the intended page. Remove links to temporary previews or unfinished destinations.
For booking websites, complete a test booking and check availability, confirmation, and cancellation instructions. For online stores, use the payment provider's approved test process where available. Review product options, delivery information, order confirmation, and how staff will handle an order.
Do not place a real paid order simply to see whether a button works. Agree on a suitable test process with the person managing your payment setup.
5. Review basic accessibility
Check that text is readable against its background and that information is not communicated by colour alone. Form fields should have understandable labels, and error messages should explain what needs to be corrected.
Try moving through navigation and forms with a keyboard. You should be able to see which control is focused and reach the important actions. Give meaningful images useful descriptions; decorative images do not need to repeat nearby text.
These checks are a useful starting point, not a substitute for a complete accessibility assessment. If your business has specific accessibility obligations or customer needs, arrange an appropriate review before launch.
6. Review search visibility essentials
Ask your developer to check that public pages have descriptive page titles, clear main headings, and the intended canonical URLs. Public marketing pages should be available to search engines, while private dashboards and account areas should not appear as public landing pages.
Check that your XML sitemap lists the intended public pages and that robots.txt references the sitemap without blocking files needed to render the website. A sitemap helps discovery, but does not guarantee that every page will be indexed or ranked.
If you are replacing an existing site, identify old URLs that customers or search engines may still use. Relevant redirects can help people reach the corresponding new pages. Do not redirect every removed page to an unrelated destination just to avoid an error.
7. Check loading and image quality
Open the website on an ordinary mobile connection as well as your office connection. Notice whether important text and buttons appear promptly and whether images cause the layout to jump while loading.
Use images that are appropriately sized for their placement. A small card does not usually need the original full-resolution photograph. Ask your developer to review unnecessarily large assets and any third-party widgets that slow the page down.
Balance visual quality with practical usability. A decorative animation should not prevent someone from reading your services or submitting an enquiry.
8. Confirm ownership, access, and backups
Know who controls your domain, hosting, business email, and website administrator accounts. Keep access arrangements clear, and avoid using a shared administrator account for everyone who needs to edit content.
Ask how backups are created, where they are stored, and who can restore them. A backup is most useful when there is a clear recovery process. Keep a record of the support contact and the steps to take if the site becomes unavailable.
If your website stores enquiries, clients, bookings, or invoices, check that a saved record remains available after reopening the site or using another authorised device. Data that exists only in one browser is not a reliable shared business record.
9. Agree on a final sign-off
Create a short launch record with the checks completed, remaining issues, and the person approving publication. Resolve issues that stop enquiries, bookings, purchases, or access to essential information before promoting the site.
Smaller improvements can be placed on a follow-up list, but give each one an owner. Avoid treating an unfinished feature as complete simply because the home page looks ready.
10. Keep checking after launch
Once the website is live, repeat a test enquiry and revisit important pages from the public domain. Review any available error reports and confirm that your team knows where new messages arrive.
Over the following weeks, review genuine customer questions and the actions visitors take. Use that information to improve unclear content or unnecessary steps. Website maintenance is an ongoing responsibility, not only a launch-day task.
Frequently asked questions
When should I share my new website?
Share it after the essential pages and customer actions have been tested on the live domain. If a key form or booking process is not working, fix that first or provide a clearly explained alternative.
Does a sitemap mean my website is on Google?
No. A sitemap provides information about public URLs, but discovery, indexing, and ranking are separate processes. Check the site's search monitoring tools rather than assuming submission means immediate visibility.
Do I need to test every form?
Yes. Different forms may use different settings or destinations. Test each one, check the received details, and confirm that the customer sees an accurate result.
Plan a confident website launch
A clear checklist helps your team launch with fewer surprises. Start with accurate information, reliable customer actions, and a practical plan for maintenance. InfoTech Coder can help you discuss website development and the checks your project needs before publication.
Explore our services: https://infotechcoder.com/services/
Tell us about your project: https://infotechcoder.com/request-quote/