AEO and AI search

Schema markup for AEO: what to add and why

IN SHORT

Schema markup is structured data, usually written as JSON-LD, that labels what a page is about using the shared schema.org vocabulary. It helps machines read your pages unambiguously. Google says no special schema is needed for its AI features, and no provider guarantees a citation from markup, but accurate markup removes guesswork about who you are and what you offer.

By Hristijan Najcheski, Head of SEO and AEO at Webtec: technical SEO and AI SEOReviewed October 11, 20269 min read

Google recommends JSON-LD for structured data, and says markup must match content visitors can see.
Google says there is no special schema.org markup to add for AI Overviews or AI Mode.
Google stopped showing FAQ rich results in Search from May 7, 2026, so FAQ markup no longer earns that display.
It supports entity clarity: who you are and what you do. It never guarantees a feature or a citation.

TRY IT

Switch markup types on and read the JSON-LD

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "name": "Northfield Accounting",
      "url": "https://northfield.example",
      "sameAs": [
        "https://www.linkedin.com/company/northfield"
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What does bookkeeping include?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Recording and reconciling every transaction each month."
          }
        }
      ]
    }
  ]
}

What schema markup is

Schema.org is a shared vocabulary of types, such as Organization, Product or Article, and properties, such as name, price or author. It is understood, according to the schema.org getting-started guide, by the major search engines including Google and Microsoft. You can write it in JSON-LD, Microdata or RDFa. Google recommends JSON-LD because it is usually the easiest to implement and keeps markup separate from the visible text.

The markup does not change how the page looks. It adds a machine-readable description of the same facts: this page is about this business, this service, this product at this price. See schema markup for a short definition.

What Google says about schema and AI features

Google’s documentation on AI features (last updated December 2025) says there is no special schema.org structured data you need to add to appear in AI Overviews or AI Mode, and that structured data should match the visible text. Its generative AI optimization guide (July 2026) adds that structured data is not required for generative AI search and remains useful for rich result eligibility.

So the honest position is this. Schema is not a lever Google has said it uses to choose AI answers. It is still worth doing, because it helps machines read the page, qualifies pages for features that do use it, and it is evidence that your facts are consistent. We do not claim it makes assistants cite you.

Other assistants have not published how, or whether, they use markup. Because the markup states the same facts the page shows, it costs little and cannot hurt when it is accurate.

The types we use most

Organization: who you are, with your name, logo, profiles and contact details.
LocalBusiness subtypes: address, opening hours and service area for local firms.
Service and Product with Offer: what you sell, and price and availability where shown on the page.
Article and Person: who wrote a guide and what their expertise is.
BreadcrumbList: where a page sits in your site.
Review and AggregateRating, only where the reviews are genuine and visible on the page.
FAQPage: valid schema.org, but see the next section before relying on it.

FAQ markup: what changed

For years FAQPage markup could earn an expandable question display in Google results. In September 2023 Google limited that to well-known government and health sites. Google’s documentation now says FAQ rich results no longer appear in Search from May 7, 2026, and the FAQ documentation has been removed.

Keep visible FAQs on service pages and guides, because buyers read them and they are quotable passages. Whether to keep the matching markup is a smaller decision: it is harmless when accurate, but do not expect a display in Google, and do not add it where no questions appear on the page.

How to implement it, step by step

List your page types: home, service, product, guide, location, contact.
Choose the most specific schema.org type for each, and fill in the properties you can show on the page.
Write JSON-LD in a script block, ideally generated from the same data that renders the page.
Make sure every fact in the markup is visible on the page.
Validate with the Schema Markup Validator and Google’s Rich Results Test, then monitor the rich result status reports in Search Console, because templating mistakes can break markup after launch.
Link the same entity facts to your profiles with sameAs, and keep them consistent with brand, entity and mentions.

What to avoid

Google’s general guidelines say not to mark up content that is not visible to readers, and not to use fake reviews or misleading claims. Spammy markup can trigger a manual action that removes rich result eligibility. Passing the Rich Results Test does not guarantee a rich result will appear.

Also avoid adding every type available, and avoid blocking marked-up pages with robots.txt or noindex. Markup on a page crawlers cannot read does nothing. Pair this work with AI crawler access checks, and see llms.txt for the other machine-readable file people ask about.

How to measure it

Measure correctness first: zero errors in the validators and Search Console reports, and a spot check that each marked-up fact is on the page. Then measure features that depend on it, such as product or review displays, in Search Console.

Do not credit schema for AI citations without a controlled test. Change one thing at a time and track a fixed prompt set, as described in measuring AI visibility. Most of the time you will not be able to isolate its effect, and that is fine.

Examples by industry

Illustrative scenarios, not client results. Pick the one closest to your business.

LAW FIRMS
A law firm with three practice areas. Every page is marked up the same generic way, or not at all.
1. Add Organization markup with the firm’s real profiles and details.
2. Add Service markup to each practice area page, matching visible content.
3. Add Person markup for attorneys on their profile pages, with real credentials.
Takeaway: Precise, honest markup states who the firm is and what each page covers.
DENTAL AND HEALTH CLINICS
A dental clinic. The site lists services, hours and a location, but only as text.
1. Add LocalBusiness-type markup with address, hours and the practice’s profiles.
2. Keep a visible FAQ on treatment pages, and mark it up only if the questions appear on the page.
3. Validate it and keep it in step with the page.
Takeaway: Structured facts make a local business unambiguous to machines.
E-COMMERCE BRANDS
A store with genuine customer reviews. Product pages show reviews visually but have no markup.
1. Add Product and Offer markup with price and availability.
2. Add AggregateRating only where the reviews are genuine and visible on the page.
3. Add BreadcrumbList for the collection structure.
Takeaway: Markup must match what shoppers can see. Never add reviews that are not on the page.

THE WEBTEC ANSWER METHOD · STEP 5 OF 6

Plumb: how we do it

Structured data is part of the plumbing: it states your facts clearly to machines.

Add Organization, Service or Product markup that matches the page
Add Article and Person markup to guides
Validate and keep it generated from content

See all six steps

Common mistakes

Marking up content that does not appear on the page, which breaks Google’s guidelines and can lead to a manual action.
Adding every type available, which adds noise and maintenance without any benefit.
Letting markup go out of sync with the page, so prices or hours in the markup contradict the visible page.
Expecting schema to guarantee rankings or citations. Google says no special schema is needed for AI features.
Adding review markup for reviews that are not shown, or that you wrote yourself.
Relying on FAQ markup for a Google display after Google ended FAQ rich results.

Checklist

Organization markup is on your site, with consistent name, logo and profiles.
Service, Product or LocalBusiness markup matches the visible facts on each page.
Guides carry Article and author markup with real credentials.
All markup validates and matches the visible page.
Markup is generated from the same data as the page.
Marked-up pages are indexable and not blocked in robots.txt.
Rich result reports in Search Console show no errors.

Questions

Does schema markup help AI citations?

Google says it does not require any special schema for AI Overviews or AI Mode, and no major provider has said it uses markup to choose citations. It helps machines understand your pages and supports rich results where features exist. Treat it as hygiene, not a growth lever. Accurate markup works alongside clear content, a crawlable site and consistent business facts. The most reliable benefit of accurate markup is consistency: it states the same facts your page shows, in a form that is easy to validate.

Should I use FAQ markup everywhere?

No. Google stopped showing FAQ rich results in Search from May 7, 2026, after limiting them to well-known government and health sites in 2023. Visible FAQs are still worth having on service pages and guides because buyers and assistants can read them. Add the markup only where the questions and answers appear on the page, and expect no special display. The visible questions and answers are what readers and assistants can use, so spend your effort on writing those well.

Is JSON-LD better than Microdata?

For most sites, yes. Google supports JSON-LD, Microdata and RDFa, and recommends JSON-LD because it is usually the easiest to implement and maintain. It sits in one block, separate from your visible text, so it is easier to generate from your content and to test. Use whichever your platform produces correctly, and validate it. Validate after every template change, because a theme update can silently break markup. If you are on WordPress or Shopify, check whether your theme or app already outputs markup, to avoid duplicate or conflicting blocks on the same page.

How long does it take and what does it cost?

For a small site, core markup for Organization, Service and Article takes a few hours to a day, depending on your platform. Plugins and templates can generate it, but they need checking for accuracy. We do not quote prices in guides. The larger cost is keeping the markup accurate over time, which is why we generate it from content. Plan a quick check after every redesign or plugin update, because that is when markup most often breaks.

Do local businesses need schema?

Yes, in a modest way. LocalBusiness markup with your address, hours, service area and profile links makes your details unambiguous and matches what is on your site and Google Business Profile. Google’s guide also points local businesses to keep Business Profile details current. Consistency matters more than adding extra types. Match the markup to the details a visitor sees on the contact page, and update both together when hours change. Use the same business name and phone format everywhere, because small differences make details look like different businesses.

Can wrong schema hurt me?

Yes. Google says spammy or misleading markup can trigger a manual action that removes rich result eligibility, though it says this does not affect ranking. Mismatched facts can also confuse machines. If you are unsure, add less and keep it accurate. A short, correct Organization and Article markup is better than a long, wrong set. Run your key pages through the validators after every redesign, since mismatched or broken markup is the most common problem we see. Fix errors in the order Search Console lists them, and re-validate after each change.

Sources

Webtec reviews this page regularly. Search and platform features change, so check provider documentation for the latest. How we research and verify our guides.

Hristijan Najcheski

Head of SEO and AEO at Webtec: technical SEO and AI SEO. Leads technical SEO and AI SEO at Webtec: crawling, indexing, site speed, structured data and how AI systems read a site. He also verifies the numbers in our case studies.

Related guides

Pick up where this one leaves off.

All AEO and AI search guides

Previousllms.txt NextMeasuring AI visibility

Want this done for your business?

Book a consultation

Explore our services

Start with the one closest to what you just read.

All services