A website template can look finished while still containing sample content and demonstration links. Before customizing it, separate what the design shows from what a real visitor will need to do.
This walkthrough uses the public Revamp med spa website template as a worked example. Its demo brand is FORMA. This is a review of the public example, not a report about a real clinic or a completed customer launch.
1. Map the page before judging the design
The example has a hero introduction, an approach section, a treatment menu, a skin-care philosophy section, first-visit information, and footer navigation.
That sequence gives a reviewer something concrete to evaluate: can someone understand the offer, explore the relevant service, and find a next step?
For another business, write the same sequence in ordinary language. A restaurant might need a menu, location, opening hours, and a reservation route. A consultant might need services, evidence, and an enquiry route. Decide what the visitor needs before adding more sections.
2. Inspect the destination behind the action
In the FORMA preview, the main navigation links point to sections on the same page. The hero's starting-point link points to the treatment section, and several consultation links point to the first-visit section.
Those are navigation steps. They do not establish that an appointment has been requested or confirmed.
The final contact link in this public demo uses an illustrative email address, hello@example.com. That is sample content to replace before a real launch. A visual review should catch it before a visitor does.
For each important link, record three things:
- The label the visitor sees.
- The destination it opens.
- The business outcome that should happen afterward.
For example, 'Request a consultation' could open an enquiry form, an email draft, or a scheduling service. Choose the behavior deliberately and make the label match it.
3. Keep design and business setup as separate decisions
The template's catalog page describes appointment tools as possible additions. That wording should not be treated as evidence that a booking account is already connected.
When reviewing any starter design, keep a short list of what is visible, what is sample content, and what needs configuration. This prevents a useful design from being mistaken for a completed business workflow.
Replace the demo business name, service descriptions, imagery, contact details, and any other sample information with content the real business has approved. For a regulated business, the relevant professional should review its public claims.
4. Write acceptance checks for the finished website
These are proposed checks for a customized website, not claims that this demo has passed them:
| Area | Check before launch |
|---|---|
| Navigation | Open every important destination directly and through the page's links |
| Contact | Send a clearly identified test enquiry and confirm it arrives at the intended destination |
| Scheduling | If scheduling is added, check the available service, time, and confirmation |
| Mobile | Review the menu, long text, buttons, and forms on a narrow screen |
| Keyboard | Reach the important links and controls without a pointer |
| Content | Search for sample names, contact details, and descriptions that still need replacement |
If a check fails, describe the observed behavior and the expected result. 'The contact link opens the sample email address; replace it with the approved enquiry route' is more actionable than 'make the site work.'
What this review establishes
A public preview can show the design, section structure, and link destinations. It cannot establish the results of a customer's launch, the reliability of an untested integration, or whether a website will attract enquiries.
Review the example, customize it for the actual business, then test the completed visitor journey on the published site.
Disclosure: This educational walkthrough was prepared with AI assistance and input from Revamp. It is not an independent customer testimonial. Observations concern the public demo; the launch checklist describes checks to perform, not completed tests.
