Services · Website development · Healthcare websites

Healthcare websites that work across Saudi regions and Saudi rules.

Codeeo delivers healthcare website development in Saudi Arabia for hospital groups, polyclinic networks, specialist centres, laboratory chains, pharmacy groups and home care operators with branches in more than one city. We build one Arabic first website platform that presents every region, branch, specialty and doctor accurately, follows national rules on health advertising and personal data, and routes each enquiry to the team that serves that patient, wherever they are in the Kingdom.

National providers face a particular problem: each region wants its own voice, while head office needs one brand, one set of rules and one way of measuring results. The platform we build gives regional teams controlled editing rights inside a structure that head office owns and governs.

Built for
Hospital groups, clinic networks, laboratory and pharmacy chains, and home care providers operating in several Saudi regions.
Typical timeline
Agreed after discovery maps every region, brand, specialty and integration; most national builds launch in phases, with each phase dated in the written plan.
What you own
The domains, hosting, CMS, design system, content and analytics properties, registered to your group and controlled by your IT team.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

Platform capabilities

What a multi-region healthcare website needs to do.

Saudi healthcare is split between public facilities, now organised into health clusters under Health Holding, and a private sector of groups that often span Riyadh, Jeddah, the Eastern Province and smaller cities such as Madinah, Abha or Qassim. A private group's website sits in the middle of that system. It has to explain services to patients and insurers, show practitioners within the limits set by the Ministry of Health, protect personal data under the Personal Data Protection Law, and work in Arabic first with complete English.

Healthcare website design in Saudi Arabia at this scale is mostly about governance. Who can edit what, who approves clinical content, how a new branch is added, and how regional teams stay inside the brand. The capabilities below are the parts we build so a national site remains accurate as it grows, rather than slowly filling with outdated pages and contradictory information. Each one is configured once at group level and inherited by every region, which keeps the cost of adding a new city low.

Explain your project
  • Region, city and branch architecture

    A clear hierarchy from region to city to branch, with specialty pages that show every location offering a service. URLs, navigation and structured data follow the same pattern everywhere, so search engines understand the network and patients in any city reach their nearest branch in a few taps. Smaller cities get proper pages too, not a single line on a contact list.

    A national structure that scales without redesign.

  • Governed multi-team CMS

    Regional editors manage their branches, doctors and local news. Head office controls templates, brand elements and national pages. A medical review role approves anything clinical before publication, and every change is logged with user and time so audits are straightforward. Permissions can be changed by your administrators as staff join or leave.

    Local teams move quickly within central rules.

  • National doctor directory

    One directory for every practitioner in the group, searchable by specialty, city, branch, language and gender. Profiles are descriptive, with optional Saudi Commission for Health Specialties registration details, because the rules restrict practitioners from promoting themselves outside approved channels.

    Patients find the right doctor anywhere in the network.

  • Insurance network information

    A central list of insurers and plans you accept, with exceptions by branch or service, maintained by your contracts team. Patients check cover before they book, and the list stays consistent because it is stored once and shown wherever it is needed.

    One source of truth for insurance questions.

  • Enquiry routing by region

    Appointment requests, callback forms, calls and WhatsApp messages route to the call centre or branch that serves the patient's city and specialty. Corporate enquiries from employers go to the business team for that region, with the company's locations captured. Each route is tagged, so head office can see demand by region and service.

    No enquiry lands in the wrong queue.

  • Compliance-aware content model

    Templates for service pages, treatment information and health awareness articles are designed around factual content, review dates and named clinical reviewers. They leave no space for testimonials or outcome claims, which the Ministry of Health has acted against in health advertising. Review dates prompt clinicians to recheck articles before they go stale.

    Content stays within advertising rules by default.

  • Accreditation and quality pages

    Pages that state accreditation status, such as CBAHI accreditation by facility where you hold it, patient rights and responsibilities, complaints procedures and visiting rules. Your quality team owns these pages, and dates show when each was last reviewed. Insurers and corporate clients checking your standards find the same information patients see.

    Clear, current quality information for patients and payers.

  • Data protection and security baseline

    Forms collect only what is needed, consent follows the Personal Data Protection Law overseen by SDAIA, and health details never pass to advertising tools. Hosting, access control, logging and patching follow the National Cybersecurity Authority Essential Cybersecurity Controls as a reference, agreed with your IT and security teams.

    A public site that passes your security review.

  • National and local search

    Group-level pages compete for national searches, while branch pages and business profiles target each city. Hreflang, structured data for organisations, branches and physicians, and Core Web Vitals work are planned for the whole platform, not page by page.

    Visibility nationally and in every city you serve.

  • Analytics and consent

    A consent banner in Arabic and English, analytics configured to respect it, and dashboards that show enquiries by region, branch, specialty and channel. Leadership sees which parts of the network the website supports well and where content needs work. Reports can be shared with regional managers so each team sees its own results.

    Decisions based on regional enquiry data.

Who this is for

Four national healthcare situations we plan for.

National healthcare websites tend to fail in predictable ways: separate regional sites that drift apart, a single site nobody outside head office can update, or a directory that falls out of date within months. These are the starting points we see most often, and how the platform addresses each. Larger groups often face two or three of them at once, and the rollout plan sequences the work accordingly.

01

Groups consolidating several regional sites

Acquisitions and growth often leave a group with separate websites for Riyadh, Jeddah and the Eastern Province, each with its own design and CMS. We merge them into one platform, keep the pages that earn search traffic, redirect every old URL and give each region its own editing space under a shared brand. Doctor and branch data from the old sites is cleaned and checked with regional managers before import, so the new platform does not inherit old errors.

One platform, many regional editors.

02

Networks expanding into new cities

When you open in Madinah, Abha or Tabuk, the website should be ready before the doors open. Our branch and city templates let your team publish a new location with hours, doctors, services, insurers and a local search profile, without commissioning new development each time. Pre-launch pages can announce an opening date and collect interest, then switch to a full branch page when the facility is licensed and ready.

03

Laboratory, pharmacy and home care chains

These operators have many small locations or service areas rather than a few large hospitals. The website needs a fast locator, service area coverage, test or service directories and request forms that reach the right local team. We design for volume and quick updates rather than lengthy content. Locations can be imported in bulk from a spreadsheet or your operations system, so hundreds of sites stay accurate without manual editing.

04

Groups adding paid services online later

Some groups plan to sell health check packages or home visits online. We keep the information website separate in purpose but ready to connect to a payment and booking build, which brings mada, Apple Pay, STC Bank (formerly STC Pay), ZATCA e-invoicing through Fatoora and registering the online store with the Ministry of Commerce into scope. Planning that separation early prevents the information site from being rebuilt when online sales begin.

How a national healthcare website is planned and rolled out.

  1. 01Group discoveryWorkshops with head office in Riyadh in person, or by video call elsewhere, mapping regions, brands, specialties, systems, approval rules and the people who will edit the site.
  2. 02Governance and architectureA sitemap from region to branch, a permissions model for central and regional teams, and a content model that builds advertising and privacy rules into every template.
  3. 03Design systemReusable Arabic and English components, tested for accessibility and speed, so every region's pages look and behave the same while carrying local content.
  4. 04Platform buildCMS, directories, locators, routing, analytics and integrations with CRM and call centre systems, built once and configured for each region.
  5. 05Pilot regionThe first region launches, its editors are trained and real enquiry data is reviewed, so the setup is corrected before other regions follow.
  6. 06National rolloutRemaining regions move across in planned waves, with redirects from legacy sites, search monitoring and support for regional editors throughout.

Technology

What we build this with.

For multi-region groups we typically use a headless CMS with Next.js, or WordPress multisite where the team prefers it. Hosting location, backup and access policies are agreed with your IT and security leads, and integrations with CRM, call centre and hospital systems use only interfaces they support safely. Patient records and results stay in your clinical systems and portals, never in the public website.

01Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

02Commerce

  • Shopify Plus
  • WooCommerce
  • BigCommerce
  • Headless storefronts

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

04Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Questions national healthcare groups ask.

Health advertising, personal data and cybersecurity rules.

The Ministry of Health regulates how health services are advertised and restricts practitioners from promoting themselves outside approved channels. The Personal Data Protection Law, overseen by SDAIA, covers what you collect through forms and analytics, with health data treated as sensitive. National Cybersecurity Authority controls are a sensible baseline for hosting and access. Your legal and compliance teams interpret these for your facilities; we build the website so following them is the default, with privacy notices, consent records and approval history ready for review.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews