Confirm the agreed scope
Start with the written project scope. Check that the agreed pages, functions and content are present, and separate launch essentials from ideas that were deliberately left for later.
This protects both sides of the project. The business knows what it is reviewing, and unfinished future ideas do not become ambiguous last-minute requirements. Any genuine change can be described, priced and agreed before it is added.
Review the real copy
Read every page with the final or approved text in place. Placeholder copy can hide layout problems and makes factual review impossible.
Check names, services, service areas, contact details and claims. Make sure headings accurately describe their sections and that button labels explain the action. If the website includes prices, opening hours or other details likely to change, confirm who owns those facts and how they will be kept current.
Follow the important visitor journeys
Do not review pages only in isolation. Start where a visitor is likely to arrive and complete the route they are expected to take.
Can someone understand the offer, find the relevant detail and reach the next step without guessing? Does the navigation behave consistently? Are dead ends and unnecessary detours removed? Test the primary journey first, then the secondary routes.
Test forms and contact delivery
A form is not working merely because it displays a success message. Submit realistic test enquiries and confirm that they reach the intended destination. Check required fields, validation messages, privacy information and the response shown after submission.
Provide an alternative contact route where appropriate. Agree who will monitor enquiries and what response expectations the website should communicate. Remove test entries once the verification is complete.
Check current browsers and screen sizes
Review the site on representative phones, tablets and desktop screens. Check the actual navigation, headings, forms and calls to action rather than only the homepage screenshot.
Look for clipped text, awkward line breaks, overlapping controls and actions that are uncomfortable to tap. Test current major browsers relevant to the audience. The goal is dependable behaviour, not identical pixels in every environment.
Check accessibility in the finished interface
Accessibility belongs in the design and build, but the finished site still needs review. Confirm that headings follow a useful order, images have appropriate alternatives, controls are labelled and the interface can be navigated with a keyboard.
Check colour contrast, visible focus states and motion that could distract or disorient. Automated tools can help identify some issues, but they do not replace direct review of the actual experience.
Confirm domains, hosting and analytics
The business should know which account holds the domain, where the website is hosted and which paid services need renewal. Record the account owner, renewal route and practical recovery information outside the public website.
If analytics, cookie controls or third-party services are part of the agreed setup, confirm that they reflect the real site and are enabled only when the relevant decisions have been made. Domain and tracking changes should not happen by surprise.
Approve publication explicitly
A private review link is not publication approval. Record which version has been reviewed, what remains outstanding and who has authorised the public change.
Material edits after approval should return to review. This prevents a final unexamined change from slipping into the release simply because the rest of the website was already accepted.
Keep a practical handover
After launch, retain the source, account information, deployment notes and known limitations needed to operate or move the site. Confirm who is responsible for maintenance, backups and future content changes.
A clear handover is part of a dependable launch. It means the finished website is understandable as a working business asset, not only as a set of public pages.
The compact checklist
A dependable launch is not dramatic. It is a series of small checks that protect the visitor's first experience and the business's control after the site goes live.
- Agreed pages and functions are present.
- Final copy and business details are accurate.
- Primary visitor journeys work from start to finish.
- Forms deliver to the right destination.
- Current browsers and screen sizes have been checked.
- Accessibility checks have been completed on the finished interface.
- Domain, hosting, analytics and renewal responsibilities are recorded.
- The exact version has explicit approval to publish.
- Handover files and practical notes are ready.