Answer Engine Optimization

Schema Markup for AI Search: The JSON-LD That Actually Matters

Schema won't force your way into AI answers, and anyone promising that is overselling. What it does is remove ambiguity: who you are, what a page is, and how everything on your site connects.

A web page with structured data braces connected to icons for a person, an organization and a document

For AI search, the structured data that matters most is the markup that identifies who you are and what each page is: Organization or Person (with sameAs links), WebSite, BreadcrumbList, Article or BlogPosting, Service or Product, LocalBusiness where relevant, and FAQPage for genuine question-and-answer sections. Schema doesn't force inclusion in AI answers. It removes ambiguity, connects your pages into one entity and reinforces the signals that make your content trustworthy.

I write structured data by hand for every client site, and I'm careful about what I claim it does. Google states that no special schema is required for AI Overviews or AI Mode. But clean, connected markup consistently helps search engines and AI systems understand a site, and the cost of doing it well is low. This guide covers the markup I actually use, with examples.

What structured data does, and doesn't

Structured data is code, usually JSON-LD in a <script type="application/ld+json"> block, that describes a page using the schema.org vocabulary.

What it does:

  • States explicitly what a page is: an article, a service, a product, a profile.
  • Identifies the entities involved: the author, the business, the place.
  • Connects pages and profiles, so a search engine can tell they all relate to the same business.
  • Makes pages eligible for certain rich results in Google, such as breadcrumbs, product details and review snippets for eligible content.

What it doesn't do:

  • It doesn't rank pages on its own.
  • It doesn't guarantee a rich result, an AI Overview citation or a ChatGPT mention.
  • It doesn't compensate for thin or unclear content.

Think of it as labeling. Good labels help a well-organized warehouse. They don't fix an empty one.

AI systems combine information from many sources to describe entities and answer questions. Structured data helps in three ways:

  1. Entity resolution. Organization or Person markup with sameAs links tells systems that your website, LinkedIn and other profiles describe one entity. This is the backbone of entity SEO.
  2. Content typing. Knowing a block is a question and its answer, or that a page is a service offered in a specific area, makes retrieval and extraction more reliable.
  3. Trust context. Author, publisher, dates and relationships give systems the context they use to judge whether content is credible and current.

Format and placement rules

  • Use JSON-LD. Google recommends it, and it's the easiest to maintain because it's separate from your HTML.
  • Put it in the page it describes. Each page carries markup for its own content.
  • Use an @graph to group several related items in one script.
  • Use stable @id values, such as https://example.com/#organization, and reference them from other items instead of repeating details.
  • Match the visible content. Every fact in the markup should be visible on the page. Google's guidelines treat marking up hidden or misleading content as a violation.

The core set for most businesses

1. Organization or Person

This defines the entity behind the site. Businesses use Organization (or a more specific subtype such as ProfessionalService or LocalBusiness). Consultants and personal brands often use Person, sometimes alongside an Organization.

Key properties:

  • name, alternateName, url, logo or image
  • description
  • address (at least city and country)
  • email, telephone
  • sameAs: your official profiles
  • knowsAbout (Person) or areaServed (Organization)

Put this on the homepage with a stable @id, and reference it everywhere else.

2. WebSite

A small block naming the site and its publisher:

{
  "@type": "WebSite",
  "@id": "https://example.com/#website",
  "url": "https://example.com/",
  "name": "Example Studio",
  "publisher": { "@id": "https://example.com/#organization" }
}

3. BreadcrumbList

Breadcrumbs show where a page sits in the site's hierarchy and are still shown as rich results in Google. Add them to every page below the homepage, and make sure they match the visible breadcrumb trail.

{
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Insights", "item": "https://example.com/insights/" },
    { "@type": "ListItem", "position": 3, "name": "Schema Markup for AI Search", "item": "https://example.com/insights/schema-markup/" }
  ]
}

4. Article or BlogPosting

For articles, guides and case studies:

  • headline, description, image
  • datePublished and dateModified, matching visible dates
  • author, referencing your Person @id
  • publisher, referencing your Organization or Person
  • mainEntityOfPage

On my own site, every case study is an Article and every insight is a BlogPosting, all with the same #person entity as author. That consistency ties all the content to one expert.

5. Service

For service pages, Service markup describes what you offer:

{
  "@type": "Service",
  "@id": "https://example.com/services/technical-seo-audit/#service",
  "name": "Technical SEO audit",
  "serviceType": "Technical SEO audit",
  "provider": { "@id": "https://example.com/#organization" },
  "areaServed": [{ "@type": "Country", "name": "Bangladesh" }, { "@type": "Place", "name": "Worldwide" }],
  "url": "https://example.com/services/technical-seo-audit/"
}

Service markup doesn't produce a rich result in Google, but it states clearly what the page is about and who provides it. I also link each Service to the case studies that prove it, using subjectOf.

6. Product

For e-commerce, Product markup with offers (price, currency, availability), brand, sku and genuine reviews can produce rich results with price and rating information. Keep prices and availability in sync with the page; mismatches are a common error in Search Console.

7. LocalBusiness

For businesses serving a local area, LocalBusiness (or a specific subtype such as RoofingContractor or Dentist) adds address, geo-coordinates, opening hours and service area. It should match your Google Business Profile exactly. The local side is covered in the Google Business Profile guide.

8. FAQPage

For genuine question-and-answer sections:

{
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Does blocking GPTBot remove my site from ChatGPT?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "No. GPTBot collects content for training. ChatGPT search uses OAI-SearchBot."
    }
  }]
}

Since 2023, Google shows FAQ rich results mainly for well-known government and health sites, so most businesses won't see the expandable display. I still add FAQPage markup to genuine FAQs because it labels questions and answers unambiguously, which supports the answer-first content approach. Never add it for questions that aren't visible on the page.

Connecting everything with @id

The most powerful and most overlooked technique is referencing. Instead of repeating your business details on every page, define them once on the homepage and point to them:

  • Each Article's author → {"@id": "https://example.com/#person"}
  • Each Service's provider → the same @id
  • The WebSite's publisher → the same @id

Systems that read your pages can then link every article, service and case study to one entity, rather than seeing dozens of disconnected descriptions. On my own site, the homepage defines the Person and ProfessionalService once, and every other page references them.

Schema for case studies and portfolios

Case studies are some of the most citable content a service business has, because they contain specific, first-hand results. I mark them up as Article with:

  • author and publisher referencing the main Person or Organization.
  • about describing the service involved.
  • datePublished and dateModified.
  • associatedMedia pointing to a downloadable PDF version, if there is one.
  • A BreadcrumbList showing the case study's place under the case studies hub.

Then I connect each Service page to its proof with subjectOf, pointing to the case study Article's @id. The result is a small, explicit graph: this person provides this service, and here are the documented projects that show it. A machine reading any one of those pages can follow the connections to the others.

The hub page itself works well as a CollectionPage with an ItemList of the case studies in order.

Keeping schema maintained

Structured data decays like any other content. Prices change, people change roles, profiles get renamed and plugins get updated. A few habits keep it accurate:

  • Generate markup from the same data as the page where possible, so the two can't drift apart. On my own site, the same source file produces both the visible case study and its Article markup.
  • Review sameAs links twice a year and remove any that are dead or no longer yours.
  • Re-validate after every theme, plugin or template change.
  • Update dateModified only when content actually changes.

Markup to be careful with

  • Review and AggregateRating on your own business. Google doesn't show star ratings for reviews that a business publishes about itself on its own site (self-serving reviews for LocalBusiness and Organization). I display client reviews as content but don't mark them up as ratings of my own business.
  • HowTo. Google no longer shows HowTo rich results. The markup won't hurt, but don't expect a display benefit.
  • Speakable. It's a limited beta aimed at news publishers. For most businesses it's optional.
  • Invented or hidden facts. Ratings, prices or credentials that don't appear on the page are a policy violation and a trust problem.
  • Copy-paste markup from plugins that describes the wrong business type, has empty fields or conflicts with your manual markup. Duplicate, conflicting Organization blocks are common on WordPress sites with several SEO plugins.

A note on plugins versus hand-written markup

SEO plugins generate reasonable default markup, and for many small sites that's enough. The trouble starts when a theme, a page builder and one or two SEO plugins each add their own blocks. I prefer either one plugin configured carefully or hand-written JSON-LD on static sites, never both. Whichever you choose, check the final rendered page, not the settings screen, because that's what search engines read.

How to validate

  1. Rich Results Test (Google) shows which rich results a page is eligible for and flags errors in supported types.
  2. Schema Markup Validator (schema.org) checks any schema.org type, including ones Google doesn't use for rich results, such as Service.
  3. Search Console enhancement reports show errors and warnings across the site for supported types, such as Breadcrumbs and Products.
  4. Manual review. Read the JSON-LD and compare it line by line with the visible page. Automated tools don't catch facts that are valid but wrong.

I also parse every JSON-LD block programmatically during audits, because a single missing comma breaks the whole script, and those errors are easy to miss when markup is edited by hand.

A practical rollout order

If you're starting from nothing:

  1. Homepage: Organization or Person with sameAs, plus WebSite.
  2. All pages: BreadcrumbList.
  3. Service pages: Service, referencing the provider.
  4. Articles and case studies: Article or BlogPosting with author and dates.
  5. Genuine FAQs: FAQPage.
  6. Local businesses: LocalBusiness matching the Business Profile.
  7. E-commerce: Product with accurate offers.

Then validate everything and add schema checks to your regular technical SEO audit.

Common mistakes from real audits

  • Two different Organization blocks from a theme and a plugin, with different names or logos.
  • Dates that never change because a plugin hard-coded dateModified.
  • Author set to "admin" instead of a real person.
  • sameAs pointing to profiles that don't exist anymore or belong to someone else.
  • Breadcrumb markup that doesn't match the visible breadcrumbs or the URL structure.
  • Product prices in markup that differ from the price on the page after a sale ends.

Where to start if you only have an hour

Add Organization or Person markup with sameAs links to your homepage, and BreadcrumbList to your main templates. Those two steps give the biggest return for the least effort, and everything else builds on them.

Frequently asked questions

Does schema markup help with AI search?

It helps indirectly. Structured data tells search engines and AI systems what a page is, who's behind it and how pages connect, which supports entity clarity and trust. Google says no special schema is required for AI Overviews, and markup alone won't get content cited if the content itself isn't the clearest answer.

Which schema type should a consultant use?

Most consultants should use Person on their homepage with name, job title, location, sameAs profiles and knowsAbout topics. If you also run a registered business, add an Organization or ProfessionalService and connect the two, for example by marking yourself as its founder.

Is FAQ schema still worth adding?

Yes, for genuine FAQs. Google now shows FAQ rich results mainly for authoritative government and health sites, so most businesses won't get the visual display. The markup still labels questions and answers clearly for machines. Only mark up questions and answers that are visible on the page.

Should I mark up my reviews with star ratings?

Not for reviews of your own business on your own site. Google doesn't show star rich results for self-serving reviews from LocalBusiness and Organization pages. Show genuine reviews as content, and let review platforms like Google Business Profile carry your ratings.

How do I check if my schema is correct?

Use Google's Rich Results Test for supported rich result types and the Schema Markup Validator for any schema.org type. Then check Search Console's enhancement reports for site-wide issues, and compare the markup manually with the visible content to catch facts that are valid but wrong.

Want results like these for your site?

Send your website and goal. I reply within one business day (Dhaka time, GMT+6).

WhatsApp