Schema markup appears in dozens of agency posts about AI search, often framed as one of the primary levers for getting cited in AI Overviews. The framing is plausible, structured data does help search systems understand content, but the degree of influence is routinely overstated. This article is a precise account of what schema actually does, what it does not do, and how to implement it correctly for a medspa without building false expectations.
It is part of the AI Search Visibility for Medspas pillar guide. The pillar covers the full picture; this article goes deep on schema specifically.
What Schema Markup Is
Schema markup is structured data, typically JSON-LD code in a page's <head>, that describes the content of a page in a vocabulary search engines understand. It uses the Schema.org vocabulary, which Google, Bing, and other search systems jointly developed and continue to maintain.
The value is precision. A page about Botox injections contains text about the procedure, the provider, the price, and patient questions. Schema markup labels that text: this block of text is a price range for a specific service; this question-and-answer pair is an FAQ item; this page represents a medical business at a specific address. Without schema, a search system must infer those labels from context. With schema, the inferences are replaced by explicit declarations.
What Schema Markup Is Not
Schema is not a ranking signal in the traditional sense. Google's John Mueller has stated repeatedly that structured data does not directly improve rankings. Google's own Search Central documentation notes that structured data makes content eligible for certain rich results features, but eligibility is not the same as guaranteed display, and neither eligibility nor display translates directly to higher rankings or more AI citations.
This is an important distinction for medspa operators evaluating where to invest time. Schema is worth implementing correctly, the precision benefit is real, but it is the last layer of optimization, not the first. A medspa with accurate, helpful treatment content, a well-maintained Google Business Profile, and credible backlinks will outperform a clinic that invested primarily in schema markup while neglecting those foundations.
Google's guidance, reviewed August 20, 2026: "Structured data is a standardized format for providing information about a page and classifying the page content… Google uses structured data that it finds on the web to understand the content of the page, as well as to collect information about the web and the world in general." It is a tool for clarity, not a ranking mechanism.
Schema Types That Matter for Medspas
LocalBusiness / MedicalBusiness
This is the foundational schema type for any medspa. It declares the clinic's name, address, phone number, website, geo-coordinates, hours of operation, and business type in machine-readable form. It should live on the homepage and, if you have a dedicated contact page, there as well.
Key properties to include: name, address (with all sub-properties: streetAddress, addressLocality, addressRegion, postalCode), telephone, url, geo (latitude and longitude), openingHoursSpecification, image, and sameAs (links to your Google Business Profile, Yelp, Healthgrades, and other authoritative profiles).
The most common error: The name, address, and telephone in the schema do not match what is visible in the page footer or what appears in the Google Business Profile. All three must be identical.
Service / MedicalProcedure
Apply Service or MedicalProcedure schema to each treatment page. This tells search systems that the page is about a specific offering, who provides it, what it costs, and what the procedure involves. For medspas, Service is the more flexible type; MedicalProcedure is appropriate for FDA-cleared or clinically defined procedures with formal names.
Key properties: name (the exact treatment name), description (a concise summary), provider (your clinic's LocalBusiness schema), offers (with price or priceRange and priceCurrency), and areaServed (your service city or region).
Practical note: If you do not publish pricing on your pages, you can still implement Service schema without the offers property. A partial schema that is accurate is more useful than a complete schema that contains placeholder or inaccurate data.
FAQPage
FAQPage schema marks up question-and-answer pairs so search systems can extract them as discrete units. It is the schema type most directly associated with AI Overview citation patterns, because AI synthesis systems frequently pull question-answer pairs verbatim or near-verbatim from indexed pages.
Critical rule: The question and answer text in the JSON-LD must match the visible text on the page exactly, not approximately, not paraphrased. Google's guidelines treat discrepancies as potentially manipulative. The cleanest approach is to generate both the visible HTML and the JSON-LD programmatically from the same data object, so drift is impossible.
Scope: FAQPage schema is appropriate for pages with genuine frequently-asked questions, not for content that has been artificially restructured as questions to gain a rich result. Apply it where the Q&A format genuinely serves the reader.
BreadcrumbList
Breadcrumb schema describes the hierarchical path to a page and enables breadcrumb display in search results. For medspas with treatment categories (e.g., Home > Skin Treatments > Sofwave), this schema makes site structure explicit to search systems. It is low-effort to implement and helps with crawl efficiency on larger sites.
Article / BlogPosting
Apply Article or BlogPosting schema to editorial content, this guide included. Key properties are headline, datePublished, dateModified, author, and publisher. The dateModified property is particularly useful for AI systems evaluating content freshness; update it every time you materially revise a page.
Implementation: The Technically Correct Approach
JSON-LD is the recommended format. Embed it in a <script type="application/ld+json"> block in the page's <head>. This approach keeps structured data separate from the visible HTML, making it easier to maintain and validate.
Validation Before Publishing
Run every new or updated schema through both of these tools before the page goes live:
- Google Rich Results Test (
search.google.com/test/rich-results): Shows which rich result types the page is eligible for and flags errors in required or recommended properties. - Schema Markup Validator (
validator.schema.org): Validates against the Schema.org specification and catches property names or type errors the Rich Results Test may not surface.
After publishing, check Google Search Console's Enhancements section 1–2 weeks later to confirm there are no new structured data errors across the site.
CMS-Specific Notes
- WordPress: Plugins such as Rank Math and Yoast SEO handle LocalBusiness and FAQPage schema through their UIs without code editing. Review their output with the Rich Results Test; plugin-generated schema is occasionally missing required properties for medical business types.
- Webflow: Add JSON-LD via the page's custom code head section. Use Webflow CMS collections to generate schema dynamically for treatment pages rather than hand-coding each one.
- Squarespace: LocalBusiness schema is partially auto-generated from business settings. FAQPage and Service schema require custom code injection in the page settings' code injection section.
- Framer / custom builds: Implement JSON-LD via the framework's head component or a metadata API. Confirm that server-side rendering is delivering the schema in the initial HTML response, not injecting it after JavaScript loads.
Common Schema Mistakes on Medspa Sites
| Mistake | Why It Matters | Fix |
|---|---|---|
| NAP in schema differs from GBP or page text | Creates entity ambiguity; search systems may trust neither source | Audit all three and make them identical before publishing |
| FAQPage schema text differs from visible FAQ text | Treated as manipulative; rich result may be suppressed | Generate both from a single data source |
| Service schema with placeholder pricing ("Call for pricing") | Provides no useful signal; may be ignored | Use a genuine price range or omit the offers property |
| Schema injected client-side only | Googlebot may not execute JavaScript and may miss the markup | Confirm schema is in the server-rendered HTML response |
| Multiple conflicting LocalBusiness blocks on the same page | Creates ambiguity about which data is authoritative | One LocalBusiness block per page; use sameAs for profile links |
We review structured data alongside visible content in our medspa AI visibility work. Markup should describe verified facts, not introduce claims the page cannot support.

