// SERVICES
Schema & Structured Data
Schema markup is how you communicate directly with search engines and AI platforms. Without it, Google and AI systems have to guess what your content means, who your organization is, what credentials you hold, and how your pages relate to each other. With proper structured data, you’re telling them explicitly — and the difference in outcomes is measurable.
Sites with full schema hierarchy using @graph and @id entity relationships achieve an 81% rich result appearance rate compared to 42% for standalone schema. AI citation rates jump from 31% to 73% when schema establishes verified entity relationships with credential markup. These aren’t theoretical improvements — they’re the documented outcomes of implementing schema the way we do it.
Most agencies treat schema as a checkbox: add some basic Organization markup, maybe an FAQ schema, and move on. We treat it as strategic infrastructure. Every entity on your site — your organization, your locations, your services, your people, your content — is connected through persistent @id references that create a verified entity network. Google doesn’t just know what’s on each page. It knows how everything relates to everything else. And that changes how it ranks you, how it displays you, and whether AI systems trust you enough to cite you.
@graph/@id Entity Architecture
Our schema methodology is built on the @graph structure with persistent @id linking — the approach Google’s own documentation recommends for complex sites. Every entity on your site gets a consistent @id that’s referenced identically across all pages. Your Organization entity at https://example.com/#organization is the same entity on your homepage, your about page, your service pages, and your location pages. This consistency is what allows Google to build a verified knowledge graph entry for your business.
We implement this through Rank Math’s custom schema editor as the single authoritative source — never through competing header/footer code plugins that create duplicate entities. The result is a clean, unified schema architecture where every page contributes to the same entity verification rather than fragmenting it.
Healthcare & YMYL Schema Specialization
Healthcare organizations face unique schema requirements. We implement MedicalBusiness typing (not generic Organization) with hasCredential properties for Joint Commission accreditation, state licensing, CARF certification, and other credentials that establish trust. Location pages use MedicalClinic with areaServed properties. Service pages use MedicalTherapy or related types with evidence-based treatment descriptions.
For multi-location treatment organizations, we build interconnected location entities where each facility maintains its own MedicalClinic @id while connecting back to the parent MedicalBusiness entity. Each location gets its own address, phone, geo-coordinates, and credential markup while inheriting organizational authority from the parent entity.
Content-Specific Schema Patterns
Different content types require different schema patterns, and choosing the wrong one actively hurts performance. We follow a decision matrix based on actual content structure: single-focus pages (one video, one article, one service) use mainEntity to establish that content as the page’s primary purpose. Multi-content pages (press centers, resource libraries) use CollectionPage with hasPart to properly represent multiple content items without incorrectly elevating one above the others.
Common implementations include VideoObject for facility tours and treatment explainers (linked via hasPart, never mainEntity, on multi-content pages), FAQPage schema for treatment FAQ sections, Service schema for individual service pages, and BreadcrumbList auto-generated by Rank Math — never duplicated in custom schema.
Schema Audit & Cleanup
Before we build, we clean. Most sites we onboard have competing schema implementations: plugin-injected markup in the header conflicting with theme-generated schema in the footer conflicting with manually added JSON-LD in post content. We audit every schema source, document the conflicts, delete all problematic implementations, and rebuild from scratch using Rank Math as the single authoritative source.
For one treatment center client, we identified and deleted six separate conflicting schema snippets that were creating duplicate Organization entities, citing competitor URLs in knowsAbout properties, using incorrect typing, and missing @graph structure entirely. After cleanup and rebuild, the site’s rich result eligibility increased significantly and AI citation accuracy improved because search engines could finally identify a single, verified entity.
// CONTACT
Get a free quote or contact us!
How schema directly impacts AI citation rates.
AI systems like ChatGPT, Google AI Overviews, and Perplexity use structured data as a primary signal for citation decisions. When an AI platform encounters a query about addiction treatment in Nashville, it doesn’t just evaluate content quality — it evaluates source authority. Schema is how you prove that authority to machines.
Here’s the decision chain AI systems follow: First, they discover content on your page. Then they check for parent WebPage schema to understand context. Then they trace @id references to find your Organization entity. Then they verify credentials through hasCredential properties. If that chain is intact and connects to a verified MedicalBusiness with documented accreditation, citation confidence is high. If any link in that chain is broken — orphaned entities, missing @id references, generic Organization typing instead of MedicalBusiness — citation confidence drops.
This is why we build schema as a connected system rather than isolated snippets. Every page contributes to entity verification. Every @id reference reinforces authority. Every credential property builds trust. The compounding effect across a full site is what separates organizations that AI platforms consistently cite from those they consistently skip.
Our implementation workflow: audit, clean, build, validate.
Phase 1: Audit Existing Schema
We examine every source of structured data on your site: Rank Math output, theme-generated schema, plugin-injected markup, and manually added JSON-LD. We document every entity, identify conflicts and duplications, and map the current state against what’s needed.
Phase 2: Clean Problematic Implementations
We delete competing schema sources, remove header/footer code plugin injections, and eliminate theme-generated markup that conflicts with our architecture. Rank Math becomes the single authoritative source.
Phase 3: Build Connected Entity System
We implement the full @graph architecture with persistent @id references: Organization entity (consistent across all pages), WebSite entity, page-specific WebPage entities with appropriate typing (AboutPage, CollectionPage, ContactPage), content entities (VideoObject, Service, FAQPage), and relationship properties (mainEntity, hasPart, isPartOf, about, publisher).
Phase 4: Validate and Monitor
Every implementation is validated against Google Rich Results Test, Schema.org Validator, and Google Search Console. We monitor for structured data errors post-launch and verify rich result appearances over the following 2–4 weeks. Healthcare schemas receive additional validation for credential markup and MedicalBusiness typing compliance.
// FAQS
Some frequently asked questions.
Having schema and having effective schema are very different things. Most sites we audit have markup that’s technically present but strategically broken: standalone snippets without @graph structure, inconsistent @id references creating multiple competing entities, generic Organization typing instead of industry-specific types like MedicalBusiness, and missing relationship properties that leave entities orphaned. The difference between 42% and 81% rich result eligibility comes down to how schema is architectured, not just whether it exists.
SEO plugins generate baseline schema automatically — basic WebPage, Organization, and BreadcrumbList markup. This is a starting point, not a complete solution. Plugins don’t create connected @graph architectures with @id references, don’t implement healthcare-specific typing like MedicalBusiness with hasCredential, don’t build CollectionPage schemas for multi-content pages, and don’t optimize for AI citation patterns. We use Rank Math as the implementation platform but build custom schema through its advanced editor that goes far beyond what the plugin generates automatically.
Schema doesn’t directly boost rankings in the traditional keyword sense, but it significantly impacts visibility through two mechanisms. First, rich results: proper schema enables enhanced search appearances (FAQ dropdowns, video carousels, star ratings, breadcrumbs) that dramatically increase click-through rates — 40–150% CTR improvement is typical. Second, AI citation: schema with verified entity relationships increases AI citation rates from 31% to 73%, which drives traffic from ChatGPT, AI Overviews, and Perplexity. Both of these translate to more qualified traffic without changing your keyword rankings.
For healthcare clients, we typically implement MedicalBusiness (parent organization) with hasCredential for Joint Commission, state licensing, and CARF accreditation. MedicalClinic for individual facility locations with geo-coordinates and areaServed. Service schema for treatment programs (residential, detox, outpatient, dual diagnosis). VideoObject for treatment overview videos and facility tours. CollectionPage for press and resource centers. FAQPage for treatment FAQ sections. Person schema for medical directors and clinical leadership. And BreadcrumbList for site-wide navigation context. All connected through @graph with persistent @id references.