Schema.org structured data is no longer just about earning rich snippets on Google. In 2026, it has become a direct lever for visibility with generative AI engines. When ChatGPT, Gemini, or Perplexity analyze your site, JSON-LD markup lets them understand without ambiguity who you are, what you offer, and why your content is trustworthy.

A site without structured data forces the AI to guess. A site with complete markup gives it certainty. And AI engines cite the sources they understand first.

This guide shows you exactly which schemas to implement, in what order, with ready-to-copy code examples.

Why Schema.org matters for GEO

AI engines work differently from Google. When Googlebot crawls your page, it interprets HTML, meta tags, and popularity signals to rank your page. When an AI crawler (GPTBot, ClaudeBot, PerplexityBot) analyzes your page, it looks to understand entities: who is speaking, about what, with what authority, and when.

Structured data answers exactly these questions, in a format machines read without interpretation.

Specifically, Schema.org impacts 3 of the 8 Detekia GEO Score criteria:

  • Structured data (10 points) — direct, measurable impact
  • Authority & E-E-A-T (15 points) — the Organization schema and author information strengthen credibility signals
  • Extractability (25 points) — the FAQPage schema structures your content in a format natively extractable by AI engines

That is a potential impact on 50 out of 100 points of your GEO Score.

The 5 priority schemas for GEO

You do not need to implement all 806 Schema.org types. For GEO, 5 schemas cover 90% of the impact. Here they are, in priority order. To understand how each criterion weighs in the GEO score, see the 8 GEO criteria explained.

1. Organization — your identity

This is the most fundamental schema. It tells AI engines: "This is who we are." Without it, generative engines have no certainty about your business identity.

Where to implement: on your homepage, in the <head> or before the closing </body>.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://www.your-website.com",
  "logo": "https://www.your-website.com/logo.png",
  "description": "Concise description of your business in 1-2 sentences.",
  "foundingDate": "2020",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street",
    "addressLocality": "New York",
    "addressRegion": "NY",
    "postalCode": "10001",
    "addressCountry": "US"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "contact@your-website.com",
    "contactType": "customer service"
  },
  "sameAs": [
    "https://www.linkedin.com/company/your-company",
    "https://twitter.com/your-company"
  ]
}

Key points for GEO:

  • The sameAs property is crucial: it lets AI engines connect your site to your LinkedIn, Twitter, Wikipedia, and Crunchbase profiles. The more consistent these links are, the stronger your entity identity.
  • The description should be factual and concise — it is often what AI will extract first to introduce you.
  • The logo as an absolute URL lets AI engines visually verify your identity.

2. FAQPage — your questions and answers

This is the most impactful schema for GEO. AI engines operate on a question-and-answer basis: a user asks a question, the AI looks for the best answer. The FAQPage schema structures your content in exactly that format.

Where to implement: on any page containing Q&A — dedicated FAQ page, bottom of product pages, help sections.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How can I improve my site's visibility in ChatGPT?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "To be cited by ChatGPT, optimize your content's extractability (direct answers in the first 100 words), add Schema.org structured data, verify your robots.txt does not block GPTBot, and source your claims with verifiable data."
      }
    },
    {
      "@type": "Question",
      "name": "How long does it take to appear in AI answers?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Technical optimizations (robots.txt, Schema.org) take effect in 2 to 4 weeks. Content improvements are reflected in 4 to 8 weeks. Building external authority takes 2 to 3 months."
      }
    }
  ]
}

Key points for GEO:

  • Each answer must be self-contained: understandable without additional context. AI engines often extract the answer alone, without the question.
  • Questions should be phrased in natural language, the way a user would ask ChatGPT. No jargon, no corporate phrasing.
  • Limit yourself to 5-10 questions per page. Beyond that, informational density drops and Google may ignore the markup.
  • Each answer should contain verifiable facts (numbers, timeframes, steps) — not vague responses.

3. Article / BlogPosting — your editorial content

This schema identifies your articles as structured editorial content, with an author, a date, and editorial context. For AI engines, this is a strong credibility signal — especially when the author is identifiable and expert.

Where to implement: on every blog post, guide, case study, or editorial content page.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "GEO: the complete guide to getting cited by AI in 2026",
  "description": "GEO definition, 8 citation-worthiness criteria, 7 concrete actions to optimize your site.",
  "author": {
    "@type": "Person",
    "name": "John Smith",
    "url": "https://www.linkedin.com/in/johnsmith",
    "jobTitle": "Founder",
    "worksFor": {
      "@type": "Organization",
      "name": "Your Company"
    }
  },
  "publisher": {
    "@type": "Organization",
    "name": "Detekia",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.detekia.com/logo.png"
    }
  },
  "datePublished": "2026-03-27",
  "dateModified": "2026-03-27",
  "image": "https://www.detekia.com/images/geo-guide-og.jpg",
  "mainEntityOfPage": "https://www.detekia.com/blog/geo-guide-complet-2026"
}

Key points for GEO:

  • The author object with a url pointing to LinkedIn or a bio page is essential. AI engines cross-reference author information to evaluate expertise (E-E-A-T).
  • dateModified is as important as datePublished. AI engines check content freshness — a recent modification date is a positive signal.
  • The description should summarize the content in a factual, extractable way.

4. WebSite + SearchAction — your site as an entity

This schema helps AI engines understand your site as a whole, not just page by page. It is also used by Google to display the sitelinks search box.

Where to implement: on the homepage only.

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Detekia",
  "url": "https://www.detekia.com",
  "description": "GEO audit to measure your site's visibility in AI answers.",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://www.detekia.com/results?url={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}

→For more on FAQPage, see FAQ and FAQPage Schema: the winning GEO combo.

5. BreadcrumbList — your architecture

Breadcrumb markup helps AI engines understand your site's hierarchy: which page is the parent of which, how content is organized. It is a structural signal that reinforces crawlability.

Where to implement: on all internal pages.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://www.detekia.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://www.detekia.com/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "GEO: the complete 2026 guide",
      "item": "https://www.detekia.com/blog/geo-guide-complet-2026"
    }
  ]
}

Secondary schemas by activity type

Beyond the 5 priority schemas, certain specific markups strengthen your visibility depending on your business type.

E-commerce

  • Product — name, price, availability, reviews. AI engines use these for product comparisons.
  • AggregateRating — average rating and number of reviews. Strong trust signal.
  • Offer — price, currency, conditions. Lets AI engines cite precise pricing.

→For a complete approach, read E-commerce: how to appear in AI product recommendations.

Services and professional firms

  • LocalBusiness — address, hours, geographic area. Essential for local queries ("best [profession] in [city]").
  • Service — description of your offerings with pricing and coverage area.

SaaS and tech

  • SoftwareApplication — name, operating system, category, price. AI engines cite this info in software comparisons.
  • HowTo — steps for using your tool. A format that is highly extractable by AI engines.

→Before implementing schemas, make sure your site is crawlable by AI bots: llms.txt, robots.txt and AI crawlability.

Technical implementation

The format: JSON-LD only

There are three formats for structured data: JSON-LD, Microdata, and RDFa. In 2026, the choice is clear: use JSON-LD in 100% of cases.

Why:

  • Google officially recommends it
  • It is added as a <script> block without touching the visible HTML
  • It is easier to maintain and debug
  • AI crawlers parse it natively

Where to place the code

The JSON-LD block goes in the <head> of your page or just before </body>. Both work. The most common convention is in the <head>.

<head>
  <!-- ... your meta tags ... -->
  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Your Company"
  }
  </script>
</head>

Multiple schemas on a single page

You can (and often should) have multiple JSON-LD blocks on a single page. For example, your homepage can contain an Organization schema, a WebSite schema, and an FAQPage schema. Each schema gets its own <script type="application/ld+json"> block.

Next.js implementation

If your site is built with Next.js, use the Head component:

import Head from 'next/head';

export default function HomePage() {
  const schema = {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Your Company",
    "url": "https://www.your-website.com"
  };

  return (
    <>
      <Head>
        <script
          type="application/ld+json"
          dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
        />
      </Head>
      {/* ... your content ... */}
    </>
  );
}

WordPress implementation

Two options:

  • Plugin — Yoast SEO and Rank Math automatically add certain schemas (Organization, Article, BreadcrumbList). Check the settings and complete manually if needed (FAQPage is not always automatic).
  • Manual — paste the JSON-LD block in your page's HTML editor, or use a plugin like "Insert Headers and Footers" to add it globally.

Testing and validation

Before publishing, always test your markup.

Testing tools

  • Google Rich Results Test (search.google.com/test/rich-results) — verifies if your markup is valid and eligible for rich results. This is the reference tool.
  • Schema Markup Validator (validator.schema.org) — validates your markup syntax against the complete Schema.org vocabulary. Stricter than the Google test.
  • Your Detekia score — run an audit before and after implementation to measure the impact on your structured data score.

Common errors to avoid

  • Invisible markup — the content described in the schema must be visible on the page. A FAQPage schema whose questions are not visually displayed violates Google guidelines and may be ignored.
  • Inconsistent information — the company name in the Organization schema must match exactly what is displayed on your site, your Google Business Profile, and your social media. Any inconsistency weakens AI trust.
  • Missing or false dates — datePublished and dateModified must reflect reality. Do not set today's date as dateModified if you have not actually modified the content.
  • Minimal schema — an Organization schema with only the name is nearly useless. Fill in all relevant properties: logo, address, contact, sameAs.
  • Forgetting to test after deployment — a template change, plugin update, or migration can silently break your markup.

Implementation checklist

Phase 1 — The fundamentals (day 1)
  • ☐Organization schema on homepage with name, URL, logo, description, address, contact, sameAs
  • ☐WebSite schema on homepage with SearchAction
  • ☐Test with Rich Results Test
Phase 2 — The content (day 2-3)
  • ☐Article or BlogPosting schema on each editorial content piece with complete author, dates, description
  • ☐BreadcrumbList schema on all internal pages
  • ☐FAQPage schema on pages containing Q&A
  • ☐Test each modified page
Phase 3 — Activity-specific (week 2)
  • ☐Activity-specific schemas (Product, LocalBusiness, SoftwareApplication, etc.)
  • ☐Consistency check: does the information in schemas match what is displayed?
  • ☐Detekia audit to measure impact on score
Ongoing phase
  • ☐Verify markup after every site update
  • ☐Add FAQPage on every new page containing Q&A
  • ☐Update dateModified with every real content modification

Frequently asked questions

Is structured data enough to be cited by AI?

No. It represents one of the 8 GEO Score criteria (10 direct points + indirect impact on authority and extractability). But without quality content, without crawlability, and without external presence, markup alone is not enough. It is an accelerator, not a substitute.

How long before seeing the impact?

Effects on Google rich snippets appear within a few days to 2 weeks. Impact on AI citations takes 2 to 4 weeks, the time for AI crawlers to re-analyze your site.

Can I use an automatic schema generator?

Yes, to get started. Tools like Google's Structured Data Markup Helper or the built-in features of Yoast/Rank Math work well for basic schemas. But for GEO-optimized markup (complete sameAs, detailed author, well-structured FAQPage), manual customization is often necessary.

Can too many schemas hurt?

No, as long as each schema is valid and describes content that is actually present on the page. Google and AI engines have no limit on the number of schemas per page. The only rule: only mark up what is visible and truthful.

Measure the impact

You have implemented your schemas? Measure the impact right away.

Run a GEO audit on Detekia — your structured data score will go from 0-3 to 7-10 if the implementation is correct. In under 60 seconds, no signup required.