Guide

Schema for a One-Clinician Practice: One JSON-LD Block, Two Types Out

Summary

A one-clinician practice marks up its about page as Physician, or as MedicalBusiness when the clinician is not a physician, with the clinician as a Person in the same JSON-LD block. The block carries the name, address, telephone, hours, specialty and NPI exactly as the page prints them, plus sameAs links to the NPI Registry, the Business Profile and the state licence lookup. Leave out ratings markup for the practice's own reviews and FAQPage markup for answers the page does not show: both can draw a manual action.

By Gale Editorial · Updated 2026-09-15. Every figure cited to a dated source. How we write.

Does a solo practice need schema markup to appear in AI answers?

No. Google's guide to its generative AI features says structured data is not required for them and that there is no special schema.org markup to add 1. The block on a practice site does a smaller job. It states the practice's name, address, hours and identifier in a form a machine reads without guessing, and it is also the one place where a vendor's ratings package can get the site flagged.

That smaller job is worth an hour. A five-page site names the practice in a header, an about paragraph, a footer and a contact page, and the four can disagree by a suite number or an old phone line. The block is one statement of the facts, with the values the page shows. When it agrees with the NPI record, the Business Profile and the state licence lookup, the practice reads as one entity across the sources an engine already has. When it disagrees, it is one more conflicting record.

The same guide says a site needs no new machine-readable files or markup to appear in Search, and that adding them neither helps nor harms visibility 1, so the block earns no placement. And the guidelines that welcome the markup also police it: markup describing content readers cannot see can cost the page its rich-result eligibility.

Which type: Physician, MedicalBusiness, or a Person?

Physician for a physician's practice, MedicalBusiness for any other prescriber's practice, and a Person for the clinician inside either. Google asks for the most specific LocalBusiness subtype the site can support 2, and schema.org defines Physician as an individual physician or a physician's office, a subtype of MedicalBusiness, which is itself a LocalBusiness 3.

Physician carries five properties of its own: usNPI, the ten-digit National Provider Identifier that CMS issues; medicalSpecialty; hospitalAffiliation; availableService; and occupationalCategory 3. It inherits address and telephone from Organization, openingHours from LocalBusiness, and sameAs and identifier from Thing 3. A nurse practitioner or physician assistant who owns the practice does not fit the Physician definition, and the type should not be stretched to fit. MedicalBusiness sits one level up in the same tree with the same inherited fields, and the NPI then goes on the Person as an identifier.

The Person is where the clinician's name and credential live. Schema.org's Person type carries jobTitle, honorificPrefix, honorificSuffix, worksFor and memberOf, and it inherits identifier and sameAs from Thing 4. The credential string is the one form of name and credential you use everywhere. Put it in honorificSuffix, the NPI in identifier and the practice in worksFor. A page may carry more than one marked-up entity 5, so the practice and the clinician sit in one script block as two objects.

What goes in the one block

Name and address are the only properties Google requires for LocalBusiness markup; telephone, url, geo, openingHoursSpecification and priceRange are recommended 2. For a practice, add medicalSpecialty and the NPI, and the sameAs list covered below. Every value is copied from the visible page and never typed fresh, because the rule that gets a site flagged is markup describing what readers cannot see 5.

PropertyValueWhere the visible page shows it
nameas the header prints itheader and footer
addressPostalAddress: street, suite, city, state, postal codecontact page
telephoneas the contact page prints it, same formatcontact page
openingHoursSpecificationone entry per day or day range, with opens and closescontact page or footer
medicalSpecialtythe specialty as NPPES lists itabout page
usNPI, or identifier on the Personas NPPES lists itabout page, so print it there
areaServedtelehealth only: the states-served block, as the licence page lists themservices page
sameAsthe four registry URLs belownowhere required

JSON-LD is the format Google recommends 5, and the block belongs on the page that describes the business, where Google says it may make more sense to put LocalBusiness markup 2. On a five-page site that is the about page. The shape, with your values in place of the placeholders:

```json [ { "@context": "https://schema.org", "@type": "Physician", "@id": "https://example.com/about#practice", "name": "Elm Street Practice", "telephone": "as the contact page prints it", "address": { "@type": "PostalAddress", "streetAddress": "…", "addressLocality": "…", "addressRegion": "…", "postalCode": "…" }, "openingHoursSpecification": [ { "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday", "Tuesday"], "opens": "09:00", "closes": "17:00" } ], "medicalSpecialty": "as NPPES lists it", "usNPI": "from the NPPES record", "sameAs": ["NPI Registry URL", "Business Profile URL", "state licence lookup URL", "profile URL"] }, { "@type": "Person", "name": "as the licence board prints it", "honorificSuffix": "as the licence board prints it", "identifier": { "@type": "PropertyValue", "propertyID": "NPI", "value": "from the NPPES record" }, "worksFor": { "@id": "https://example.com/about#practice" }, "sameAs": ["NPI Registry URL", "state licence lookup URL"] } ] ```

Print the NPI on the about page, so the markup describes what a reader can see. And copy the telephone and address from the contact page instead of retyping them; a transposed digit in the block is a second phone number the practice now claims.

Where the sameAs list points

A sameAs value is the URL of a reference page that unambiguously indicates the item's identity, in schema.org's own words 4. For a practice that means four URLs: the clinician's record in the NPI Registry, the Google Business Profile, the state licence lookup, and the gale.care profile. With the site itself, those are the five sources an engine can reconcile, and the list is what separates the practice from another clinician with the same name.

The list is the same set of identifiers that make up the disambiguation kit, and it works only while every target agrees. A sameAs pointing at a Business Profile that still carries last year's suite number points at a contradiction. Gale keeps a provider's gale.care page consistent with the NPPES record, with the NPI visible, and announces the page through IndexNow the day its facts change. The other three targets are the provider's own to keep current.

The two types that invite a manual action

Ratings markup for your own reviews, and FAQPage markup for answers the page does not show. Google's review snippet documentation says that when the entity being reviewed controls the reviews about itself, its pages using LocalBusiness or any other Organization type are ineligible for the star feature, whether the rating sits in the structured data or arrives through an embedded third-party widget such as a Google Business reviews widget 6.

The local business documentation says the same from the other side: review and aggregateRating are recommended only for sites that capture reviews about other local businesses 2. A website package that drops an aggregateRating into the practice block is marking up what the guidelines exclude, and the general guidelines name fake reviews as their first example of misleading markup 5. How the practice asks for reviews is a separate problem. Review gating is asking only the people expected to be pleased, and deleting a script tag does not fix it.

FAQPage is the second. The general guidelines say not to mark up content that is not visible to readers of the page 5, and an FAQPage block whose questions and answers appear nowhere on the page is exactly that. The reward is gone in any case: Google's documentation changelog records that the FAQ rich result stopped appearing in Search on May 7, 2026, and that its documentation was removed the following month 7. A visible FAQ section with matching markup breaks no rule and earns no rich result.

A structured data manual action removes the page's eligibility to appear as a rich result and shows in the Search Console Manual Actions report; Google says it does not affect how the page ranks in web search 5.

Validate it, then keep it identical to the page

Paste the block into the about page, then run the page through the Rich Results Test, which Google names as the check for its technical guidelines 5, and through the Schema.org Markup Validator. Then read the block against the page, field by field. The validator checks syntax; whether the hours match is something you check by reading.

The block drifts the same way the page does: someone changes the hours on the contact page and nobody opens the script tag. So the check is a calendar entry, once a quarter, comparing the block, the visible page and the NPPES record on name, address, phone, hours and NPI. The monthly prompt panel gives an earlier warning when an answer engine returns the practice with an old address; the block and the page are the first two places to look.

This is the technical half of local SEO for a one-clinician site; the Business Profile is the other half, and both are checked against the same NPPES record. The block's job is to say, in a form a machine reads, what the five-page website already says in prose.

Common questions

Physician, if the clinician is a physician. Google asks for the most specific LocalBusiness subtype a site can support, and Physician adds usNPI and medicalSpecialty, which LocalBusiness lacks. A nurse practitioner or physician assistant who owns the practice uses MedicalBusiness, the parent type, and carries the NPI on the nested Person as an identifier. Plain LocalBusiness is valid but says less than the page already knows.

Leave them out of the markup. Google's review snippet rules make pages ineligible for star snippets when the entity being reviewed controls the reviews about itself, and that includes ratings pulled in through an embedded Google Business reviews widget. The local business documentation recommends review and aggregateRating only for sites that collect reviews about other businesses. Quotes may stay visible on the page as ordinary text.

The about page, in one script tag of type application/ld+json. Google says LocalBusiness markup can go on any page but may make more sense on a page that describes the business, and the about page is where the name, credential and NPI are printed. Most site builders accept the tag in a page's custom code or header field. Put it on the about page only, and do not copy it to the contact page.

Open the page source and read what it added before writing anything. A builder's block often declares a generic LocalBusiness with the wrong hours, and some vendor packages include an aggregateRating for the practice's own reviews, which is the self-serving pattern Google excludes. Either replace the vendor block with yours or remove it, so the page carries one description of the practice and every value in it matches the visible text.

No. Google's documentation changelog records that the FAQ rich result stopped appearing in Search on May 7, 2026, and the feature's documentation was removed afterwards. A visible FAQ section is still useful reading and may carry matching markup without breaking any rule. An FAQPage block describing questions and answers that do not appear on the page is markup for invisible content, which is the pattern that draws a manual action.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

  1. 1.Google Search Central (2026). Google's Guide to Optimizing for Generative AI Features on Google Search. Google Search Central documentation (developers.google.com). link ✓Google's statement that structured data is not required for its generative AI features, that no special schema.org markup exists for them, and that new machine-readable files neither help nor harm visibility.
  2. 2.Google Search Central (2026). Local Business (LocalBusiness) Structured Data. Google Search Central documentation (developers.google.com). link ✓Which LocalBusiness properties Google requires (name, address) and recommends; that review and aggregateRating are recommended only for sites capturing reviews about other businesses; the most-specific-subtype instruction; and where on a site the markup belongs.
  3. 3.Schema.org Community Group (2026). Physician - Schema.org Type. Schema.org. link ✓The schema.org definition of Physician, its place under MedicalBusiness and LocalBusiness, its own properties usNPI, medicalSpecialty, hospitalAffiliation, availableService and occupationalCategory, and the properties it inherits from Organization, LocalBusiness and Thing.
  4. 4.Schema.org (2026). Person - Schema.org Type. Schema.org vocabulary (V30.1). link ✓The Person type's jobTitle, honorificPrefix, honorificSuffix, worksFor and memberOf properties, its inherited identifier and sameAs, and schema.org's definition of sameAs as a reference URL that unambiguously indicates identity.
  5. 5.Google Search Central (2026). General Structured Data Guidelines. Google Search Central documentation (developers.google.com). link ✓Google's general structured data rules: JSON-LD recommended, markup must describe content visible to readers and must not be misleading, multiple entities may be marked on one page, the Rich Results Test checks technical guidelines, and a structured data manual action removes rich-result eligibility without affecting ranking.
  6. 6.Google Search Central (2026). Review Snippet (Review, AggregateRating) Structured Data. Google Search Central documentation (developers.google.com). link ✓That a page using LocalBusiness or any Organization type is ineligible for star review snippets when the entity controls the reviews about itself, directly in markup or through an embedded third-party widget.
  7. 7.Google Search Central (2026). Latest documentation updates. Google Search Central, What's new (developers.google.com). link ✓The dated changelog entries recording that the FAQ rich result stopped appearing in Google Search on May 7, 2026 and that its documentation was removed the following month.

https://www.gale.care/for-providers/aeo-practice-schema-one-block · 7 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

← Back to for providers

Findability, by specialty

How practices like yours get found in local search and AI answers — the honest playbook, per specialty.

SEO for private practices · SEO for AI search / answer engines (all verticals)