Schema markup for AI search: what is known, plus 6 JSON-LD snippets

What is known about structured data and AI answers?

From Google (official, guide last updated 2026-07-10): structured data is not required for generative AI features in Search, and no special schema.org markup is needed for them. The same guide still recommends structured data as part of ordinary SEO, because it supports eligibility for rich results. Google's page on AI features (last updated 2025-12-10) says the only requirements are that the page is indexed and eligible to show with a snippet, and it recommends that structured data match the visible text.

From one controlled study (Ahrefs, an SEO software vendor, published 2026-05-11): the team took URLs already cited in Google AI Overviews that added JSON-LD, measured citations for 30 days before and after, and compared 1,885 treated pages with 4,000 control pages that never added schema. Relative to controls, AI Overviews showed -4.6% (statistically significant but small), AI Mode +2.4% and ChatGPT +2.2% (both indistinguishable from zero). The authors list limits: every page already had 100+ AI Overview citations in February 2025, schema additions often coincided with other edits, all schema types were pooled, the window was 30 days, and only static-HTML JSON-LD was tested.

The same article reports an earlier correlation study of about 6 million URLs in which cited pages were nearly three times as likely to carry schema, and notes that correlation cannot show cause. It also cites an outside experiment suggesting five AI systems did not use JSON-LD when fetching pages live; we did not open that experiment, so treat the claim as reported, not verified.

What does Google say about FAQ and HowTo rich results now?

• FAQ: Google's FAQ documentation page, opened 2026-10-28, states the rich result is discontinued. Its dated notes say it would stop appearing in Search from 7 May 2026 (notice added 8 May 2026) and that the documentation was removed on 15 June 2026. The last eligibility rule on record (14 September 2023) limited it to well-known government and health sites. The documentation page was still reachable when we opened it, so read the dated notes at the top of it.
• HowTo: the update log records the HowTo structured-data documentation as removed on 14 September 2023 because the rich result no longer appears on desktop or mobile.
• Neither is a reason to delete valid markup. Google's guide does not list FAQ markup as an AI-feature requirement, and schema.org still defines FAQPage. It is simply no longer a route to a Google rich result. We did not find a source saying FAQPage markup helps AI citations; the FAQPage snippet below is provided as a description of visible Q&A, not as a tactic.

What rules must any markup follow?

• Mark up only content readers can see on the page. Google's general guidelines (last updated 2026-07-10) say not to mark up content that is not visible to readers.
• Keep it accurate and relevant. Misleading markup, such as fake reviews, is not allowed, and time-sensitive values (prices, availability) should be current.
• Violations can lead to a manual action that removes rich-result eligibility; Google says this does not lower web ranking. Check Search Console's Manual Actions report.
• JSON-LD is Google's recommended format where your setup allows it (intro page, last updated 2025-12-10).
• Passing a validator does not prove correctness; Google notes the Rich Results Test can miss errors.

How were the snippets checked?

Each snippet below was parsed with Python's json.loads on 2026-10-28 and every type and property name was looked up on schema.org (Organization, Article, Service, Product, Offer, Question, Answer, BreadcrumbList, ListItem, Audience, Brand). We did not run Google's Rich Results Test or the Schema Markup Validator, because we cannot from this environment. Run both on your real pages before publishing. All names, URLs, prices and dates are fictional placeholders (example.com); replace every one and make sure each value appears on the page.

Snippet 1: Organization with sameAs

Put this on your home or about page. sameAs lists URLs of profiles that represent the same entity. Only list profiles you actually control or that genuinely describe you.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Brightwell Analytics Example Ltd",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/images/logo.png",
  "description": "Fictional company that makes web analytics software for small online shops.",
  "foundingDate": "2019-04-01",
  "email": "[email protected]",
  "sameAs": [
    "https://www.linkedin.com/company/example-placeholder",
    "https://github.com/example-placeholder",
    "https://www.youtube.com/@example-placeholder"
  ]
}

Snippet 2: Article

For a blog post or guide. Use real author and date values that are visible on the page, and update dateModified only when the content materially changes.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to read your first analytics report",
  "description": "A short walkthrough of the five numbers that matter in a first report.",
  "image": "https://www.example.com/images/first-report.png",
  "author": {
    "@type": "Person",
    "name": "Asha Example",
    "url": "https://www.example.com/team/asha-example"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Brightwell Analytics Example Ltd",
    "url": "https://www.example.com/"
  },
  "datePublished": "2026-03-02",
  "dateModified": "2026-09-14",
  "inLanguage": "en",
  "mainEntityOfPage": "https://www.example.com/blog/first-report"
}

Snippet 3: Service

For a page describing a service you sell. Do not add an offers block unless the price is stated on the page.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Analytics Setup Audit",
  "description": "A fixed-scope review of an online shop's analytics tracking, delivered as a written report.",
  "serviceType": "Analytics consulting",
  "url": "https://www.example.com/services/analytics-setup-audit",
  "provider": {
    "@type": "Organization",
    "name": "Brightwell Analytics Example Ltd",
    "url": "https://www.example.com/"
  },
  "areaServed": "Worldwide",
  "audience": {
    "@type": "Audience",
    "audienceType": "Small online shop owners"
  }
}

Snippet 4: Product with Offer

For a product page where price and availability are shown. Keep price and availability in sync with the visible page, including when they change. Do not add aggregateRating or review unless real reviews are visible on the page.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Brightwell Starter Plan",
  "description": "Hosted analytics for one shop, up to 10,000 sessions a month.",
  "sku": "BW-STARTER-001",
  "image": "https://www.example.com/images/starter-plan.png",
  "brand": {
    "@type": "Brand",
    "name": "Brightwell Example"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://www.example.com/pricing#starter",
    "price": "29.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "priceValidUntil": "2027-03-31"
  }
}

Snippet 5: FAQPage

Only for a page that visibly lists these questions and answers. Remember the Google rich result is discontinued (see above); this simply describes the visible Q&A.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does the Starter Plan include data export?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. You can export raw events as CSV once a day."
      }
    },
    {
      "@type": "Question",
      "name": "Can I cancel at any time?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Cancel from the billing page; access continues until the end of the paid month."
      }
    }
  ]
}

Snippet 6: BreadcrumbList

The last item is the current page. position starts at 1. Mirror the breadcrumb trail readers see.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://www.example.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://www.example.com/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "How to read your first analytics report",
      "item": "https://www.example.com/blog/first-report"
    }
  ]
}

How do I add a snippet to a page?

Wrap the JSON in a script tag in the page head or body, one block per type or an array. Render it in the server-sent HTML where you can; the Ahrefs study tested only static-HTML JSON-LD, and we have no evidence on JavaScript-injected markup.

<script type="application/ld+json">
{ ...paste one snippet here... }
</script>