Skip to main content
Enterprise Healthcare Case Study Methods & Systems Precedent

Making Complex Specialty Care Easier to Navigate

How an academic health system unified hundreds of clinical specialties into a structured, patient-centered component operating system that search engines and patients can easily navigate.

Client / Domain Academic Medical Center (UC Health)
My Role SEO Manager & Content Architect
Core Deliverable 14 Reusable Component Specs
Relevant Service Strategy & Roadmap

1. Context & The Initial Challenge

Academic medical centers provide some of the world’s most advanced subspecialty medicine—from rare genitourinary cancers to complex skull-base neurosurgery. However, their websites often reflect internal administrative departments and academic silos rather than how vulnerable patients actually search for care.

At UC Health, hundreds of clinical service lines, programs, and condition pages were managed across scattered documents with inconsistent authoring rules. Writers had to guess which components to use, clinical faculty were frustrated by ad-hoc interview requests, and patients struggled with conflicting navigation between condition overviews, physician profiles, and scheduling triage.

2. My Role & Delivery Ownership

Serving as the in-house SEO Manager and content systems lead, I was responsible for bridging the divide between clinical subject-matter experts (physicians and nurse practitioners), brand marketing, and the technical web development team.

Rather than treating SEO as a post-launch keyword polish, I designed the structural taxonomy and co-architected the Component Operating System. I established how information is gathered, governed, assembled, and indexed across the digital footprint.

3. Operating Constraints

Clinical SME Capacity

Attending physicians have packed surgery schedules and clinical rounds. We could never expect clinicians to write marketing copy or review lengthy open-ended drafts.

Strict Medical Compliance

Medical information requires strict factual adherence, plain-language patient explanations, and exact adherence to credentialing without hyperbolic marketing superlatives.

Complex Information Hierarchy

Dozens of multidisciplinary programs overlap (e.g. Cancer Institute vs. Surgery vs. Radiation Oncology), requiring explicit wayfinding components to avoid canonical confusion.

Multiple Authoring Stakeholders

Content had to be drafted reliably by internal marketing consultants, freelance writers, and structured AI workflows without deviations from brand style.

4. Diagnosis & The Core Insight

Architectural Thesis

“Meaning lives in structure, hierarchy, prominence, and context.”

When pages fail to rank or confuse patients, the problem is rarely a shortage of keywords. The failure happens because content is treated as unstructured prose in Word documents rather than modular data linked to distinct user tasks.

5. Approach: The 3-Layer Component Operating System

To solve this systematically, I developed a 3-Layer Model that treats every website component (from the hero banner to interactive triage tabs) as structured data:

Layer 1

Intake Schema (The Raw Input)

Instead of asking physicians “Write a headline,” we ask structured questions: “What is the primary patient symptom?”, “Which conditions do you co-manage with primary care?”, and “What are the direct referral criteria?”

Layer 2

Shared Governance (The Rules & Constraints)

Non-negotiable guidelines for human writers and AI prompts alike: character caps, heading syntax (no punctuation in H2s), mandatory reading-level targets (8th-grade Flesch-Kincaid), and explicit bad-smell tests (e.g. banning unverified claim words like “best” or “leading”).

Layer 3

Assembly Instructions (The Prompt & Field Spec)

A precise assembly specification that maps Layer 1 inputs through Layer 2 constraints into the CMS component schema, enabling consistent, scalable drafting across thousands of clinical assets.

6. Delivered System Artifacts: Re01–Re14 Component Suite

The system established 14 reusable components divided into three distinct functional categories:

Marketing & Storytelling
  • • Re01 Hero + Carousel: Visual anchor for service lines with strict headline character caps.
  • • Re05 Benefit Pillars: 3–6 column grid clarifying clinical advantages.
  • • Re06 Featured Benefit: Square image + narrative block for clinical milestones.
  • • Re09 Featured Story: Patient impact narrative highlighting specialized care paths.
Wayfinding & Triage
  • • Re02 Specialties Grid: Structured crawlable links to sub-specialties.
  • • Re04 Interactive Tabs: High-density triage tab combining clinical services with consumer health library.
  • • Re03v1 Quick Links: Task-based cards for patients (Pay Bill, Find Doctor, Virtual Visit).
  • • Re03v2 Journey Tabs: Patient journey steps for new vs. returning patients.
Utility & Trust
  • • Re07 Feature Stat Cards: Trust-building volume and outcome figures.
  • • Re10 In the News: Tag-driven clinical trials and press releases.
  • • Re12 Locations & Map: Multi-clinic routing with schema coordinates.
  • • Re13 Contact & Scheduling: Direct call-to-action routing per clinical department.
Architectural Decision Spotlight: The Re02 vs. Re04 Triage

Solving the "Everything Is Important" Service Page Paradox

When clinical departments wanted to list 40 different conditions on a single landing page, simple link lists created visual exhaustion and high bounce rates. We engineered Re04: an interactive tabbed matrix separating primary conditions from wellness articles. This allowed search engines to discover all deep URLs while keeping the immediate visual experience clean and accessible for stressed patients on mobile devices.

7. Verified Result & System Impact

In accordance with our evidence standards, we separate delivered operational artifacts from multi-factor organizational metrics:

✓ Standardized 14 Reusable Component Specs: Completely documented in a central source-of-truth operating system with explicit field definitions and QA acceptance tests.
✓ Eliminated Writer Guesswork: Created a governed assembly pipeline enabling multiple writers to draft complex clinical landing pages with zero deviations from brand or medical compliance.
✓ Structured Physician Intake: Replaced open-ended copy requests with targeted 5-question intake schemas that respect clinician time.

8. Limitations & Attribution Notes

Digital health redesigns occur in multi-year phases across large clinical enterprises. System components roll out gradually across service lines. Overall health system traffic gains reflect combined contributions from marketing teams, PR, EHR integrations, and search demand shifts; this case study documents the content architecture and component systems design specifically.

Strategic Takeaway for Prospects

Do not ask subject experts to write copy. Build an intake schema.

Whether you run a hospital system or a national consulting firm, your experts should provide facts, symptoms, and nuances—not polished marketing paragraphs. When you establish explicit components with predefined character rules and prompt schemas, high-quality search content becomes repeatable and scalable.

Need a structured content architecture for your website?

Explore how the SEO Strategy & Roadmap engagement applies these methods.

Direct Expert Advisory

Let’s make your next SEO decision clearer

Tell me what you want to improve, where the work is getting stuck, and who is involved. We can explore whether a focused project or ongoing advisory partnership is the right fit for your team.

Personal delivery by Matthew Conner · No junior account reps · Response within 1 business day