Give every page a job
Before checking colours and spacing, write down who the website serves and what that person should do next. A visitor should be able to understand your service, decide whether it fits and find a useful contact or booking route. Review the site as someone who has never heard of your business.
Read the actual published text, including mobile menus and confirmation messages. Confirm service areas, opening hours, prices and exclusions. Use only photographs, logos and testimonials you have permission to publish, and assign an owner to any information likely to change.
Test the whole customer journey
A working submit button is only the beginning. Send a clearly labelled test enquiry and check its arrival in the intended inbox or system. Ask the person handling enquiries to confirm that they have enough information to reply. Use an approved test environment for payment checks.
- Open the main pages on a phone and a desktop, and follow the primary call to action.
- Try a missing field, an invalid email and a long message; make sure errors explain how to recover.
- Check phone links, booking confirmations, cancellation instructions and language switching where offered.
- Agree who receives enquiries, when they are checked and what happens if delivery fails.
Check access and search visibility
Use the keyboard to move through navigation and forms, and check that focus remains visible. Zoom the page and look for clipped text. Meaningful images need useful descriptions; decorative images do not need repetitive labels. These are useful first checks, not a complete accessibility assessment.
Check that important public pages have descriptive titles, readable headings and links from the rest of the site. Confirm that launch pages are not accidentally marked noindex. Submit the sitemap through your search tools when access is ready; submission does not guarantee indexing or rankings.
Keep control after launch
Record who owns the domain, hosting, content and third-party accounts. Your business should know how to recover access without relying on one person's inbox. Agree which files and data are backed up, how restoration is tested and who authorises changes. Keep credentials in an appropriate password manager rather than in the launch checklist.
Name the person responsible for updates, renewal notices and content corrections. Separate defects covered by the project agreement from new work and optional ongoing care.
Make the release decision explicit
Keep a checklist with a result, responsible person and evidence for each important task. Resolve broken contact routes and incorrect commercial information before launch. Record less urgent improvements with an agreed follow-up date. A bounded Starter Website may fit a straightforward presence; multilingual content, substantial copywriting and connected systems need their own agreed scope. Send Skulbyte your page list, available content and required integrations so the proposal matches the work.