Services · Website development · Taxi booking websites
Codeeo provides taxi booking website development Saudi Arabia operators use to present a licensed, multi city transport business online and turn search traffic into booking requests and corporate accounts. One Arabic first platform carries a section for every city you serve, such as Riyadh, Jeddah, the Eastern Province, Makkah and Madinah, with its own routes, airports and contact points, while your brand, compliance details and lead handling stay consistent nationally. Your team edits it, your systems receive the requests and you own every part of it.
This service is the public website and the request and account flows behind it. Rider and driver apps and paid online booking are separate services, and we plan the site so they can join it later without a rebuild. A national site also needs clear ownership, so we agree who approves national pages and who runs each city.
200+ companies servedFrom a first store to an ADX listed developer
Platform capabilities
A taxi company that operates in several Saudi cities faces a problem a single city operator does not: customers search locally, but compliance, brand and corporate sales are national. A Riyadh business traveller, a Dammam resident and a pilgrim arriving in Jeddah each expect a page about their city, their airport and their trip.
Demand also differs by city. Riyadh leans on business travel and airport work, Jeddah on its airport, port and Haramain rail links, the Eastern Province on industrial and commuter traffic across Dammam, Khobar and Dhahran, and Makkah and Madinah on pilgrims who plan from abroad. A single set of generic pages cannot serve all of them.
We solve this with a site architecture of national pages and city hubs. The national layer carries your licence and company details, corporate accounts, careers, privacy and policies. Each city hub carries its own routes, landmarks, contact numbers and seasonal notices, managed by the team that runs that city. The capabilities below describe how that works in practice.
A clean URL structure with a hub per city and route pages beneath it, shared templates so new cities launch quickly, and permissions so each city manager edits only their own section of the CMS. Shared components such as fleet cards and request forms are updated once and change everywhere.
You add a city in a planned release rather than a redesign.
Transport General Authority licence details, commercial registration and VAT number shown consistently, with policies on lost property, complaints and passenger conduct maintained once and displayed in every city section.
Customers and procurement teams see a licensed, accountable operator everywhere they land.
A national application flow for companies, hotels and government related entities, capturing billing entity, cities of use, approvers and expected volumes, routed to the right sales lead by region. Commercial registration details are captured for checks by your team.
Multi city contracts start with complete information and a named owner.
A secure area where approved corporate clients see their booking requests, download invoices issued by your accounting system under ZATCA e-invoicing rules, and update authorised bookers, with optional sign in through your identity provider.
Fewer emails chasing invoices and booker changes.
Booking requests and WhatsApp conversations routed to the right city control room automatically, based on pickup location, with fallbacks when a team is offline and the source page and language recorded each time. Out of hours requests can go to a national desk that covers every city overnight.
No request waits in the wrong city's inbox.
Technical SEO for a large site, structured data for each city's service, consistent Google Business Profiles per branch, and internal linking that lets city pages rank locally while national pages build authority. Branch details on maps match the site exactly, which search engines reward.
Visibility in each city without pages competing against one another.
Right to left Arabic as the primary design, English mirrored from it, and extra languages added by city where pilgrims or expatriate communities make up much of the demand, all managed from one CMS.
Each audience reads the site in its own language without duplicating your work.
A careers section with city filters, eligibility requirements written by your team, and applications that store licences and identity documents in a restricted system, not shared mailboxes. Each city's requirements can differ, and the CMS lets you show the right ones.
Recruitment for new cities starts before the launch date.
Consent managed under the PDPL, with analytics and advertising tags loading only after agreement, and reporting that shows requests and accounts by city, page, language and campaign.
Each city manager sees what is working in their own market.
Connections to your dispatch platform, CRM and accounting system through APIs or webhooks, so website requests and accounts appear where your controllers and finance team already work. Field mapping is agreed and documented before build, so nothing is lost between systems.
The website becomes part of operations, not a separate inbox.
Who this is for
Not every taxi business needs a multi city platform. It makes sense when you run, or plan to run, in more than one city, sell to organisations that use you in several places, or need one brand that customers recognise from the airport in Riyadh to the Corniche in Jeddah. A custom taxi booking website development Saudi Arabia project of this kind usually starts from one of these four positions. Whichever applies, we begin by agreeing which city earns the most today and which one is next, because that order shapes the architecture, the content plan and the first release.
You are strong in one city and adding a second or third. We build the national structure now, launch your home city hub first, and add the new cities as your licences, vehicles and staff are in place. Search authority from your established city helps the new pages, and the site never advertises a city you do not yet serve. We also prepare recruitment pages for each new city ahead of launch.
Cities go live when operations are ready, not before.
Taxis, limousines, staff buses and airport transfers may sit under one group but have different customers. We plan whether these live on one site with clear sections or on separate sites sharing a design system and CMS, based on how customers search and how your sales teams are organised. Shared components keep costs down even when brands look different.
Procurement teams check websites before shortlisting suppliers. They look for licence details, policies, data protection statements, coverage by city and a professional account process. We give them all of it in Arabic and English, with an account application that reaches the right regional sales lead quickly. Case material is never invented; we work only with what you can show.
Procurement readers want evidence, not slogans.
Over the years each branch launched its own site, with different designs, numbers and outdated information. We consolidate them into one national platform, map redirects from every old URL that still earns visits, and align the Google Business Profiles, so you keep search history while ending the inconsistency. Old phone numbers and email addresses are mapped so no customer contact is lost in the move.
How we work together
Part of our team of 80+ is based in Riyadh, so discovery workshops and key reviews can be held in person there. City managers in Jeddah, Dammam, Makkah, Madinah and elsewhere join by video call, and decisions are kept on a shared board everyone can see. As a taxi booking web development company Saudi Arabia operators can hold to a written plan, we fix scope before design starts. Cost depends on the number of cities and languages, the volume of content, the client account area and the integrations with your existing systems. Each phase ends with a review, and timing for the next one is confirmed then.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
Large multi city sites usually run on a headless CMS with a Next.js front end; smaller ones on WordPress. Hosting is set up in your account in a region you choose, with security settings that can follow NCA controls where contracts require it. Should online payment be added later, it runs through SAMA licensed providers, and we plan for registering the online store with the Ministry of Commerce and the disclosures the Saudi e-commerce law expects.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
A great deal: each city adds content, routing and local SEO work.
The national structure, design system and integrations are built once. Each additional city then needs its own hub, route pages, contact routing, Google Business Profile alignment and, often, extra languages. That is why we usually launch one or two cities first and add the rest in planned releases. You see results from the first city before committing to the full rollout, and later cities move faster because the templates already exist. We give you a city by city plan so the budget follows the business case.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
React
Next.js
TypeScript
Node.js
Laravel
WordPress
Shopify Plus
WooCommerce
BigCommerce
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio