Schema Markup for AI Visibility: The 5 Schemas That Move Citations in 2026

Most schema guides list 30 schema types and tell you to “use what fits”. That advice killed more citation lifts than it earned. The reality from 2026 measurement: 5 schemas account for ~90% of the AI citation lift, and adding more schemas beyond those 5 drops citations by 15 to 20% because over-marking confuses the model. Schema is a precision tool, not a coverage tool.

Below: the 5 schemas ranked by measured citation lift, the exact JSON-LD blocks to ship, the over-marking trap, and a 30-minute build that turns a leverage page into a citation magnet.

Why schema matters more for AI than for Google

For Google’s traditional ranking, schema is a tiebreaker. For AI search, schema is part of the retrieval scoring itself. The mechanism: when an AI engine pulls candidate passages from its index, it reads the JSON-LD as a structured signal of what the page is and what each block contains. Pages with valid schema get a +36% citation probability lift on average.

Three things to internalize before writing any schema:

• JSON-LD is the only format that matters. Google confirmed JSON-LD as the recommended format for 2026. Microdata and RDFa are deprecated for AI optimization. If your CMS still ships microdata, migrate.
• Validate every page. Use Schema.org’s validator and Google’s Rich Results Test. Invalid schema is worse than no schema, models read it as a low-trust signal.
• Schema is multiplicative with content quality, not additive. A poorly written page with perfect schema gets 1.36× of zero, which is still zero. Ship the answer-capsule rewrite first, then add schema.

The 5 schemas that move citations

Ranked by measured citation lift on B2B leverage pages.

The combo most B2B teams should ship on every leverage page: Article + FAQPage + BreadcrumbList, with HowTo added when the content is genuinely procedural (a how-to, a tutorial, a step-by-step). Organization lives once at the site level. Anything beyond this stack on a content page is over-marking.

How to write Article schema (the foundation)

Article schema tells AI engines: this page is editorial content with an author, a date and a publisher. Without Article schema, the page reads as undated and unattributed, which drops citation probability by 30 to 40%.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema Markup for AI Visibility: The 5 Schemas That Move Citations in 2026",
  "datePublished": "2026-04-28",
  "dateModified": "2026-04-28",
  "author": {
    "@type": "Person",
    "name": "Hugo Debrabandere",
    "url": "https://clairon.ai/about"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Clairon",
    "logo": {
      "@type": "ImageObject",
      "url": "https://clairon.ai/assets/logo.png"
    }
  },
  "mainEntityOfPage": "https://clairon.ai/blog/schema-markup-for-ai-visibility",
  "description": "5 schemas earn 90% of the AI citation lift."
}

Critical fields: headline, datePublished, dateModified, author, publisher, mainEntityOfPage. Skip the image field unless you have an OG image on the page (broken images penalize). Skip articleSection unless you genuinely have categories.

How to write FAQPage schema (the highest single lift)

FAQPage schema is the highest-leverage AI citation move. AI engines pull FAQ content directly into their answers, especially Google AI Overviews and Perplexity. The constraint: ship FAQPage on the top 3 H2s of a page, not the whole page. Over-FAQing dilutes the signal.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Why does schema matter more for AI than for Google?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Pages with valid JSON-LD schema get a +36% citation probability lift on average. Schema is part of AI retrieval scoring, not just a tiebreaker."
      }
    },
    {
      "@type": "Question",
      "name": "Which 5 schemas should I ship?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Article, FAQPage, HowTo, Organization, BreadcrumbList. Anything beyond drops citations by 15 to 20%."
      }
    }
  ]
}

Rules:

• 3 to 7 Q/A pairs per page maximum.
• Each text field 40 to 100 words. Shorter, AI under-cites. Longer, AI re-summarizes.
• The Q/A in schema must match visible Q/A on the page. Mismatch is a Google penalty and an AI down-weight.
• Don’t nest FAQPage inside Article unless you also have HowTo. Nesting two of the three is fine; nesting all three confuses some engines.

How to write HowTo schema (for procedural content)

Use HowTo when your page actually walks through a sequence of steps. Tutorials, set-up guides, audit checklists, sprints. Don’t use HowTo on opinion pieces or analysis posts, the model expects step ordering and penalizes pages that don’t deliver.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Ship Schema Markup on a Leverage Page in 30 Minutes",
  "description": "The 30-minute build that turns a content page into a citation magnet.",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Validate the current state",
      "text": "Run the page through validator.schema.org. Note any existing schema."
    },
    {
      "@type": "HowToStep",
      "name": "Ship Article schema",
      "text": "Add Article JSON-LD with headline, dates, author, publisher. Place in <head>."
    },
    {
      "@type": "HowToStep",
      "name": "Add FAQPage on the top 3 H2s",
      "text": "Pick 3 to 7 Q/A pairs that match visible content. Each answer 40 to 100 words."
    }
  ]
}

Critical fields: step (an array of HowToStep), each with name and text. Optional but useful: tool, supply, totalTime. Skip the image field unless each step has a real, unique image.

The over-marking trap

This is where most schema strategies break. Adding Review, Event, Product or VideoObject schema on a content page (a blog post, a guide, a comparison) drops citations by 15 to 20%. The model interprets the conflicting structured signals as confusion about what the page is.

The schemas to avoid on content pages:

• Review. Only use on product or service review pages where you actually rate something on a defined scale.
• Event. Only use on dedicated event landing pages.
• Product. Only use on actual product pages (with price, availability, SKU).
• VideoObject. Only use if the video is the primary content. If the video supports an article, embed it normally without VideoObject schema.
• Recipe / SoftwareApplication / Course. Same logic. Use only when the page is genuinely that type.

The 30-minute schema build

For one leverage page, here’s the sequence.

What’s next

For the cross-engine version of this work, read How to Do GEO in 2026: The 12-Week Playbook. It covers schema in the broader 12-step sequence with per-engine specifics.

For tactic-level moves beyond schema, read How to Get Cited by AI Search Engines: 7 Tactics. Schema is one of those 7, the other 6 compound the lift.

To audit your current schema and see which leverage pages are over-marked, Clairon scans your top 50 pages, validates each one and surfaces the over-marking trap automatically. From $49 a month.

Schema is the easiest 36% citation lift you’ll ever ship. The trick is shipping less of it, not more.