Local AI visibility for a medical practice: getting the place right

Why is a practice's address harder to state than it looks?

Because a medical address has parts many business addresses do not: a building name, a suite, a floor, sometimes a campus with its own street address, sometimes a hospital's name in front of all of it. Each part can be written several ways, and each way is a different string. A patient reading your contact page copes with that. Five spellings across your site, your map listing and three insurer directories leave anyone comparing them to work out whether they describe one office or five.

The audit measured the general form of this problem. In our audit of 9,483 small business websites across 40 trades and 90 metros, run between late August and early September 2026, 43.1% were inconsistent about who and where they are across their own three main pages. 36.9% published more than one phone number, and 34.1% had no postal address a machine could parse on any of them. All three describe the whole sample, not medical practices in particular.

Then there is movement. Physicians join, retire and change offices; a practice opens a second location, or joins a health system and takes its name. Every change leaves the old fact behind somewhere: a footer, a PDF form, a directory, a hospital's find-a-doctor page. The work is deciding the one true version of each place fact, so that the practice reads as one entity, and then making every copy say it. What a practice states beyond its places is gathered in the overview for medical practices.

One address, written one way everywhere

Choose the form your postal service uses, suite included, and use that exact string wherever the address appears: the footer, the contact page, each office page, the markup and every listing you control. "Suite 200", "Ste 200", "#200" and "2nd floor" can all be true of one office; pick one and retire the others. The building name and the way in (which entrance, which floor, where to park) go in a sentence of directions beside the address, where a patient reads them, and stay out of the street line.

If your building has two addresses, a campus address and a street address, use the one mail is delivered to and a navigation app finds, and name the other once, in the directions. The same goes for a building patients know by a name ("the medical arts building"): the name belongs in the directions, the postal form in the address. A block like this, identical in every footer, carries the place facts in one piece.

[Practice name]
[Street number] [Street name], Suite [number]
[City], [State or province] [Postal code]
Main line: [number]

In the [building name], [which entrance], [floor].
Parking: [where, and whether it is validated].

The markup repeats the same string, split into its parts. In it the office is a Physician node, or a MedicalClinic node for a clinic (both are MedicalBusiness types, part of the LocalBusiness schema family), and its address is a PostalAddress whose parts match the visible text exactly, written as JSON-LD. Google's local business documentation lists name, address, telephone and opening hours among the properties it reads.

{
  "@context": "https://schema.org",
  "@type": "Physician",
  "name": "[Practice name]",
  "telephone": "[main line]",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "[Street number] [Street name], Suite [number]",
    "addressLocality": "[City]",
    "addressRegion": "[State or province]",
    "postalCode": "[Postal code]",
    "addressCountry": "[two-letter country code]"
  }
}

Several offices: one site, and a page for each

A practice with more than one office is one organization with several places, and the site should say exactly that: one site, one page per office. A patient who asks for a doctor near one of them should land on a page about that office, not on a list of every address the practice has. The table is what each office page carries.

Each office gets its own node, of the same type, with the same practice name, its own address, telephone and hours, and the practice as its parentOrganization. The hours go in OpeningHoursSpecification by day, so that an office that closes early on Fridays says so. When you measure, the panel needs a location question for each office, as measuring a practice's AI visibility explains.

Label every phone number. A practice can have a main line per office, a fax, a billing number, an after-hours line and sometimes a number that belongs to an answering service; published without labels, that is five phone numbers for one place. Put the office's main line in its markup and in the footer of its page, and write the others once, each with what it is for.

Do not build pages for towns where you have no office. A page titled with a suburb, over the same text as a real office page, describes an address you do not have. If patients come from nearby towns, the office page can say how far the office is from them, in a sentence, as a fact.

Hospital affiliations, and practices inside a hospital's building

State each affiliation as a fact about a named clinician: the hospital by the name it uses for itself, and what the affiliation is, such as admitting privileges or the hospital where that physician operates. "Affiliated with the region's leading hospitals" is an adjective. "[Physician name] has admitting privileges at [Hospital]" is a fact a patient can check and a machine can match against a question that names the hospital.

Being in a hospital's building is a different fact from being part of the hospital, and the page has to say which. A practice in a medical office building on a campus that writes only "at [Hospital] Medical Pavilion" leaves every reader, human or machine, to guess whether it is the hospital's own practice. Say it outright: an independent practice located in the building, or part of [health system], under that name. If you belong to a system, use the name the system uses for you, because its directory will.

schema.org's Physician type has a hospitalAffiliation property for the hospital a physician or an office is affiliated with. Use it on a Physician node for an affiliation the whole office holds, and state each clinician's own affiliations in their text, where a patient reads them. Markup that states an affiliation the page never mentions is a claim no visitor can see, which Google's introduction to structured data asks you not to make.

Address or service area: which one a practice publishes

A practice patients come to publishes its address, because that is where the care happens. For care delivered away from the office, use areaServed, the property for the area a service covers: the states or provinces where your clinicians are licensed to see patients by video, or the towns you cover for house calls. List those in text on the page that describes that service, and in the markup on the same node.

What belongs in neither is a region nobody can check. "Serving the greater metro area" states no place a patient's question could match. An office address, a list of towns for house calls and a list of states or provinces for video visits are three separate facts; written separately, each can be matched to the question it answers.

The directories that have to agree with your site

A practice's address is published in many places, and several of them are edited by someone else. The rule for all of them is the same: your site is the master record, and every other copy is corrected to match it.

1. Write the master record: for each office, the address in its fixed form, the main line, the hours and the clinicians who practice there. Date it.
2. Look up the practice and each clinician by name in every directory in the table, and copy what each shows into a sheet beside the master record.
3. Mark every difference, however small: a missing suite, an old number, a clinician listed at an office they left.
4. Fix your own pages first, then the map listing, then send each insurer and hospital its correction with the master record attached.
5. Check again whenever a clinician joins, leaves or changes offices, or an office changes its hours, because a directory changes only when someone sends it the change.

The site comes first because it is the one copy where you control every word, and the one you point an insurer or a hospital to when you ask for a correction. A directory entry cannot be corrected against a site that disagrees with itself. Once the copies agree, measure whether the answers changed, on the fixed panel our methodology describes, with a location question for each office.