Different agents may read HTML, rendered pages, images, search results, or tool responses. Schema.org structured data adds explicit labels to business information; it is useful to evaluate alongside clear visible content, not a prerequisite for every agent to understand a page.
In this guide, you will learn exactly how Schema.org markup makes your business visible and actionable to AI agents like ChatGPT, Claude, and Gemini -- and how to choose, add, and validate markup for your site's actual content.

What Schema.org Actually Means for AI Agents
Schema.org is a collaborative vocabulary of structured data types maintained by Google, Microsoft, Yahoo, and Yandex. Originally created for search engine rich results (those enhanced listings with stars, prices, and FAQs), its documented vocabulary can describe entities and relationships for compatible consumers.

| Without Schema.org | With Schema.org |
|---|---|
| AI reads: 'Open 9am-5pm Monday-Friday' | AI reads: {openingHours: 'Mo-Fr 09:00-17:00'} |
| A reader infers business type from copy | Markup explicitly labels the business type |
| Pricing appears in visible text | Offer markup can label price and currency |
| Address appears in visible text | PostalAddress can label address components |
| Matching depends on the consumer | Structured fields provide another input to matching |
Markup is a representation of your claims, not independent verification. Keep it consistent with visible information and test the consumer you intend to support.
The 7 Essential Schema.org Types for AI Agent Visibility

1. LocalBusiness (or Organization)
This is the foundation of your AI visibility. Every business website should have this on the homepage. It tells AI agents your business name, type, address, phone, hours, and description.
| Field | Example | AI Agent Use |
|---|---|---|
| @type | Dentist, DaySpa, Restaurant | Categorizes your business for search queries |
| name | "Serenity Spa NYC" | Matches to user's natural language request |
| address | {streetAddress, city, state} | Location-based service discovery |
| telephone | Your main phone number | Direct contact fallback |
| openingHours | "Mo-Sa 09:00-20:00" | Availability checking for booking |
| priceRange | "$$" | Budget filtering for recommendations |
| description | "Premium wellness center..." | Understanding service scope |
2. Service
List each service you offer with name, description, price, and duration. AI agents use this to match specific user requests ("deep tissue massage within my budget") to your offerings.
3. Product
For businesses selling products, Product schema includes name, price, availability, brand, and reviews. AI shopping agents rely heavily on Product schema for comparison shopping.
4. FAQPage
FAQPage markup describes visible question-and-answer content. It does not guarantee a Google rich result or an AI citation; check the search platform's current eligibility rules before expecting either.
5. Review and AggregateRating
Review and AggregateRating can describe genuine, attributable reviews and ratings. Consumer behavior varies, and markup does not prove authenticity or guarantee recommendation.
6. Event
Event markup can describe an event's date, location, and offers. Booking still requires a separately configured transaction system and authorization; the markup itself does not reserve a place.
7. BreadcrumbList
BreadcrumbList describes a page's place in a site hierarchy. Test whether the intended consumer uses it rather than assuming an extraction-accuracy improvement.
How to Implement Schema.org JSON-LD (Step by Step)

Step 1: Choose Your Primary Schema Type
Start with the most specific type that matches your business. Schema.org lists types you can evaluate, including Dentist, DaySpa, HealthClub, Restaurant, LegalService, RealEstateAgent, FinancialService, EducationalOrganization. If none fits perfectly, use the generic LocalBusiness type.
Step 2: Write Your JSON-LD Block
JSON-LD (JavaScript Object Notation for Linked Data) is the recommended format for Schema.org. It goes in a script tag in your page's head section. The key fields to include are: @context, @type, name, description, address, telephone, url, openingHours, priceRange, and sameAs (social links).
Step 3: Add Service and Product Schemas
After your primary business schema, add individual Service or Product schemas for each offering. Include name, description, provider (referencing your business), price or priceRange, and any category information. The more specific your service descriptions, the better AI agents can match them to user queries.
Step 4: Validate Your Markup
Use Google's Rich Results Test or Schema.org's validator to check your markup for errors. Common mistakes include missing required fields, incorrect data types (string instead of number), and invalid URLs. After validation, run Dashform's AX Audit to inspect its current Findings. An AX Score reflects the audit's checks, not measured AI visibility or recommendation frequency.
5 Common Schema.org Mistakes That Hurt AI Visibility
| Mistake | Why It Hurts | Fix |
|---|---|---|
| Unsupported or malformed format | Consumer support varies | Validate the format your intended consumer supports |
| Missing @type or @context | AI agents cannot identify what the data represents | Always include @context and specific @type |
| Overly generic type | It omits a useful classification | Use the most specific accurate type |
| Missing location details | The data omits relevant service context | Include accurate applicable address or service-area information |
| Outdated hours or pricing | Agents recommend you for wrong times/budgets | Audit and update Schema data quarterly |
Advanced: Schema.org for AI Agent Transactions
Structured data can describe information and actions, but performing a transaction requires an actual supported interface. Consider these separate pieces:
Combine Schema.org with llms.txt
Your llms.txt file provides a narrative summary while Schema.org provides structured data. llms.txt is an optional proposal with varying support. Neither file guarantees discovery or supplies a transaction system.
Connect Schema.org to MCP Endpoints
Dashform provides public form information and a form MCP endpoint. Test the actual discovery and fill path with a compatible client; booking and payments have separate requirements.
Frequently Asked Questions
Do I need Schema.org if I already have good SEO?
Yes. Traditional SEO (meta tags, title tags, alt text) is designed for search engine crawlers. AI agents use different parsing methods and prioritize structured data formats like JSON-LD. Schema.org is the bridge between SEO and AI visibility.
How much Schema.org markup is enough?
At minimum, add LocalBusiness schema to your homepage and Service/Product schema to your offering pages. Choose types that accurately describe the visible business information, services, and other supported content; no type count guarantees AI visibility. You do not need to schema-mark every page.
Can AI agents read Schema.org from any website platform?
Yes. JSON-LD Schema.org works on WordPress, Shopify, Wix, Squarespace, custom builds, and every other platform. It is a standard HTML script tag that any platform supports. Many platforms also have plugins that generate Schema.org automatically.
How do I test if AI agents can read my Schema.org?
The fastest way is to run Dashform's free AX Audit. It specifically checks for Schema.org presence, completeness, and validity as part of its Structured Data dimension. You will see exactly which schema types are detected and which are missing.
Does Schema.org help with AI-generated answers and citations?
It can provide explicit information to consumers that read it, but this guide establishes no citation-rate lift. Test relevant queries and verify that any cited details match your current business information.
Start Adding Schema.org Today
Schema.org is one way to label business information explicitly. Start with LocalBusiness schema on your homepage, add Service schemas for your offerings, and validate with AX Audit. For businesses ready to go beyond visibility into AI-powered transactions, Dashform provides form MCP access and configurable Lead Scoring. Review the published form, configure criteria and Destinations, and test the intended workflow.







