Each surface verifiable. Each surface aligned to the same licensure footprint.
A per-state telehealth landing page exists to capture the state-specific commercial query and route the visitor into a defensible intake. The page has to clear five surfaces simultaneously. State-board advertising rule alignment, where the page text complies with the per-state medical-practice marketing rules (Florida's testimonial-typicality rule, California's Business and Professions Code §651, Texas Medical Board's advertising rule, New York's similar provisions) that govern claims and disclosures. IMLC vs independent-licensure positioning, where the page surfaces the path the attending physician actually used to reach that state. Schema.org Physician.areaServed scoped to the verified licensed-state list rather than aspirational coverage 1 . GBP NAP (name, address, phone) consistency across the physician-owner's per-state directory listings. Intake routing that captures the patient's current location at scheduling time.
The five together form the architectural signal a state board compliance scan can cross-reference against the federal record at NPPES and the board's own licensure database 2 . Drift on any one of the five surfaces opens the surface to enforcement action: a per-state page asserting capability where the schema's areaServed disagrees, a GBP listing claiming a physical presence where the practice has none, an intake form pre-filling the patient's state from the URL when the patient is traveling out of state. Each surface either reinforces the others or contradicts them; the architecture has no quiet failure mode.
Per-state architecture and the licensure footprintPer-state pages exist only for states the practice can defensibly serve.
The architectural starting point is the verified licensure footprint: the list of states where at least one attending physician holds active licensure through the IMLC pathway, an independent state-by-state application, or a qualifying state-specific telehealth registration 5 . The per-state page set matches the footprint. A practice with attending physicians licensed across 22 states ships 22 per-state pages, not 50. The aspirational pattern of pre-building all 50 state URLs as thin placeholders and filling them in as licenses arrive reads to Google's quality signals (thin content, low-engagement signal) and to a state board compliance scan (the marketing claims capability that the licensure cannot back) as the same misrepresentation the architecture is supposed to prevent.
The URL pattern choice is consistent within the site. Either per-state pages nest under the telehealth path (/telehealth/[state]/) or live at the top level with the state name verbatim (/california-telehealth/). The choice tracks the rest of the site's URL architecture; consistency across the licensure footprint matters more than which pattern. Internal linking from the hub of healthcare SEO work at Praxis routes through the IMLC explainer at the compact's pathway and into each per-state page. The breadcrumb surfaces the hierarchy. The schema's MedicalBusiness markup names the physical operating location; the per-state page references the physician(s) licensed in that state via employee or member on the page's MedicalBusiness node.
Populated with the verified license list. Not the targeted-query list.
The Physician.areaServed property is the machine-readable surface that Google reads against the per-state landing-page set 1 . The property's value is an array of State nodes (or the equivalent textual representation per the practice's structured-data implementation) listing the states where the physician holds active licensure. The implementation surfaces the licensure footprint as a machine-verifiable claim that a state board's compliance scanner can cross-reference against NPPES and the board's own licensure database. The reconciliation is direct: the sameAs chain on the physician's schema points to the NPPES record + the State of Principal License board profile + the ABMS verification page 3 ; the areaServed list reads alongside as the active licensure-footprint claim.
The clinical-content schema types belong on a different surface. MedicalCondition, MedicalProcedure, MedicalTherapy sit on encyclopedic editorial content, not on commercial location pages. Applying clinical types to a commercial location surface reads to Google's medical classifiers as an attempt to manipulate medical rich results, and the manual-action pattern that follows the misuse is well-documented. The per-state location pages mark up with MedicalBusiness + availableService; the editorial content under the practice's research or education section carries the clinical types with the ABMS-certified author bylines.
The patient's location at the moment of service. Captured at scheduling, not assumed from the URL.
Google Business Profile listings align with the physical operating locations the practice actually maintains under Google's GBP guidelines for the medical category 6 . A telehealth-only practice without per-state physical operating locations cannot legitimately create per-state GBP listings; the GBP layer carries the listing for the physical operating location(s), and the per-state landing pages carry the licensure-footprint signal through schema and content. NAP consistency holds across the physician-owner's directory listings (Healthgrades, Zocdoc, Vitals, NPPES) so the entity-graph reconciliation across the directory ecosystem aligns on the practice's verified facts rather than splitting across conflicting records.
The intake routing on the per-state page captures the patient's current location at the time the consult is scheduled, not the patient's residential address. AMA Code Opinion 1.2.12 binds the licensure requirement to the patient's location at the moment of service 4 . A page that pre-fills the state from the URL (the visitor landed on /california-telehealth/, so the scheduling form assumes California) misroutes when the patient is traveling out of state. The page's URL targets the query; the intake captures the fact. The routing then assigns the consult to the attending physician licensed in the captured state. A multi-physician practice that operates across the IMLC footprint plus several non-participant states routes each query to the physician licensed in the patient's location. The architecture is verifiable end to end.