By Touchbase Technologies · Published
Before launching your website, complete the visitor's task
The website looks finished in the editor. The heading fits, the images are in place and the main button is easy to see. Then a visitor opens the published link on a phone and finds that the button leads to a page requiring an unexpected login.
A launch review should test the page people will actually use. This checklist gives a small-business owner and a website builder a shared way to review that experience. It includes a fictional service-business example and a release log you can adapt. It is a practical starting point, not a complete technical, security or accessibility audit.

Photo by fauxels on Pexels, used under the Pexels License. This stock photograph illustrates work at computers; it does not depict a Touchbase customer project or an endorsement.
Write down the one task the page must support
Begin with a sentence such as: “A visitor can understand the installation service, check whether their location is covered and request a consultation.” That is more useful than “the homepage works” because it gives the reviewer a sequence to complete.
Choose the task that matters for this release. A product page might need to explain an offer and lead to an appropriate signup. A local service page might need to provide service details and a working contact route. A support page might need to help someone resolve a specific problem.
Record what counts as finishing. Clicking a button is not always the result. The result might be a visible confirmation, a correctly opened contact method or a completed booking in the intended system. Name the evidence the reviewer should see, and identify which parts depend on another provider.
Review the published address outside your editing account
Copy the actual public URL and open it in a signed-out browser when the website is intended for new visitors. Do not rely only on the editor's preview or on a session that already has access to every connected service.
Check the starting page and the destination of its primary action. If the journey intentionally includes an account or payment step, the page should explain that before the visitor reaches it. If the page is meant to provide public information, an accidental account requirement is a launch issue.
Use a simple acceptance record. On a small screen, swipe these tables sideways to see every column.
| Step | Reviewer action | Evidence to record |
|---|---|---|
| Open | Visit the exact published URL while signed out | Correct business and page appear |
| Understand | Read the heading and first explanation | Offer and intended audience are clear |
| Check fit | Find the details needed for a decision | Relevant service, product or location information is available |
| Act | Follow the main button or contact route | Destination matches its label |
| Confirm | Finish the permitted test journey | The expected confirmation or opened contact method appears |
Keep credentials, payment information and private customer records out of the review evidence. Use appropriate sample information for tests that need an input, and agree with the receiving team before creating test requests.
Read the page as a customer would
Review content in the order it appears. Can a new visitor tell what the business provides, who it serves and what to do next without opening several unrelated sections?
Check for unfinished text, generic category names, unsupported promises and facts copied from an old version of the business. A polished layout does not repair an incorrect service area, price or contact address. Have the person responsible for those facts approve them.
For images, review the actual subject and its purpose. A project photo should belong to the project it claims to show. A licensed stock image should not be described as a customer or a completed job. Replace a decorative image when it obscures information or makes the offer harder to understand.
If the page includes a testimonial, verify that you have the appropriate permission and that the wording retains its meaning. Do not manufacture a review to fill an empty design block. A shorter page with accurate information is a better release candidate than one padded with invented proof.
Check a phone-sized view and an actual phone when available
Start with the smallest layout you intend to support. Read the full heading, open navigation and reach the primary action. Look for text hidden beneath fixed bars, buttons that overlap, images that cut out the useful subject and content that extends beyond the page edge.
Then inspect a wider view. A page can work at one width while breaking between its mobile and desktop layouts. Resize gradually and check the transition rather than relying only on two screenshots.
A browser viewport preview is helpful, but label it accurately in your release log. It does not establish that the page has been tested on every physical device. If you have a phone available, open the published URL there and repeat the main journey, including any external booking or contact destination.
Record the browser, device or preview width used. That makes a report such as “the heading is cut off” much easier to reproduce and repair.
Try keyboard navigation and readable controls
Use the keyboard to move through the page's interactive controls. Check whether the current position is visible and whether navigation or dialogs leave you stuck. Review the actual button and link labels: a visitor should understand the next action without guessing from a decorative icon.
W3C WAI's Easy Checks covers an initial accessibility review, including keyboard focus, headings, text alternatives and forms. It explicitly warns that passing a few checks does not establish comprehensive accessibility. Use it to begin a review and involve appropriate expertise for a fuller assessment.
For your launch task, write down any point where someone cannot identify a control, read its purpose or continue the journey. Test enlarged text as well as the default appearance. A successful mouse click at the default size does not answer those other questions.
Do not mark accessibility “complete” merely because an automated checker or one reviewer found no obvious issue. Keep the scope and unresolved findings visible.
Test the actions, including the failure path
Follow every prominent action on the released page. Check phone links, email links, navigation anchors, downloads and external destinations where they exist. If a link opens another service, verify the intended public page there rather than stopping at the redirect.
For a form, review labels, required fields and understandable feedback. Use an approved test input to check the expected submission result. Also try a missing required value so you can see whether the page explains what needs attention instead of appearing to do nothing.
The website's confirmation and the receiving team's workflow are separate checks. If the business relies on inquiries, use the website inquiry handoff checklist to verify who receives and owns the request after submission. This launch checklist focuses on the visitor-facing journey; it does not assume that a success message proves a sales follow-up occurred.
Confirm the intended domain and search signals
Open the hostname you intend to share, including its chosen root or www version. Verify that it serves the correct published site over HTTPS. Treat a DNS ownership label, successful publication and a working public page as separate observations; one does not demonstrate all three.
If you are connecting a domain, use the domain connection guide to review the website records while preserving unrelated business email settings. Have the domain owner or authorized administrator make changes in the appropriate account.
Google's canonical URL documentation explains how a preferred URL can be signaled and why conflicting signals should be avoided. Review whether the page's canonical address and sitemap identify the intended published URL. A canonical declaration is a signal, not proof that Google has indexed the page.
Check the page title and description for the business and task they describe. When search visibility matters, keep technical availability, discovery and confirmed indexing as separate entries in the launch record. Do not report “on Google” merely because the website opened successfully in your browser.
Work through a fictional release review
Imagine a small installation business preparing a service page. Its intended journey is: understand the service, check the area covered and request a consultation. The reviewer finds the following fictional issues:
| Finding | Why it affects the task | Repair and recheck |
|---|---|---|
| The phone layout hides part of the main button | The visitor cannot clearly reach the action | Adjust the layout, then repeat the phone journey |
| The service area still names an old location | A visitor may judge fit using the wrong fact | Obtain the owner's current wording and publish the correction |
| The booking link opens an internal management screen | A new visitor reaches the wrong destination | Use the intended public booking page and test signed out |
| A form error says only “failed” | The visitor cannot tell what to correct | Provide useful feedback and test the missing-value case again |
The reviewer records these as findings, not as a judgment that the entire website is unusable. Each issue has a specific owner and a reproducible recheck. Once the corrections are published, the reviewer repeats the affected steps on the public version.
The release is ready for this defined task when the agreed checks pass and any remaining limitations have an explicit decision. That is more concrete than approving the page because it looks finished in a screenshot.
Keep a short release log
Use one row per material finding:
| Field | Example to record |
|---|---|
| Page and version | Published URL and the revision being reviewed |
| Environment | Browser, device or clearly labeled viewport preview |
| Reproduction | Starting state and exact action |
| Expected result | What the visitor should see or complete |
| Observed result | What actually happened, with appropriate evidence |
| Owner | Person responsible for the correction |
| Recheck | Date, reviewer and result after publication |
Keep the log focused. Minor visual preferences can be scheduled separately from a broken primary action, incorrect contact detail or inaccessible navigation. Explain the priority in terms of the visitor's task so the owner knows what must be addressed before sharing the page widely.
After launch, revisit this journey when you change a domain, form destination, external provider or major layout section. A review belongs to a particular version and setup, not to every future change automatically.
Questions
Is a website preview enough before launch?
Use the preview while editing, then repeat the intended task at the real published URL. Public permissions, domain routing and external destinations may differ from the editing environment.
Does this checklist establish full accessibility?
No. It provides an initial practical review. A fuller accessibility evaluation requires a broader scope and appropriate methods and expertise.
Does publishing guarantee that the site appears in Google?
No. Confirming the live page and its technical discovery signals is different from confirming Google's indexing decision. Use dated search-console evidence where you have access.
What should I verify when evaluating Touchbase's website builder?
Check the editing, publishing and domain workflow you actually need, and review current plan eligibility. This checklist is an evaluation method, not a promise that every website builder supports arbitrary applications, integrations or custom code.
The service-business scenario and release-log examples are fictional teaching materials, not customer results.
Prepared with AI assistance and checked against the sources linked in this guide.
Your next step
Get started with Touchbase
Find relevant customers, prepare outreach for review and keep contacts, replies and follow-up connected.
Start for freeStart with a Free account. Upgrade or add credits when you need more capacity. Compare plans