How to Add AI-Friendly Schema to Your Site

Updated May 2026 • 10 min read

An Irmo office worker with growing low-back pain from desk work and post-pregnancy recovery opens ChatGPT and asks, "I need a chiropractor in Irmo SC for chronic low-back pain — postpartum considerations, gentle adjustment styles (not just instrument-assisted), available Tuesday or Thursday afternoon, accepts BCBS. Independent practice preferred." Two practices appear in the answer. Both have implemented schema on their websites. The third Irmo chiropractor — with comparable actual clinical capability — is not mentioned, in significant part because their website lacks the schema implementation that lets the AI confidently match all four query attributes.

This article is the step-by-step implementation guide. You'll get JSON-LD templates you can adapt, validation steps, and the common pitfalls to avoid.

Before You Start: Prerequisites

Before adding schema, ensure:

• You have access to edit your website's HTML or your CMS's "custom HTML / scripts" feature.
• You know which CMS or platform you're on (WordPress, Squarespace, Webflow, custom build, etc.) — implementation method varies.
• You have your canonical business information ready: legal name, address, phone, hours, services, named providers with credentials.
• You bookmark the Rich Results Test: https://search.google.com/test/rich-results

Step 1: Choose Your Primary Type

Identify the most-specific applicable schema.org type for your business. For a chiropractic practice, that's Chiropractic (a MedicalBusiness subtype).

Common subtypes by category:

• Chiropractic, Dentist, Optometric, Physician, Pediatric, etc. — for healthcare.
• Attorney, LegalService — for legal.
• FinancialService, AccountingService — for financial.
• HVACBusiness, Plumber, Electrician, PestControlService, HousePainter — for trades.
• HealthClub, SportsActivityLocation — for fitness.
• HairSalon, BeautySalon — for personal services.
• Restaurant, CafeOrCoffeeShop — for hospitality.
• RealEstateAgent — for real estate.

If no exact match exists, use the closest LocalBusiness subtype available.

Step 2: Draft the Homepage Schema

This is the foundation. For an Irmo chiropractic practice, the homepage JSON-LD block:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Chiropractic",
  "name": "Reid Chiropractic Care",
  "image": "https://reidchiropractic.com/img/clinic-front.jpg",
  "url": "https://reidchiropractic.com",
  "telephone": "+18035550199",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "5821 Lake Murray Boulevard",
    "addressLocality": "Irmo",
    "addressRegion": "SC",
    "postalCode": "29063",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 34.0856,
    "longitude": -81.1858
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Wednesday", "Friday"],
      "opens": "08:00",
      "closes": "17:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Tuesday", "Thursday"],
      "opens": "09:00",
      "closes": "18:00"
    }
  ],
  "priceRange": "$$",
  "areaServed": ["Irmo", "Chapin", "Ballentine", "Columbia"],
  "medicalSpecialty": "Chiropractic",
  "employee": [
    {
      "@type": "Person",
      "@id": "https://reidchiropractic.com/about#drsarahreid",
      "name": "Dr. Sarah Reid, DC",
      "jobTitle": "Owner / Chiropractor"
    }
  ],
  "sameAs": [
    "https://www.google.com/business/your-profile-url",
    "https://www.facebook.com/reidchiropractic"
  ]
}
</script>

Replace the placeholder values with your actual business information. Keep all field names as written — they're schema.org keywords.

Step 3: Build Each Provider's Person Schema

On each provider's bio page, add a more detailed Person schema:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://reidchiropractic.com/about#drsarahreid",
  "name": "Dr. Sarah Reid, DC",
  "jobTitle": "Chiropractor (Doctor of Chiropractic)",
  "image": "https://reidchiropractic.com/img/dr-sarah-reid.jpg",
  "worksFor": {
    "@type": "Chiropractic",
    "name": "Reid Chiropractic Care"
  },
  "alumniOf": {
    "@type": "EducationalOrganization",
    "name": "Sherman College of Chiropractic",
    "url": "https://www.sherman.edu"
  },
  "hasCredential": [
    {
      "@type": "EducationalOccupationalCredential",
      "credentialCategory": "license",
      "name": "South Carolina Chiropractic License",
      "recognizedBy": {
        "@type": "Organization",
        "name": "South Carolina Board of Chiropractic Examiners"
      }
    },
    {
      "@type": "EducationalOccupationalCredential",
      "credentialCategory": "certification",
      "name": "Webster Technique Certification",
      "recognizedBy": {
        "@type": "Organization",
        "name": "International Chiropractic Pediatric Association"
      }
    }
  ],
  "memberOf": [
    {"@type": "Organization", "name": "American Chiropractic Association"},
    {"@type": "Organization", "name": "South Carolina Chiropractic Association"}
  ],
  "knowsAbout": [
    "Postpartum chiropractic care",
    "Webster Technique (prenatal)",
    "Activator method",
    "Diversified technique",
    "Sports injury rehabilitation",
    "Low back pain management"
  ]
}
</script>

Repeat for each provider. The @id field allows cross-referencing — note the homepage employee array references this Person's @id.

Step 4: Add Service Schema to Each Service Page

For each major service page (e.g., "/services/low-back-pain", "/services/prenatal-chiropractic", "/services/auto-injury"):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "serviceType": "Chiropractic care for low back pain",
  "name": "Low Back Pain Treatment",
  "description": "Comprehensive evaluation and chiropractic care for acute and chronic low back pain, including diversified-technique adjustments, soft-tissue therapy, and rehabilitation exercises.",
  "provider": {
    "@type": "Chiropractic",
    "name": "Reid Chiropractic Care"
  },
  "areaServed": ["Irmo", "Chapin", "Ballentine", "Columbia"],
  "offers": {
    "@type": "Offer",
    "priceCurrency": "USD",
    "priceSpecification": {
      "@type": "PriceSpecification",
      "minPrice": "65",
      "maxPrice": "185",
      "description": "Initial evaluation $185, follow-up visits $65-$95"
    }
  }
}
</script>

Adapt for each service. The pricing block is optional but produces strong AI-citation lift when populated honestly.

Step 5: Add FAQPage Schema

On your FAQ page (or FAQ sections of other pages):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does a typical chiropractic visit take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Initial new-patient visits at our Irmo practice take 45-60 minutes, including evaluation, x-ray if needed, and the first adjustment. Follow-up visits typically run 15-25 minutes — most of that time is the actual adjustment and any soft-tissue work. We schedule realistically so you don't sit in the waiting room."
      }
    },
    {
      "@type": "Question",
      "name": "Do you accept BCBS dental insurance?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, we are in-network with BCBS of South Carolina, Medicare (most plans), and several other major insurers. Initial-visit out-of-pocket typically ranges $40-$120 depending on plan and whether x-rays are needed. We verify benefits before your visit."
      }
    }
  ]
}
</script>

Add 10-20 Q&A pairs covering the questions customers actually ask.

Step 6: Add BlogPosting Schema to Blog Content

On each blog post:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Postpartum Low Back Pain: When to See a Chiropractor",
  "datePublished": "2026-04-15",
  "dateModified": "2026-05-13",
  "author": {
    "@type": "Person",
    "@id": "https://reidchiropractic.com/about#drsarahreid"
  },
  "publisher": {
    "@type": "Chiropractic",
    "name": "Reid Chiropractic Care"
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://reidchiropractic.com/blog/postpartum-low-back-pain"
  },
  "image": "https://reidchiropractic.com/img/blog/postpartum-back-pain.jpg"
}
</script>

Adapt for each post. The author reference uses @id to point back to the Person schema you set up earlier.

Step 7: Implement the Schema in Your CMS

For WordPress

• Use a plugin like Yoast SEO or RankMath for basic schema, then add custom JSON-LD via a "Custom HTML" block on each page.
• Or use a dedicated schema plugin like Schema Pro for templated implementation.
• Or hand-add JSON-LD in the page editor with the appropriate block.

For Squarespace

• Use Code Injection (Settings → Advanced → Code Injection) to add site-wide schema in the header.
• Use Code Blocks on individual pages for page-specific schema.

For Webflow

• Site-wide schema in Project Settings → Custom Code → Head Code.
• Page-specific schema in Page Settings → Custom Code → Inside <head>.

For custom builds

• Add JSON-LD blocks directly in the HTML, typically in the <head> section.
• Use server-side templates to generate dynamic schema where appropriate (e.g., service pages that pull from a database).

Step 8: Validate Each Implementation

1. Open the Rich Results Test.
2. Paste the URL of the page you just schemed.
3. Wait for the test to complete.
4. Check that the expected schema type appears in the "Detected items" panel.
5. Review any warnings or errors.
6. Fix issues and re-test.

Common warnings:

• Missing recommended fields — usually safe to ignore unless the recommendation is high-value.
• Mismatched content/schema — fix immediately.
• Invalid value formats (dates, prices, URLs) — fix the format.

Common Pitfalls and How to Avoid Them

Pitfall 1: Invalid JSON syntax

JSON requires precise syntax — proper quote marks, commas between properties, curly braces matched, brackets matched. A single missing comma breaks the entire block. Use a JSON validator (e.g., jsonlint.com) if you suspect syntax issues.

Pitfall 2: Smart quotes from word processors

Pasting from Word or Google Docs can introduce "smart quotes" that JSON doesn't accept. Always use straight ASCII quotes ".

Pitfall 3: Schema-content mismatch

Schema says priceRange $$. Service page says "starting at $45 — clearly $." The AI sees inconsistency. Match schema to visible content.

Pitfall 4: Multiple schemas with conflicting information

Two different LocalBusiness blocks on the same page with different hours or addresses. Choose one canonical block per page.

Pitfall 5: Stale schema after content changes

You added a new service to the site but didn't add Service schema. You raised prices but didn't update the offer block. Treat schema as a content-management discipline.

Pitfall 6: Over-implementation that doesn't apply

Adding schema for content you don't actually have (Recipe schema on a non-cooking site, JobPosting when not hiring) reads as low-quality. Implement only what genuinely applies.

The Maintenance Discipline

Once implemented:

Monthly

• When content changes, update corresponding schema fields.
• When new pages are added, add appropriate schema at the same time.

Quarterly

• Validate all schemed pages.
• Check that schema content matches current visible content.
• Review any new schema warnings.

Annually

• Comprehensive schema audit.
• Check for new schema.org types relevant to your category.
• Refresh credentials, employee arrays, and reference URLs.

The Bottom Line

Adding AI-friendly schema is a 15-30 hour project that produces compounding citation lift for years. The Irmo chiropractic practice that completes the 8-step implementation gets named when the office worker with low-back pain asks ChatGPT. The practice with the same clinical capability but partial or no schema does not — and the citation differential is large enough to justify the implementation effort by itself.