Advanced Schema Markup: Beyond Basic JSON-LD for AI Visibility

If you've already added basic LocalBusiness JSON-LD to your website, you've taken the most important first step for AI visibility. But basic schema only scratches the surface of what's possible. Advanced schema markup techniques can dramatically expand the range of AI queries your business matches and increase the depth of information AI can cite about you.

This guide covers the advanced schema patterns that produce measurable improvements in AI visibility scores.

Nested Entities: Services Within Your Business

Basic schema lists your business as a single entity. Advanced schema describes the hierarchy of entities within your business — each service, each team member, each location — as connected, structured data.

For example, instead of a flat list of services in your description, you can use the hasOfferCatalog property to define each service as a separate entity with its own description, price range, and availability:

"hasOfferCatalog": {
  "@type": "OfferCatalog",
  "name": "Plumbing Services",
  "itemListElement": [
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Emergency Pipe Repair",
        "description": "24/7 emergency pipe repair for burst pipes, leaks, and water damage. Average response time: 45 minutes within San Jose.",
        "areaServed": { "@type": "City", "name": "San Jose" },
        "provider": { "@type": "Plumber", "name": "Bay Area Plumbing Co." }
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Drain Cleaning",
        "description": "Professional drain cleaning for kitchen, bathroom, and sewer lines. Video camera inspection included.",
        "areaServed": { "@type": "City", "name": "San Jose" }
      }
    }
  ]
}

This nested structure means that when someone asks AI "Who does emergency pipe repair in San Jose?" your business can be matched specifically to that service — not just to "plumbing" generally. Each service becomes a distinct data point AI can reference.

FAQ Schema: Pre-Loading AI with Answers

FAQPage schema is one of the most powerful tools for AI visibility because it directly maps to how people use AI: they ask questions, and AI provides answers. When your website contains FAQ schema, you're giving AI pre-formatted question-answer pairs it can cite directly.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much does emergency plumbing cost in San Jose?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Emergency plumbing service calls in San Jose typically start at $150 for the visit, with most residential repairs ranging from $200-$800. Bay Area Plumbing Co. provides upfront pricing before starting any work, with no overtime charges for evenings and weekends."
      }
    },
    {
      "@type": "Question",
      "name": "Do you offer same-day plumbing appointments?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Bay Area Plumbing Co. offers same-day appointments for most plumbing issues, with an average response time of 45 minutes for emergency calls within the San Jose metro area."
      }
    }
  ]
}

The key is writing questions in the exact language customers use — not corporate-sounding questions. "How much does emergency plumbing cost in San Jose?" matches a real query. "What are your service rates?" doesn't.

Aim for 10-15 FAQ entries per page, covering your most common customer questions. Include specific numbers, timeframes, and location references in your answers.

HowTo Schema: Process Transparency

HowTo schema describes a step-by-step process. For service businesses, this is excellent for answering "how does [your service] work?" queries that AI frequently receives.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Get Emergency Plumbing Service in San Jose",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Call or Request Online",
      "text": "Call (408) 555-1234 or submit an online request. Available 24/7, including holidays."
    },
    {
      "@type": "HowToStep",
      "name": "Get a Diagnosis",
      "text": "A licensed plumber arrives within 45 minutes on average and diagnoses the issue. Video camera inspection is included for drain and sewer problems."
    },
    {
      "@type": "HowToStep",
      "name": "Review Upfront Pricing",
      "text": "Receive a written price quote before any work begins. No surprise charges."
    },
    {
      "@type": "HowToStep",
      "name": "Repair Complete",
      "text": "Most emergency repairs are completed in a single visit. All work includes a 1-year warranty."
    }
  ]
}

HowTo schema also earns rich results in traditional Google search, providing dual SEO and GEO benefits.

Industry-Specific Schema Enhancements

Beyond the general patterns above, each industry has schema types with fields that dramatically improve AI matching for industry-specific queries.

Restaurants

Use Restaurant type with servesCuisine, menu (URL to your online menu), acceptsReservations, and hasMenu with individual MenuItem entries for signature dishes. See our full guide for restaurant AI visibility.

Healthcare (Dentists, Therapists)

Use Dentist or MedicalBusiness with medicalSpecialty, availableService (listing each treatment), insuranceAccepted (extremely valuable — "dentist who takes Delta Dental" is a common AI query), and isAcceptingNewPatients.

Legal Services

Use LegalService with knowsAbout (practice areas), relevant certifications, bar admissions, and case type specializations. For law firm AI visibility, practice area specificity is the strongest differentiator.

Home Services

Use Plumber, Electrician, HVACBusiness, or RoofingContractor with hasCredential (license numbers), areaServed with specific cities and neighborhoods, and emergency availability attributes. See our home services guide.

Multi-Page Schema Strategy

Advanced schema implementation isn't just about what you put on your homepage — it's about distributing schema across your entire site strategically.

Homepage: Core LocalBusiness schema with your overall business identity, location, hours, and service catalog overview.

Service pages: Service-specific schema for each major service you offer, with detailed descriptions, pricing, and area served for that specific service.

FAQ page: FAQPage schema with your top 15-20 customer questions.

About page: Organization schema with founding date, team member information, credentials, and awards.

Blog posts: Article schema with author information, publication dates, and topic markup.

This multi-page approach creates a rich web of structured data that gives AI engines detailed information for many different query types — not just "find me a [business type] near me" but also "how much does X cost," "who specializes in Y," and "which Z accepts my insurance."

Validation and Testing

After implementing advanced schema, validate each page using Google's Rich Results Test. But remember that validation only confirms your code is syntactically correct. To verify that your schema is actually improving AI visibility, run a ScanMyGEO scan before and after your changes.

Most businesses see measurable score improvements within 30-60 days of implementing comprehensive schema markup. The combination of basic LocalBusiness JSON-LD plus FAQ, HowTo, and industry-specific schema creates the richest possible data layer for AI engines to draw from.