Taxi operators · Website
A taxi website is a booking page with a number, a route list and a fare method.
A website for a taxi operator is a small set of pages that show your cars, your routes and how to book. GullySales works on the pages a rider needs and removes the rest, so the visitor reaches the booking line without hunting.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What website means
A website is the page a customer lands on after searching, clicking an advert or scanning a code, and it decides whether they call or leave. GullySales builds and maintains sites that load quickly, explain the offer plainly and make the enquiry form or phone number easy to find.
Last updated 14 Nov 2026.
For taxi operators
Where it usually goes wrong, and what we would do.
“Visitors arrive on a phone”
A rider is standing somewhere, thumb on a screen. A page that needs zooming or hides the number below the fold loses them to the next operator.
“The call button matters more than the design”
A visitor who is ready to book wants to tap a number or a chat link. Every page should carry one, in the same place, and the page should open without a delay.
“A list of cars with no detail does not help”
A rider choosing a vehicle wants seats, luggage space and air conditioning stated. Describing each vehicle in those terms answers the question before the call.
“Trust comes from visible facts”
A real address for the stand, real pictures of the cars, the permit details you are comfortable showing and a fare method. A site that shows no names or places reads as a lead-gathering page, not an operator.
What we do
What we deliver for taxi operators.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A small site map built around bookings
Home, routes, cars, fare method, about and contact, each with a clear job.
Result: A site with few pages and each one has a purpose.
Phone-first layout
Pages built for a small screen, with a tap-to-call button and a chat link visible without scrolling.
Result: A rider on a phone can book in one tap.
Route and car pages
One page per main route and per vehicle type, with the facts a rider checks.
Result: A rider finds the route and the car on separate pages.
A fare method page
A plain statement of how the fare is worked out, linked from every route page.
Result: The same explanation is shown everywhere.
A simple booking form
A short form asking for pickup, drop, date and passengers, sent to the dispatcher's phone.
Result: Enquiries arrive in a form the desk can act on.
Basic tracking set up
Calls, chat taps and form submissions counted, so you can see what the site brings.
Result: You can tell whether the site produced a booking.
How the result is measured
- Page load time
- Bounce rate
- Enquiries from the website
Recorded as a baseline before work starts, so every later report has an honest comparison.
Searches your buyers type
What a rider wants to find on a taxi website, and the page that answers each question.
- What does an outstation trip cost
- A fare method page that explains the basis of the fare, the toll, the night halt and the waiting rule, with a quote form.
- Which cars do you have
- A car page for each type, with seats, luggage room and a real photograph of the car, not a stock picture.
- Can I book on WhatsApp
- A click-to-chat button on every page, opening a message with the route and date typed in, so the dispatcher starts with the details.
- Where is the stand
- A stand page with a map pin, a landmark photograph and the hours the number is answered.
- Is the driver reliable
- A short page on how drivers are chosen and what the office does if a rider complains, in plain facts you can keep.
Who it is for
This is written for these taxi operators.
- Stand-based taxi operators at railway stations and bus stands
- Radio and call-centre taxi fleets in a city
- Small owner-operators with two to ten cabs
- Outstation-focused taxi operators
- Taxi associations and cooperatives
- Operators who also supply cabs to apps and corporates
- Auto and cab mixed fleet operators in smaller towns
- Women-only or senior-citizen-focused cab services
Before you decide
When this may not be the right fit.
- You change fares by the day, so a fare page would be wrong at the time a rider reads it.
- Riders reach you only by walking to the stand, so a site with a call button would add nothing to how they find you.
Before you decide
Agree the work. Know how to judge it.
Website for taxi operators: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the pages that support a buying decision and the actions visitors must complete. Keep examples of failed forms, unclear product information, and questions your team answers repeatedly.
Make the scope clear
Agree the page list, content ownership, integrations, and who controls the domain and hosting. Include redirects and existing search traffic in a redesign brief, before changing addresses.
Check the work in use
Complete a real enquiry journey on a phone and a laptop. Check that the confirmation appears, the enquiry reaches the right person, and tracking records the action once.
Know when to change course
If visitors can enquire but the team does not follow up, start with the sales handover. A larger website will not resolve that delay.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from taxi operators. Anything missing is noted in the written scope, with who will supply it.
- The domain and hosting login
- Who owns the domain name and where it points. We need it to go live. If a relative or old developer holds it, settle it first, because the site cannot launch without it.
- Car photographs and registration plates
- Clear pictures of each car type, with the plates hidden if you prefer. The car pages depend on them. Missing pictures mean text-only pages, which riders trust less. Name the driver or dispatcher who can take new pictures when a car is replaced, so the pages do not keep showing a vehicle that has left the fleet.
- Licence, permit and insurance facts
- The permits you hold and the details you are willing to show. They make the trust section real. We show only what you confirm, and nothing is added from assumption.
- The fare basis you will state
- Whether to publish a rate or a method. Only the owner can decide. If undecided, the site tells the rider to call or message for a quote. If a published rate would need updating each season, say so now, and we write the method page in a way that does not go stale when the rate changes.
- A person to receive form enquiries
- Someone who reads the booking form and replies as the dispatcher would. Without a named person, form enquiries sit unread and the form should be left out.
How it works
How the website work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Look at the site on the dispatcher's phone
We open your current site, or the lack of one, on the phone a rider would use and tap the number. You tell us what you want a visitor to do first. What exists afterwards is a list of what works, what does not, and the single action the new site must make easy.
- 2
Agree the pages from the bookings you take
From your trip book we pick the handful of pages that match real bookings: the local ride, the routes, the cars, the fare method, the contact. You decide what stays out. The result is a short page list, and a note of what we deliberately did not build. We also check the trip book for the questions that decide a booking, such as whether the car has a luggage carrier, and place those answers on the page where the rider needs them.
- 3
Gather cars, routes and facts in one place
You hand over car photographs, route details, the fare basis, licence and permit facts and a line about the drivers. Gaps are listed with the person who will fill each. Nothing is invented, so each page rests on facts the owner confirmed.
- 4
Review a test version on your own phone
We publish the pages on a private address and you open them on your phone. You tap the call button, the WhatsApp link and the form, and send a test enquiry. We fix what you find. The site goes public only after the dispatcher has received that test. We also try the page with the data connection switched to the slowest your riders use, because a site that loads slowly at a station loses the visitor before the number is seen.
- 5
Take the site live and move the number
We point the domain, check the pages again from a different phone and a different network, and update the number on the Maps listing and social pages to match. You approve the switch. The old page, if any, is redirected so earlier links still land somewhere useful.
- 6
Read the call counts against the first note
At the start we noted how many calls and forms came from the old site, if any. After the new site has been up for a while, we read tracked calls, form entries and booking mentions against that note. You decide on changes. No traffic is promised; the figures show what the site delivered.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Is a Maps listing enough, or does a cab business need a site too?
Can we take payments on the site?
Does a Maps listing make a taxi website unnecessary?
Can we take payments on the site?
Should riders be able to pay on the site?
Who updates the site when a rate or a car changes?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for taxi operators
Related work to consider.
Closest to this: search and visibility
Also for taxi operators
Or start from the overview: sales and marketing for taxi operators.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.