Promise match
Ad copy and the first screen of the page carry the same phrasing.
Medical-tourism agency service
A landing page is a standalone page that carries one visitor towards one decision. What separates it from a corporate site is the absence of a menu, of multiple purposes and of free navigation. In medical tourism its success depends less on design than on the order in which information appears.
In most campaigns that spend without returning, the failure is not in the campaign. It begins one second after the click: the visitor cannot see the promised thing on the first screen and leaves.
We therefore treat landing page work as decision architecture rather than design.

They do different jobs and cannot substitute for each other. A corporate site explains the institution and answers many questions; a landing page answers one question and asks for one action.
Sending paid traffic to a corporate homepage is the most common form of wasted budget we see. The visitor cannot find the treatment they clicked on, so they leave.
| Criterion | Corporate site | Landing page |
|---|---|---|
| Purpose | Explaining the whole institution | One decision for one treatment or market |
| Navigation | Full menu and cross-links | No menu; a single action path |
| Content breadth | All services and all languages | Only what the advertisement promised |
| Success measure | Brand visibility and organic reach | Qualified enquiry rate |
| Lifespan | Continuous, under a maintenance plan | For the campaign; retired when it ends |
| Language | Every language the institution supports | Only the campaign’s language |
A treatment-seeker first asks whether this applies to them, then who performs it, and only then how to begin. When that order breaks, attention breaks with it.
So we build the page from those three questions rather than from an aesthetic. Visual language is a tool that supports the sequence; it is not the sequence.
Landing page decision order
A landing page form is not a pre-registration form. Its purpose is to start a conversation, not to profile a person.
Health status, diagnosis, treatment history and image-upload fields do not belong here. These are special-category personal data and should not be collected through a publicly accessible form.
Ad copy and the first screen of the page carry the same phrasing.
Suitability, trust and process appear in the order patients ask for them.
The page opens on low bandwidth; RTL and screen readers are supported.
Working sequence
The promise the page must honour is drawn from the campaign copy.
Suitability, trust, process and action blocks are written in sequence.
Authorisation, physician detail and facility images are verified and placed.
Field count is set from response capacity and connected to the CRM.
Checked against a performance budget and WCAG contrast thresholds.
Frequently asked questions
Not one per campaign, but one per promise. Two campaigns making the same promise can share a page; a different treatment or a different market needs its own.
No. It belongs on the institution’s own domain. A separate domain weakens the trust signal and makes authorisation harder for a visitor to verify.
Yes. Text and image areas are handed over in an editable form. Structural changes come back to us.
Publishing a fixed price carries regulatory risk. We publish scope instead: what is included, what is not, and what changes the price.
The page is retired and redirected to the relevant service page. Abandoned landing pages left live compete with corporate pages in search and weaken both.
Video explaining the institution and the process helps at decision stage. But autoplaying video that slows the page works against you on low bandwidth. We use a poster image and click-to-play.
The design stays; the direction changes. Right-to-left text, form alignment and icon orientation are checked separately. We treat this as design work, not translation work.