§ Service

Medical Website Design

Medical website design.

Abstract

The SEO architecture, the schema layer, the HIPAA-compliant intake routing, and the ABMS author-byline patterns all sit upstream of the visual design. Practices that build visually first and retrofit SEO and compliance afterward end up with information architecture that fights the commercial-query intent and forms that route PHI through tools that did not sign a Business Associate Agreement.

Book a diagnostic →

Website design is the foundational layer of our medical practice SEO retainer. It carries the schema architecture, the HIPAA-compliant intake routing, the author-byline templates, and the URL structure the rest of the work runs against.

What lives upstream of the visual brief

Four architectural decisions. Each one before pixels.

The architecture decisions that govern medical-vertical site outcomes sit upstream of the visual brief. SEO architecture, intake-form compliance, schema discipline, and author-byline patterns are foundational, not retrofittable.

SEO architecture decided before visual design.

The page hierarchy, the URL structure, the internal-link plan, the schema layer, and the canonical strategy all sit upstream of the visual brief. Practices that build the site visually first and retrofit SEO architecture afterward end up with information architecture that fights the commercial-query intent. A specialty group with cardiology and electrophysiology sub-practices needs the EP sub-practice on its own page tree from day one, not bolted onto the cardiology page when ranking gaps surface a year in.

HIPAA-compliant intake routing as a foundational requirement.

Patient intake forms collect protected health information the moment a patient describes symptoms. The form needs to route through a covered-entity-controlled surface, not a third-party form tool that does not sign a Business Associate Agreement. The intake architecture decides whether a form is HIPAA-compliant before the first patient submits one. Practices that ship forms first and ask HIPAA questions second create exposure that retrofitting cannot fully resolve.

MedicalBusiness and Physician schema baked into the build.

Schema injected as an afterthought rarely chains correctly. The MedicalBusiness type for the facility, the Physician nodes for each practitioner, the worksFor / employee / hospitalAffiliation chains, the sameAs reconciliation to NPPES + state board + ABMS. all of it needs to live in the page templates so every physician roster change updates the schema automatically through the CMS. Hand-edited JSON-LD on a per-page basis breaks within a quarter.

ABMS board-certified author-byline patterns at the template level.

The Reviews System 2023+ medical-content framework reads first-party editorial content for practicing-physician reviewer signals. The author byline template surfaces the ABMS specialty, the active state license, the institutional affiliation where it applies, and the link to the physician's standalone profile page. Editorial content authored by a credentialed physician at the practice carries the byline; content authored by an outside contributor sits clearly separated. The architecture decides which surfaces are byline-eligible for YMYL evaluation.

Side by side

SEO-architecture-first versus the visual-first retrofit, on the surfaces that govern medical YMYL outcomes.

SEO-architecture-first build

Schema + intake + byline baked in

Visual-first retrofit

SEO and compliance added later

Page hierarchy

Designed against the commercial-query intent map; sub-specialty pages on their own page tree from day one

Designed against visual flow; sub-specialties collapsed into parent pages until ranking gaps surface

Intake form compliance

Routes through a covered-entity-controlled surface or a BAA-signed third-party tool. Designed in from the start.

Generic form tool without BAA. PHI exposure created by default.

Schema layer

MedicalBusiness + Physician + worksFor / hospitalAffiliation / sameAs baked into page templates and updated through the CMS

Hand-edited JSON-LD or off-the-shelf plugin output. Drift within a quarter.

Author byline template

Surfaces ABMS specialty, active state license, institutional affiliation, link to standalone Person profile. Reviews System reviewer-signal compatible.

Generic byline or no byline. Editorial YMYL evaluation triggers demotion.

URL structure

Clean slugs aligned with commercial queries. No descriptive suffixes. No CMS-generated /category/ noise.

CMS-default URL structure with /services/cardiology/heart-rhythm/ stacking. Query-to-URL alignment fragmented.

Performance budget

Performance budget set against Core Web Vitals thresholds from the start. Image and font weights designed in.

Performance addressed after launch when the LCP and CLS scores surface as ranking signals.

SEO-architecture-first build

Schema + intake + byline baked in

Page hierarchy: Designed against the commercial-query intent map; sub-specialty pages on their own page tree from day one
Intake form compliance: Routes through a covered-entity-controlled surface or a BAA-signed third-party tool. Designed in from the start.
Schema layer: MedicalBusiness + Physician + worksFor / hospitalAffiliation / sameAs baked into page templates and updated through the CMS
Author byline template: Surfaces ABMS specialty, active state license, institutional affiliation, link to standalone Person profile. Reviews System reviewer-signal compatible.
URL structure: Clean slugs aligned with commercial queries. No descriptive suffixes. No CMS-generated /category/ noise.
Performance budget: Performance budget set against Core Web Vitals thresholds from the start. Image and font weights designed in.

Visual-first retrofit

SEO and compliance added later

Page hierarchy: Designed against visual flow; sub-specialties collapsed into parent pages until ranking gaps surface
Intake form compliance: Generic form tool without BAA. PHI exposure created by default.
Schema layer: Hand-edited JSON-LD or off-the-shelf plugin output. Drift within a quarter.
Author byline template: Generic byline or no byline. Editorial YMYL evaluation triggers demotion.
URL structure: CMS-default URL structure with /services/cardiology/heart-rhythm/ stacking. Query-to-URL alignment fragmented.
Performance budget: Performance addressed after launch when the LCP and CLS scores surface as ranking signals.

Updated 2026-05-28

How we engage

Diagnostic, then monthly retainer. Four phases, each scoped against cited deliverables.

Weeks 0-2

Diagnostic

We read your Search Console data, your traffic data, your current Schema.org markup, your physician author bylines, your testimonial pages, and your directory-profile completeness. The diagnostic comes back with the load-bearing pages, the dead weight, the YMYL-fragile content, and the entity-graph gaps. For multi-location groups, we add a GBP audit per practicing location.
Weeks 2-6

Schema and author layer

We build the MedicalBusiness and Physician schema layer with sameAs chains to NPI registry, ABMS verification, and state medical board profiles. Author bylines surface ABMS specialty and active state license alignment. CPT-aligned service pages where the procedure mix supports it. The schema layer reflects what each page actually is, MedicalCondition / MedicalProcedure types reserved for the editorial layer.
Weeks 4-8

Reviews System alignment

Editorial content rebuilt against the Reviews System 2023+ medical-content framework. Practicing-physician reviewer signals on first-party content. PubMed-cited primary literature replacing health-magazine summaries. Topic-to-specialty alignment in every author byline (a general practitioner does not author complex oncological articles). Patient testimonial workflow routed through the 45 CFR 164.508 consent path before any testimonial lands on a service page.
Monthly

Ongoing retainer

Monthly cadence on the rest of the site, plus content cadence for the queries the diagnostic surfaced. Quarterly review against your traffic data and Search Console movement. Re-audit of the entity-graph reconciliation when physician rosters change. Re-audit of the consent workflow when state medical board advertising rules change.

Common questions

Questions practice administrators ask before booking a diagnostic.

01.

We have a working website. Do we need a rebuild or can you work on top of what we have?

Depends on what's there. If the existing site has reasonable URL structure, decent schema architecture, and HIPAA-compliant intake routing, the work runs as a content and entity-chain retainer on the existing build. If the URL structure fights the commercial-query intent map, the schema is hand-edited (not template-driven), and the intake forms run through a non-BAA third-party tool, the retrofit cost approaches the rebuild cost and a rebuild produces a cleaner outcome. The diagnostic surfaces the decision.

02.

What CMS do you build on?

Astro, WordPress, Webflow, and headless setups all work. The architectural decisions sit above the CMS choice. We build on Astro by default for new sites because the static-output performance budget and the per-template schema control fit medical-vertical YMYL requirements. For practices on WordPress with an existing content team trained on WordPress, we work within WordPress as long as the schema layer can be controlled through templates and the intake forms can be routed through a HIPAA-compliant surface. The CMS is a constraint on the work, not the work itself.

03.

Do you handle the design or do we bring our own designer?

Either way works. Praxis works with the practice's designer where one is engaged, and we provide a design partner for practices that need one. The SEO architecture and the regulatory compliance work sit upstream of the visual design either way. We document the architectural decisions in a brief the designer works against, so the visual brief honors the page hierarchy, the schema constraints, and the byline patterns the YMYL evaluation requires.

04.

How does HIPAA-compliant intake routing actually work?

Patient intake collects protected health information the moment a patient describes symptoms or shares insurance details. The form has to route through a surface controlled by the covered entity (the practice) or through a third-party tool that signs a Business Associate Agreement. Generic form tools (Typeform, Google Forms, default Webflow forms) do not sign BAAs. HIPAA-aware alternatives (JotForm HIPAA-tier, Formstack HIPAA-tier, Cognito Forms HIPAA-tier, or a custom backend the practice controls) do. The architecture decides the routing at template level; every form on the site inherits the compliant surface by default.

05.

What about CPT-aligned service pages?

CPT (Current Procedural Terminology) codes are the AMA's standardized taxonomy for medical services. Aligning service pages to CPT codes where it's defensible gives the content a clean entity boundary and lets the schema layer reference the procedure correctly without crossing into MedicalProcedure schema territory (which stays on editorial content). The alignment matters most for procedure-driven practices: plastic surgery, dermatology cosmetic, orthopedics, fertility, where the patient query often maps to a CPT-coded procedure. For primary care and other consultation-driven practices, the CPT alignment is lighter touch.

06.

What's the typical timeline for a rebuild?

8 to 16 weeks depending on the size of the existing surface and the complexity of the physician roster. Weeks 0 to 2 cover the SEO architecture diagnostic and the commercial-query intent map. Weeks 2 to 6 cover the schema layer, the entity-chain reconciliation across NPPES + state board + ABMS, and the intake-form compliance design. Weeks 4 to 12 cover the template build, the editorial-content migration, and the per-physician profile pages. Weeks 12 to 16 cover the cutover, the 301-redirect map from the old URL structure, and the immediate post-launch monitoring against ranking decay.

Stop watching your competitors rank

If your existing site fights the commercial-query intent map, the rebuild cost is usually lower than the retrofit cost.

The diagnostic surfaces whether the existing site is workable, what the rebuild scope would look like, and what a grounded migration plan covers. The schema layer, the intake-form compliance, and the author-byline templates are the load-bearing surfaces either path has to ship.

Book a diagnostic → Email us