Websites

A practical website launch checklist for a small business.

Launch is not only the moment a design becomes public. It is the point where content, technical signals, enquiries and ownership need to work together. This is the checklist RASTE uses as a practical way to think about a business-site release.

Check the customer journey

Open the site on a phone and desktop. Confirm that the main offer is understandable, navigation works, contact details are correct and important buttons lead where they say they will. Submit each form through the real workflow and verify who receives the message.

Check search foundations

Confirm that public pages can be indexed, canonical URLs use the production domain, language alternatives are reciprocal, the sitemap lists the intended public pages and robots rules do not block them. Review page titles, descriptions, headings, internal links and structured data against the visible content.

Check performance and accessibility

Use appropriately sized images, explicit dimensions and lazy loading below the fold. Look for layout shifts, slow interactions and unnecessary main-thread work. Test keyboard navigation, visible focus, form labels, heading order and reduced-motion behaviour. A fast score is useful, but the real target is a site people can use comfortably.

Record ownership after launch

Write down who controls the domain, hosting, analytics, Search Console, advertising accounts and content updates. Keep access in the proper account systems rather than shared passwords. Schedule a post-launch review using real search queries, page performance and enquiry quality instead of assuming the launch itself proves success.

← Back to the blog

Make this useful for your business.

If this is a priority for you, we can discuss the current setup and agree a sensible starting scope.

Let’s grow
01

Apply this to your website

Use the questions in this article to review your own pages. Write down the current situation, the change you want and who will provide the missing material. Add this context to your website brief so the build addresses a real decision rather than only changing the appearance. Keep the scope focused enough to check the result after delivery.