A local medical clinic or med spa needs a targeted set of schema markup that directly helps Google match local patient searches with specific medical services. Instead of bloating your site with unnecessary code, focus on implementing clean LocalBusiness or MedicalBusiness schema with matching NAP data, Service schema for treatments, and FAQ schema for common patient concerns. This direct, tight mapping ensures Google displays your business details and treatment offerings accurately in local search and AI engines.
If you are trying to figure out what schema markup does a clinic need, do not make the mistake of copy-pasting every block of code you find on the web. A cluttered implementation will only confuse the search crawlers and dilute your ranking authority.
Skip the schema kitchen sink
Many web designers and SEO plugins suffer from a common affliction: they try to add every possible schema type to a website. They build elaborate graphs containing Organization, WebSite, WebPage, Service, Product, and Article schema, all mixed together in a single page head.
For a local medical clinic or med spa, this kitchen-sink approach is a waste of time. It often does more harm than good by creating conflicting data points. Google does not reward you for the sheer volume of code you write; it rewards you for clarity and accuracy.
Patients search for clinics in a very specific way. They look for local businesses nearby, and they search for specific treatments they want to receive. For instance, a searcher might look for "med spa near me" or "laser hair removal in Austin."
Your structured data needs to answer those two queries directly. It should tell Google exactly where your physical clinic is located, and it should detail the precise medical or cosmetic services you perform. Any code that does not serve these two goals is filler that you should remove.
The core foundation: MedicalBusiness and LocalBusiness schema
Every clinic website must start with a physical location entity. In the Schema.org vocabulary, you have access to a specific type called MedicalBusiness. This is a specialized subclass of LocalBusiness designed specifically for doctor offices, wellness centers, and med spas.
Using MedicalBusiness is superior to using generic LocalBusiness because it allows you to define medical specialties, accepted insurances, and practitioner credentials. It acts as the digital anchor for your clinic, translating your physical storefront into structured data that Google can read.
The most important rule when configuring your MedicalBusiness schema is absolute NAP consistency. NAP stands for Name, Address, and Phone number.
The values you enter into your schema code must match the text on your website footer, your Google Business Profile, and third-party directories like Yelp or Healthgrades. Even minor discrepancies, such as writing "Suite 200" in one place and "#200" in another, can prevent Google from connecting the dots.
When writing your MedicalBusiness JSON-LD, make sure to populate the following properties:
@id: A unique URL identifier for this physical location (usually your homepage URL with#clinicat the end).name: The official name of your clinic.address: The street address, city, state, postal code, and country.telephone: The primary phone number, including the country code.geo: The exact latitude and longitude coordinates. This helps Google Maps place your pin accurately.openingHours: Your weekly business hours.priceRange: A general indicator of your pricing, such as "$$" or "$$$".image: A high-quality photo of your clinic's exterior or lobby.
By providing this clean dataset in the raw HTML of your homepage, you give Google the exact information it needs to display your clinic in the Local Pack search results. You can find detailed technical guidance on schema properties in the official Schema.org MedicalBusiness specification.
Mapping treatments with Service schema
A common error I see on clinic websites is using Product schema to represent treatments like Botox, chemical peels, or dermal fillers. Clinic owners do this because they want Google to display pricing and availability in search results.
However, treatments are not retail products. They do not have GTINs, physical shipping weight, or standardized inventory. Placing Product schema on a medical treatment page will trigger validation warnings in Google Search Console, and Google's systems will often ignore the markup.
The correct approach is to use Service schema (or the more specialized MedicalTherapy schema). This type is built to represent actions performed by a provider for a client.
By using Service schema, you tell search engines that you offer a specific treatment, who performs it, and who it is for. You must link the service directly to your clinic by using the provider property.
Here is how you structure a Service block for a treatment page:
name: The name of the treatment, such as "Microneedling."serviceType: The category of the service.description: A brief summary of what the treatment entails.provider: An object referencing yourMedicalBusinessentity using its@id.areaServed: The cities or regions where patients can receive this treatment.
Linking your treatments to your physical location creates a connected entity graph. Google learns that your Austin clinic provides microneedling, which helps your Austin location page rank when searchers look for microneedling in that city.
Want a website that turns visitors into customers, not just compliments?
Book a 15-min introFAQ schema for capturing patient queries
Before booking a medical or cosmetic procedure, patients have questions. They want to know if the treatment hurts, how long the recovery takes, and when they will see results.
Answering these questions on your treatment pages is a proven way to increase conversion rates. It is also an excellent SEO opportunity. By marking up these questions with FAQPage schema, you make your content accessible to search engines in a structured format.
Although Google has reduced the frequency of FAQ rich results in traditional search, structured FAQs have become critical for generative search engines. AI engines like ChatGPT and Perplexity frequently crawl and extract structured FAQ markup to answer users' direct prompts.
When you write FAQ schema, make sure the questions and answers match the visible text on the page exactly. Do not use the schema to hide keywords or display text that users cannot see.
Keep your answers direct and self-contained. A good answer is one to three sentences long, defines the terms clearly, and provides a direct response. If a patient asks "How long does Botox last?", your answer should state "Botox results typically last between three and four months" before explaining the variables.
To avoid validation issues, make sure every question has a corresponding answer, and do not nest other schema types inside the FAQ block unless necessary. You can check the health of your schema markup by reading about common JSON-LD errors.
Handle reviews and ratings with extreme care
Google allows businesses to display star ratings in search results using the aggregateRating property. This is a powerful conversion booster because stars draw the eye and establish trust before a visitor even clicks your link.
However, Google enforces strict guidelines for reviews on local business and medical websites. You can only use aggregateRating if the reviews are genuine, collected directly on your website, and not imported from third-party sites like Google Reviews or Yelp.
Importing Google Reviews into your schema markup is a violation of Google's guidelines. Google already has those reviews in its system; it does not want you to duplicate them on your domain. If you do this, you risk receiving a structured data manual action, which will strip all rich results from your site.
If you have a system for collecting authentic reviews from patients on your own website, you can display them using the Review and aggregateRating properties.
If you do not collect reviews directly on your site, skip this schema block. It is far better to have no star ratings in search results than to have your site penalized for spammy schema.
Maintain a single consistent Organization entity sitewide
If your clinic has multiple locations, you must structure your schema to reflect this hierarchy. You should not define a brand-new, independent Organization entity for every location.
Instead, define one master Organization entity that represents your overall brand. Give this entity a unique @id, such as https://yourclinic.com/#organization.
Then, on each individual location page, define a separate MedicalBusiness entity. Link each location back to the parent organization using the parentOrganization property, referencing the master organization's @id.
This setup tells Google that you are a single brand with multiple physical clinics. It prevents duplicate entity conflicts and allows search authority to flow naturally between your main brand site and your local pages.
By following this tight, clean structure, you ensure your clinic website communicates effectively with search engines. You do not need a complicated code base; you just need to answer the location and service questions with absolute consistency.
For more information on structuring your website for maximum visibility, read the guidelines in Google's structured data documentation.