Hospital Website Design: Website Design for Hospitals and Health Systems, From Find a Doctor to the Redesign

Updated October 2026 · Written and maintained by the Progression Agency strategy team

Website design for hospitals is the work of turning one of the largest sites in a region into something a worried patient can use in under a minute: find a doctor, find the right campus, book or call, and understand the bill. A hospital site is a provider directory, a front door to scheduling and the portal, and a library of service line content, all run by several departments at once. This page covers the structure, directory, booking handoffs, accessibility, governance and redesign. We design and build hospital and health system websites across the US, working remotely from New York.

What is website design for hospitals?

Website design for hospitals is the planning, layout, content structure and build of a hospital or health system site around the people who use it: patients, families, referring clinicians, job seekers and staff. Hospital website design differs from practice work in scale. There are more pages, more owners and more systems behind the screen, so the first decisions are about structure, not color. Anyone typing website design for hospital work into a search box is usually trying to answer one question: how do we keep a site this large usable?

A directory, a front door and a library

A hospital site does three jobs at once. It is a directory of doctors, locations and departments. It is a front door to scheduling, the portal, bill pay and the careers system. And it is a library of service line, condition and treatment pages. Each job has a different owner and a different data source, which is why one designer working alone from a mood board rarely gets a hospital site right.

Hospital sites versus clinic and practice sites

A clinic site has a handful of pages and one address. A hospital site has campuses, departments, affiliated practices and hundreds of clinician profiles, plus legal notices that a practice never needs. For a smaller practice or a single specialty office, our healthcare website design page is the better starting point. This page is for organizations where the sitemap alone needs a committee.

Who runs the site inside a hospital

Marketing usually owns the brand and the service line pages. IT owns hosting, single sign-on and the feeds. Compliance and the privacy officer review forms and tracking. The access center owns scheduling and the phone numbers. The medical staff office owns credentialing data that fills the directory. Naming these five owners in week one prevents most of the arguments that stall a launch.

How do you build a hospital website?

You build it in stages, starting with what patients need to do and finishing with a verified launch. How to build a hospital website comes down to this order of work, which is the same nine stages we publish for every build on our fixed-scope website pricing page. Hospital web development, or hospital website development as buyers often say it, adds feeds from the directory, scheduling and careers systems on top of that sequence. If you are weighing how to design a hospital website from scratch, begin with the order of work below.

1. Discovery: services, systems, owners and what the site must accomplish
2. Architecture: a sitemap built from patient tasks
3. Content plan: who writes, who reviews and by when
4. Design: a set of templates rather than a pile of pages
5. Build: the CMS, the feeds and structured data per template
6. Content production: copy, photography and review sign-off
7. QA: accessibility, speed, forms and structured data
8. Redirect mapping: every old URL assigned a new one before development starts
9. Launch and verification: sitemap, crawl, forms and top URLs checked the same hour

Start from the tasks patients come to do

List the top tasks first, then arrange the site to serve them. Ask the access center, the front desk and the billing office what people call about. Those calls are a better map than the org chart. We do not quote traffic or conversion statistics here because the useful numbers are your own, taken from your analytics and call logs.

Inventory the content and the systems

Before any design, list every system the site touches: the CMS, the provider directory, scheduling, the patient portal, the applicant tracking system and the price estimator. For each, write down who owns it, whether it has an API or an embed, and who approves changes. The inventory tells you which pages can be built once and filled automatically.

Architecture before templates

A hospital sitemap is argued over in the wrong order when design comes first. Settle the hierarchy, the URL pattern and the navigation rules, then design templates that fit them. Our published standard asks for one page per intent and no commercial page more than three clicks from the homepage; a hospital needs the same discipline across every campus.

Hospital web design for service lines, campuses and affiliated practices

Hospital web design has to show the organization the way patients think about it, by condition and by place, even when the organization is arranged by department and legal entity. The structure below keeps all three views consistent.

Service line hubs

Each service line, such as cardiology or orthopedics, gets a hub that links to its conditions, treatments, doctors and locations. Condition and treatment pages sit underneath. The hospital’s clinicians review the clinical content; we handle the structure and the layout. A hub works when a patient can reach a doctor or a booking step in two clicks.

Campus, department and location templates

Treat a campus page as a set of fields: name, address, entrances, parking, hours, departments housed there, accessibility features and a phone number that connects to the right desk. The reasoning behind location and provider pages, including how search and assistants read them, is covered under the heading Location and provider pages that patients and assistants can read.

Affiliated practices and joint ventures

Community practices, outpatient joint ventures and affiliated physician practices confuse navigation when they appear in the same menu as hospital departments. Decide whether they live under a clearly labeled section, share the hospital domain with a sub-path, or link out. Whatever the rule, apply it to the URL pattern as well, so the structure holds when a new affiliate joins.

URLs that survive a reorganization

Hospitals reorganize service lines more often than they rename them. Use stable, descriptive URL slugs that name the service or the place, not the department’s reporting line, and keep clinician profile URLs independent of the department. When the structure changes, the page can move in the menu without its address changing.

Find a doctor: building the provider directory

The directory is the most used and most fragile part of a hospital site. A good one answers three questions fast: is there a doctor who treats this, can I get an appointment, and is the doctor near me?

Directory data from credentialing and scheduling systems

Profiles should come from a single record that the medical staff office and the scheduling system both trust. Hand-typed profiles drift out of date within weeks. The site pulls name, specialty, locations, languages and availability from the source, and editorial fields, such as a bio or a photo, are layered on top with an owner and a review date.

Search and filters patients use

Offer search by specialty, condition, location, language, accepting new patients and insurance, in that order, which suits many visitors. Let the person search by a symptom-adjacent term, such as knee pain, and return the right specialties. Keep the filter panel usable on a phone, and make sure every result is a link a screen reader can follow.

Profile templates that load fast at scale

One template serves hundreds of profiles, so one slow component repeats everywhere. Cache the listing, size photos to what is displayed and keep scripts off the template unless they earn their place. On markup, the type pages for Physician and MedicalOrganization on schema.org show the properties available, and Google’s search gallery lists the rich results it supports, which does not include one for a physician.

When the directory is a vendor product

Many hospitals license a directory from a vendor. It can arrive as an embed or as an API. An embed is quick but hard to style and test for accessibility. An API lets the site render profiles itself. We name no vendor here, and the choice is yours; what matters is that the embed passes the same keyboard and screen reader tests as the rest of the site.

Hospital appointment booking and patient portal handoffs

A hospital appointment booking website rarely does the booking itself. It hands the patient to a scheduling tool or a request form, and to a portal for everything after that. The design job is to make each handoff obvious and safe.

Online scheduling handoffs

Open scheduling lets a patient pick a slot. A request form lets the patient ask and wait for a call. Both work if the page says which one it is and when to expect an answer. The handoff is also where analytics must stop: HHS has said that tracking on pages where people book appointments may collect protected health information, so count clicks on the button yourself and send nothing from inside the booking flow.

Portal sign-in and proxy access links

A hospital website patient portal link is only a link. The portal is the EHR vendor’s product, built and secured separately, so the website provides a clearly labeled sign-in link, a proxy access explainer and a help number. If you need the portal itself built or extended, see our work in EHR software development and web portal development.

Request forms that ask for no clinical detail

Keep first-contact forms to name, phone, preferred time and the service wanted. Do not ask for symptoms, diagnoses or medications in a web form. Say on the page what happens after submission, who will call and by when. A short form completes more often, and it keeps clinical information in the systems built to protect it.

Emergency, urgent care and wait-time pages

These pages are read in a hurry, often by someone frightened. They should carry facts, not marketing, and they should never offer medical advice. For an emergency, the only instruction is the one the hospital already gives: call 911.

What the emergency page must show at once

Put the address, the entrance a visitor should use, parking and the line telling people to call 911 in an emergency at the top of the page, in plain text and in large type. Directions should work in a maps app on a phone. Nothing else, including a banner, a pop-up or a chat widget, should sit between the visitor and those facts.

Routing between urgent care and the emergency department

Describe the two services in plain terms: what each is for, its hours and where it is. Do not tell readers which one they need for a given symptom; that is a clinical judgment. A short description with a phone number for questions is the safest design. Search for urgent care locations is its own subject, covered by urgent care SEO.

Wait times only when the data is live

A wait time that is hours old is worse than none. Show wait times only when a live feed supplies them, label the time of the last update, and add a sentence saying the figure is an estimate that can change. If the hospital cannot feed the number reliably, leave the feature off and use the space for directions.

What are hospital website best practices?

Hospital website best practices are the habits that make a large site easy for ordinary people: plain language, fast pages on a phone, access in more than one language and a search box that understands how patients talk.

A patient-centered hospital website starts with plain language

The CDC’s Clear Communication Index is a research-based tool to plan and assess public communication, with 20 scored items, and plainlanguage.gov publishes guidelines for writing readers can understand the first time. Use them on service pages, instructions and billing pages. Write short sentences, lead with what the reader should do, and replace internal department names with the words patients use.

Mobile speed on large templates

Google’s Core Web Vitals describe a good experience as a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of visits. Our builds carry numeric performance targets on a throttled mobile connection, and hospital templates that repeat hundreds of times deserve them most.

Language access and translated pages

Under Section 1557, 45 CFR 92.11 requires a covered health program to post a notice of language assistance at a conspicuous location on its website, in English and at least the 15 languages most commonly spoken by people with limited English proficiency in the relevant state or states, as the rule reads today. Beyond the notice, translate the pages patients use most, such as locations, booking and billing help. Our multilingual website design page covers how to build translated paths natively.

Site search that knows medical synonyms

Patients search for heart doctor, not cardiologist, and for a bad back, not lumbar radiculopathy. Maintain a synonym list so site search returns the specialty, the condition page and the doctors together. Review the search log each quarter: failed searches show where the site and patients’ words do not match.

Accessibility for hospital websites: what to test

Accessibility for hospital websites is both a legal requirement and a daily need: patients with low vision, limited mobility, hearing loss or cognitive differences use these sites to get care. Test it as a system, not as a final checkbox.

Which rules reach a hospital site

HHS’s Section 504 rule, now at 45 CFR 84.84, sets WCAG 2.1 Level AA for the web content and apps of recipients of HHS funds, with a compliance date of May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller ones. Hospitals run by state or local governments are also covered by the ADA Title II web rule, which for entities serving 50,000 people or more starts April 26, 2027. The compliance dates and their history are set out under Accessibility deadlines for hospital websites.

Testing past automated scans

Automated scanners catch only part of the problems. We build to WCAG 2.2 Level AA, which the W3C says builds on and is backwards compatible with 2.1, so building to the newer standard is the practical choice when the HHS rule cites the older one. Every form is submitted from a real phone before launch, and the table below lists the other checks a hospital should expect from any builder.

PDFs, videos and third-party widgets

Hospitals publish a great deal of PDF material: forms, policies, maps and handouts. Each needs real text, headings and tags, or should become a web page. Videos need captions and transcripts, and any third-party widget, such as chat, a map or an embedded directory, needs to be tested on its own. Our ADA compliant website design page explains the build approach.

Price transparency, billing and financial assistance pages

Money questions follow patients through every visit to a hospital site. Design the billing pages so a person can reach an estimate, a way to get help and a human being without reading a policy.

Where the price transparency link and estimator sit

Put the price transparency link in the footer of every page and place the estimator next to the booking step, where the question arises. What the federal rule requires is explained under Price transparency pages patients can use.

Financial assistance policy on the website

The IRS says a nonprofit hospital facility must widely publicize its financial assistance policy, and that putting the policy, the application form and a plain language summary on a website is one required step. The Section 501(r)(4) guidance adds that the website needs a conspicuous link to the page and that anyone should be able to download the documents without an account or personal information. Build a dedicated page, link it from billing, bill pay and the footer, and keep the documents current.

Billing help patients can find

A billing page should answer four things in order: how to pay, how to get an estimate, how to ask for help with the cost, and who to call. Put the phone number and hours in text, not only in a PDF. If the hospital uses a separate bill pay site, say so on the page and explain why the address changes.

HIPAA-aware forms, chat and tracking on hospital sites

Forms, chat widgets and tracking scripts are the places where a hospital site can send protected health information to a third party by accident. Design them with the privacy officer in the room, not after launch.

What a pixel on a hospital page can expose

HHS’s bulletin on online tracking technologies says tracking on user-authenticated pages generally has access to PHI, and a federal court vacated part of the guidance in 2024 in American Hospital Association v. Becerra. The details, and how we build measurement around them, are under HIPAA, tracking pixels and the AHA v. Becerra ruling.

Forms, chat and video vendors

When a vendor handles PHI for a covered entity as its business associate, the covered entity needs a contract that meets 45 CFR 164.504(e). Ask every form, chat and video vendor whether it will sign one before it goes on a page that could carry PHI. Where our work involves PHI on a covered entity’s behalf, we sign a business associate agreement; our HIPAA compliant software development page covers that work.

Analytics that stops at the booking handoff

Count what happens on public pages: visits, clicks on the call button, clicks on the scheduling link, form starts on pages that ask for no clinical detail. Stop at the handoff. We set up analytics and conversion tracking in every tier, and for a hospital the tracking plan should be written with the privacy team before a single tag is added.

Content governance and the hospital CMS

Hospital website management is mostly about people. A site with hundreds of editors and no rules fills with stale phone numbers and unreviewed medical text. Governance decides who can change what, and the CMS enforces it.

Roles: who drafts, who reviews, who publishes

Separate three roles. Drafters, such as department coordinators, write or update. Reviewers, such as clinicians and compliance, approve. Publishers, a small trained team, release changes. Nobody holds all three for clinical pages. Roles should map to CMS permissions, so the system prevents a skipped review rather than relying on memory.

Clinical review and review dates on each page

Every condition, treatment and service page should name who reviewed it and when, and carry a next review date that the CMS tracks. Hospital website content that no one has reviewed in years is a risk to patients as well as to search visibility. Show the review date to readers, and use it internally to build the audit queue.

Choosing a CMS for a health system

We build on WordPress and on headless setups, never on a platform you cannot take with you. WordPress suits most hospital marketing sites that need editors, workflows and plugins; our WordPress development page describes that work. A headless build fits sites with many feeds and demanding speed targets, as explained under headless WordPress.

Audits and pruning

Run a hospital website audit twice a year. List every page with its owner, last review date, traffic and links in. Merge duplicates, redirect retired services and delete pages no one owns. Fewer, better pages are easier to keep accurate, and they are easier for patients to scan.

Hospital website redesign without losing search traffic

A hospital website redesign puts years of search visibility at risk, because the site holds thousands of URLs that earn visits quietly: doctor profiles, location pages and condition articles. Protect them first and redesign second.

A redirect map before development starts

Every indexed URL gets a specific new destination, mapped before development begins. Producing the map early forces the team to see which pages earn traffic before anyone proposes deleting them. Google’s guidance on site moves with URL changes says permanent redirects do not cause a loss of PageRank, which is why this work pays off.

Directory and location URLs at migration

Directory and location pages are where hospital migrations usually break, because profile URLs often contain an internal ID that changes with the new system. Decide the new pattern early, map each profile to it and test samples across every campus on staging. For the wider process see website migration.

How long does a hospital website redesign usually run?

The scope sets the schedule, and no one can honestly promise a date before discovery. Our published tier timelines on the fixed-scope page, such as 8 to 13 weeks for a business site, apply to sites in those tiers only. A hospital build with feeds, campuses and review cycles is scoped separately. Traffic drops after a redesign are the risk to plan for; see traffic drops after a redesign.

Health system website design across several hospitals

Health system website design adds one question to everything above: which parts are shared and which belong to each hospital? Settle it early, because it drives the domain, the navigation and the editor roles. Website design for health systems is mostly a series of decisions about shared and local.

Masterbrand or endorsed hospital brands

A masterbrand shows one name everywhere. Endorsed brands keep each hospital’s name with a system endorsement. The choice belongs to brand strategy, covered under healthcare branding, and the site inherits it in logos, page titles and the URL pattern.

One domain or several

One domain with a section for each hospital concentrates authority and keeps the directory, search and analytics in one place. Separate domains make sense when hospitals have distinct identities, legal separation or unrelated operations. Whichever you pick, redirect the others and keep a single canonical home for every doctor profile.

One template set, local content per hospital

Build one set of templates and give each hospital its own content fields: leadership, news, community programs, awards the hospital earned and local contacts. The medical center website design stays consistent, and each hospital still sounds like itself. Local editors fill their fields without touching layout.

Community and critical access hospitals

A smaller or critical access hospital needs the same essentials with a lighter scope: services, the emergency page, clinics, providers, billing help and careers. A smaller scope may fit one of the rows on our fixed-scope table; anything larger is quoted. Smaller does not mean exempt from accessibility.

Careers, nursing and physician recruitment pages

A hospital competes for clinicians as hard as it competes for patients, and the careers section deserves its own attention. Treat it as its own product with its own navigation.

Job search connected to the applicant tracking system

Pull postings from the applicant tracking system, so openings and closings update by themselves, and give each posting a page the search engines can read. Category by role: nursing, allied health, physicians, support. Do not build a parallel job board that someone has to maintain by hand.

Physician recruitment pages

Recruiting physicians has its own strategy, described under Physician recruitment and referral marketing.

Residency, nursing and volunteer pages

Residency programs, nursing education and volunteer programs each serve a distinct audience with a distinct application path. Give each a page with eligibility, dates the program publishes, contacts and a clear apply link. Keep these pages out of the patient navigation, so a patient looking for a doctor never lands in the careers area.

Best hospital website design: what strong hospital sites have in common

The best hospital website design, or best hospital web design if you prefer, shares a few patterns whatever the brand. We describe patterns only. We name no hospital and show no client example, because our site does not hold one for this service.

Homepages built around four tasks

The strongest hospital homepages answer four tasks above the scroll: find a doctor, find a location, book or call, and understand a bill. Everything else, such as news and foundation appeals, sits below. Anyone looking for hospital website examples to copy should study how these tasks are ordered rather than how the hero image looks.

Directories that answer “can I see this doctor soon?”

A useful profile shows the next available appointment type, whether the doctor is accepting new patients, languages spoken and the locations, with one booking button. Directory pages that bury this under biography text send people to the phone, which is the most expensive channel.

Service line landing pages for campaigns

Hospital landing page design is for campaigns: a heart screening drive or a new surgery center opening. Each landing page has one service, one audience and one action, and it reuses service line content rather than duplicating it. This page type is the subject of our landing page design service.

How AI assistants read hospital websites

People now ask assistants who treats a condition near them, which hospital has a certain service and whether a doctor is taking new patients. The answers come from pages that state facts in plain text.

Facts assistants lift from hospital pages

Locations with addresses and hours, services offered at each location, the names and specialties of clinicians, and whether a doctor is accepting new patients. Put those facts in sentences and tables, not only in images, maps or scripts. Keep the facts identical on the site, the directory and every listing.

Structured data hospitals can use

The Hospital and MedicalOrganization types on schema.org describe what a page can say about an organization; we validate structured data per template before launch. Broader visibility work is covered by AEO for hospitals.

How much does a hospital website cost?

A real hospital or health system build is quoted after a written scope, because directory size, integrations, campuses, languages and migration decide the price. The cost of website design for hospitals starts with those five items, so the table below shows only our published fixed-scope rows for smaller sites.

Progression website prices for smaller hospital sites

These rows come from our fixed-scope website pricing page and are written from. Most hospital and health system builds exceed these tiers and are quoted after a written scope.

Why most hospital builds are quoted after a written scope

Directory size, the number of integrations, the number of campuses, the number of languages and the volume of migrated content each change the work. A written scope names them one by one with an allowance against each, which is how we handle integrations on every project.

SEO and tracking work around the build

Some work sits beside the build. These are our published one-off prices, written from.

Ongoing search work is priced as monthly retainers of $1,500 to $2,500, $2,500 to $5,000, $5,000 to $10,000 and $10,000 upward, depending on the market. See our SEO retainers and one-off SEO projects. Hospital advertising is quoted after a written scope.

How to choose a hospital web design company

Hospitals web design succeeds when the team starts with your systems and your owners, not with a mood board, and asks about feeds, review cycles and handoffs on the first call. The same questions apply whether you hire a specialist or a general web design for hospitals partner.

Who designs hospital websites?

In-house teams, outside agencies and directory or portal vendors each take a share. In-house teams usually keep content and governance. Agencies handle structure, design and the build. Vendors own the directory, scheduling and portal products. The split should be written down, with a named owner for every seam.

Questions for a hospital web design company

Ask how it will map and test redirects, how it tests accessibility, who owns the CMS and hosting accounts, what the tracking plan is and how it handles protected health information. Ask for a business associate agreement where the work involves PHI. Ask what is excluded from the scope as well as what is included.

What you own at the end

You own the domain, the hosting, the CMS, the content, the design files and the source. All of it transfers on final payment, and none of it depends on continuing to work with us. A written offboarding process is agreed at the start.

More services for hospitals and health systems

These pages cover the work that sits beside the website.

• Hospital marketing: service lines, access and recruitment
• Healthcare website design: practices and clinics
• Healthcare branding: identity for hospitals and systems
• AEO for hospitals: being named in AI answers
• Healthcare SEO: search for providers
• Healthcare social media: compliant content
• Healthcare advertising: paid media inside the rules
• Digital healthcare marketing: the full channel mix
• Medical marketing: practices and specialists
• Website redesign: rebuilding without losing traffic
• Enterprise SEO: very large sites
• UX design: tasks, flows and testing
• Healthcare app development
• Telemedicine apps
• Healthcare lead generation
• Healthcare PR
• Review management
• Business Profile optimization
• Multi-location marketing
• WordPress maintenance
• Headless CMS options
• AEO for healthcare

Frequently asked questions