Travel services (non-healthcare) · 2026
A page for every service, and an enquiry button that follows you
Not a clinic. Included honestly, to show the same method applied to a different local business: a page per service, and an enquiry button that follows you down every one of them.
Divyam Tours and Taxi Services · Varanasi, Uttar Pradesh
- Pages, taxi, airport, sightseeing
- One per service
- Pages, taxi, airport, sightseeing
- Found by, not the business name
- Service searches
- Found by, not the business name
- Enquiry, never more than one tap away
- On every page
- Enquiry, never more than one tap away
- Languages, both spoken by the customers
- EN + HI
- Languages, both spoken by the customers
Before the build
A local operator competing with national booking sites
Divyam Tours runs taxis and tour packages in Varanasi, against aggregators with budgets it will never match. It could not win on spend. What it could win on was being the specific answer to a specific search, in a way a national platform never bothers to be, and being reachable in one tap when somebody landed on it.
Why this project is on a healthcare site
Divyam Tours is not a clinic, and we are not going to pretend the work is something it is not. It is here because it is a complete, live example of the same method, and because a practice owner deciding whether to trust us deserves to see everything we have shipped rather than a curated half.
The patterns transfer almost exactly. Where this site has a page for “airport transfer”, a clinic has a page for “root canal treatment”. The discipline is identical. What changes is the care taken with the reader, because a worried patient reads very differently from somebody booking a car.
What we built, and why
A page for every service
Taxi hire, airport transfer, local sightseeing and multi-day tours each have their own page, targeting what people genuinely type, instead of one thin page trying to rank for everything at once. It is the same reasoning behind a page per treatment on a clinic website: one page cannot answer four different questions, and search engines will not pretend it can.
Structured data from the first commit
LocalBusiness JSON-LD ships in the base layout, so every page states plainly what the business is, where it works and how to reach it. On a clinic this is the same groundwork that decides whether a search engine can describe you correctly, including in the summary it now writes above the results.
An enquiry that never disappears
A call-to-action follows the visitor down every page. Somebody ready to book should never have to scroll back up to find out how. On a clinic site that button is WhatsApp, and it matters more, because the person tapping it is often in pain.
Two languages, because the customers have two
English and Hindi, for a customer base that includes both pilgrims and foreign visitors. The same argument as Gujarati on the dental clinic: a language toggle that only translates the menu promises something it does not deliver.
Honest scope
We built and shipped the website. We do not manage this business’s Google listing, we do not run its ads, and we are not going to attribute its bookings to ourselves.
Inside the build
Three decisions, and what they look like
Every screenshot below is the live site. The note beside each one is why it was built that way rather than the obvious way.
The page is named after the search, not the company
Nobody types "Divyam Tours". They type "taxi in Varanasi", so that is the sentence the page leads with. The panel underneath answers the four things a visitor was going to ask anyway — how soon, how far, what vehicle, how to book — before they have to ask any of them. A clinic's treatment page is built exactly this way, with the symptom in place of the route.
Sorted by the question, not by the inventory
The obvious way to build a fleet page is a list of car models. Nobody chooses a car model; they know how many people and how much luggage they have. So the page sorts by that instead, and says plainly that exact models are confirmed on WhatsApp rather than promising a specific vehicle it might not have that day.
The enquiry button follows you down every page
Most visitors arrive on a phone, often mid-trip and on a weak connection. Booking is one tap from anywhere on any page, and it opens WhatsApp with the message already written so the customer only has to send it. This is the same enquiry flow we build for clinics, doing the same job for a different kind of hurry.