The homepage is ready. The team has reviewed the copy. Everyone has an opinion about the hero image.
There’s one more kind of review worth doing before launch: follow the website the way a visitor will use it, all the way through the task they came to complete.
That review can reveal the problems a page-by-page approval misses. A contact form goes to an old inbox. A course link opens an outdated registration page. A useful confirmation message never tells someone what happens next.
Use these six checks to give your launch a practical final review.
1. Choose the journeys that matter most
Write down the three most important things visitors should be able to do. Use specific actions, such as finding a program, sending an inquiry, or following a registration link.
Start from the places people are likely to arrive. That might be the homepage, an individual course page, or a link shared in an email. Follow each journey without relying on your knowledge of where things belong.
Notice labels that require explanation, missing information, and moments when a visitor has to guess.
2. Check every handoff
When a visitor submits a form or leaves for another service, continue the review. Where does the request arrive? What confirmation does the visitor receive? Who responds, and what expectation does the website set?
Use appropriate test arrangements for purchases, donations, or other consequential actions. Confirm that the people receiving requests know the launch is happening and can handle the next step.
An action is only as useful as the handoff behind it.
3. Review on a narrow screen and with a keyboard
Check the important journeys on a phone-sized screen. Look for awkward menus, cropped text, hard-to-use controls, and forms that become difficult to complete.
Use a keyboard to move through navigation and form controls. Check that you can see where focus is and understand what each control does. Review headings, field labels, text readability, and useful image descriptions.
These checks are a starting point for accessibility review. Pair them with appropriate automated tools and a deeper review for your project’s requirements.
4. Make sure editors can do their work
Ask the people who will maintain the content to complete their regular tasks. Can they find the right page, update a date, replace a document, and publish through the intended workflow?
Check their actual roles and permissions. A successful review using an administrator account can miss the experience the everyday editor will have.
Record any instructions the team needs and put them somewhere easy to find.
5. Name the owners
Give important pages and incoming requests an owner. Agree who reviews user access, coordinates software maintenance, and contacts hosting support when needed.
Keep the contact details and recovery instructions accessible to the people who may need them. If one person is away, the team should still know how to get help.
For a useful breakdown of these responsibilities, read [who maintains your Drupal website](/blog/drupal-hosting-and-code-maintenance/).
6. Put the next review on the calendar
Choose a date to revisit the critical journeys after launch. Check what visitors asked, whether requests reached the right people, and where editors encountered friction.
Repeat the relevant checks after significant website changes. Keep the list short enough that the team will use it.
Whether you’re [bringing your own Drupal codebase](https://drupito.com/hosting) or [starting with a marketplace website](https://app.drupito.com/starters), walk the complete experience before inviting visitors in. A good launch gives them a clear path and gives your team a way to keep it working.