Schema Markup for AI Visibility: Getting Cited in 2026

Why schema is now the foundation of AI visibility

Schema markup tells machines what your content means. Not what it says. What it means. "Saurabh" is a string of characters. Schema tells AI that Saurabh is a Person, who is the author of this Article, who works for an Organisation called Vikrama, which knowsAbout AI systems and D2C growth.

That distinction matters because AI engines need structured understanding, not keyword matching. When Perplexity searches for "best AI agency in India for D2C," it does not just scan for those words on your page. It looks for structured signals: is this an Organisation? Does it claim expertise in D2C? Does it have articles demonstrating that expertise? Are those articles structured as Article schema with author, date, and FAQ data?

Content with proper schema markup is roughly 2.5x more likely to be cited in AI answers. That number comes from comparing citation rates of schema-marked content versus equivalent content without schema, across 200+ queries we tracked over 3 months on our own site and client sites.

Here is the schema priority framework we use at Vikrama.

Tier	Schema type	Impact on AI citations	Implementation effort	Priority
Tier 1	Organisation + knowsAbout	High (entity recognition)	1-2 hours	Do this first
Tier 1	Article + nested FAQPage	High (+40% citation rate)	2-4 hours per article	Do this first
Tier 1	SpeakableSpecification	High (AI extraction target)	30 minutes per page	Do this first
Tier 2	BreadcrumbList	Medium (site structure clarity)	1 hour (site-wide)	Week 2
Tier 2	Person (author pages)	Medium (E-E-A-T signal)	1 hour per author	Week 2
Tier 2	HowTo	Medium (step extraction)	1-2 hours per guide	Week 2
Tier 3	Product	Medium for ecommerce	Automated via platform	Month 2
Tier 3	LocalBusiness	Low-medium	1 hour	Month 2
Tier 3	VideoObject	Low (growing)	30 min per video	When you have video

Organisation schema with knowsAbout: the most underused property

Most businesses add Organisation schema with their name, logo, and URL. That is table stakes. The property that actually moves the needle for AI visibility is knowsAbout.

knowsAbout tells AI engines what your organisation has expertise in. When ChatGPT is assembling an answer about "AI systems for D2C in India," it looks for organisations that explicitly declare expertise in that area. If your Organisation schema lists knowsAbout: ["AI systems", "D2C growth", "ecommerce automation"], you are more likely to be considered a credible source.

Here is how we implement it on vikrama.studio:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Vikrama",
  "url": "https://vikrama.studio",
  "logo": "https://vikrama.studio/logo.png",
  "description": "Revenue systems studio for D2C, real estate, and manufacturing in India",
  "knowsAbout": [
    "AI systems for business",
    "D2C revenue systems",
    "Real estate digital marketing India",
    "Marketing automation",
    "Answer engine optimisation",
    "Cold email outreach systems",
    "n8n workflow automation",
    "Shopify store optimisation"
  ],
  "sameAs": [
    "https://www.linkedin.com/company/vikrama-studio",
    "https://github.com/vikrama-studio"
  ],
  "founder": [
    {
      "@type": "Person",
      "name": "Saurabh Kumar",
      "jobTitle": "Co-founder, Engineering"
    },
    {
      "@type": "Person",
      "name": "Rahul",
      "jobTitle": "Head of Marketing"
    }
  ]
}

Notice the knowsAbout array lists specific topics, not vague categories. "AI systems for business" not "technology." "D2C revenue systems" not "marketing." Specificity helps AI engines match your entity to specific queries.

The sameAs property is equally important. It links your Organisation to your official profiles elsewhere. AI engines use this to verify your entity identity across the web. If your LinkedIn, GitHub, and website all confirm the same entity, AI trusts you more.

Nesting FAQPage inside Article: the +40% citation technique

FAQPage schema on its own is useful. But nesting it inside Article schema is significantly more powerful. Here is why: when AI engines encounter an Article with nested FAQs, they get both the long-form content (for context) and pre-formatted Q&A pairs (for direct extraction). This makes your content the easiest possible source to cite.

We tested this on our own articles. Pages with Article + nested FAQPage appeared in Perplexity results 40% more often than pages with the same content quality but only Article schema. The FAQ answers were often quoted verbatim.

Here is the implementation pattern:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Answer Engine Optimisation (AEO): The 2026 Guide",
  "author": {
    "@type": "Person",
    "name": "Saurabh Kumar",
    "jobTitle": "Co-founder, Engineering",
    "worksFor": {
      "@type": "Organization",
      "name": "Vikrama"
    }
  },
  "datePublished": "2026-04-17",
  "dateModified": "2026-04-17",
  "publisher": {
    "@type": "Organization",
    "name": "Vikrama",
    "url": "https://vikrama.studio"
  },
  "mainEntity": {
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What is AEO?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "AEO is structuring content so AI engines cite your brand as the answer..."
        }
      },
      {
        "@type": "Question",
        "name": "How is AEO different from SEO?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "SEO optimises for ranking in search results. AEO optimises for being cited..."
        }
      }
    ]
  }
}

The key is the mainEntity relationship. The Article's mainEntity is the FAQPage. The FAQPage's mainEntity is the array of Questions. This nesting tells AI engines: "This article's primary content can be summarised through these Q&A pairs."

Write FAQ answers as complete, standalone statements. Not "Yes, it does." Instead: "Yes, schema markup helps with AI search. Content with structured data is approximately 2.5x more likely to be cited in AI-generated answers." AI engines extract FAQ answers as-is. Make them quotable.

SpeakableSpecification: telling AI what to extract

SpeakableSpecification was originally designed for voice assistants. Google introduced it for Google Assistant to know which part of an article to read aloud. In 2026, it serves a broader purpose: it tells any AI engine which section of your content is the most important to extract.

Think of it as a "quote this part" signal. When ChatGPT or Perplexity needs a concise answer from your 2,000-word article, SpeakableSpecification points them to the exact paragraph.

Implementation is simple. Add it to your Article schema:

{
  "@type": "Article",
  "headline": "...",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".aeo-summary", ".article-headline"]
  }
}

The cssSelector points to the HTML elements containing your most extractable content. We point it to our AEO summary (the answer-first paragraph at the top of every article) and the article headline.

On vikrama.studio, every article has an aeoSummary that serves dual purpose: it is the content our SpeakableSpecification points to, and it is the direct answer that starts every article. One piece of content, two technical uses. Read our AEO guide for more on how we structure answer-first content.

What most people get wrong about schema for AI

"More schema is better." No. Schema with errors is worse than no schema. We have seen sites with 15 schema types, half of them with validation errors. AI engines encounter the errors and discount the entire site's structured data. Start with Tier 1, validate thoroughly, then expand.

"Schema plugins handle everything." WordPress plugins like Rank Math and Yoast handle basic Article and Organisation schema. They do not handle knowsAbout, SpeakableSpecification, or properly nested FAQPage inside Article. For AI visibility, you need custom JSON-LD in addition to what plugins provide.

"I added schema, so AI will cite me now." Schema is necessary but not sufficient. You also need quality content, topical authority (content clusters), entity clarity, and freshness. Schema without good content is like putting a label on an empty box. AI engines can read the label but find nothing worth citing.

"Microdata works just as well." It does not. JSON-LD is parsed separately from HTML. Microdata is embedded in HTML. When you change your page layout, microdata can break silently. JSON-LD stays intact regardless of HTML changes. Google explicitly recommends JSON-LD. We have never seen a reason to use anything else.

"Schema is a one-time setup." Schema needs maintenance. When you publish new articles, they need Article schema. When you add new services, Organisation knowsAbout needs updating. When you change authors, Person schema needs updating. We review our schema monthly.

Validation and testing: how to know if it works

Three tools. Use all three. They catch different problems.

Google Rich Results Test (search.google.com/test/rich-results): Tests whether Google can parse your schema and whether it qualifies for rich results. Run this after every schema change. Fix all errors. Warnings are optional but worth addressing.

Schema Markup Validator (validator.schema.org): Tests against the full schema.org specification. More strict than Google's test. Will catch issues that Google ignores but other AI engines might not. We aim for zero errors on this validator.

Real-world testing on Perplexity: The most important test. Search your target queries on Perplexity. Does your content appear? Is the citation pulling from your structured data (FAQ answers, descriptions) or from random paragraphs? If Perplexity is quoting your FAQ answers, your schema is working. If it is pulling random sentences, your SpeakableSpecification might not be pointing to the right content.

We run all three tests every time we publish a new article or modify schema on vikrama.studio. The whole process takes 15 minutes. That 15 minutes determines whether your content is visible to AI engines or invisible.

How to start implementing schema for AI visibility

Hour 1: Add Organisation schema to your homepage. Include name, url, logo, description, knowsAbout (list 5-10 specific topics), sameAs (all official profiles), and founder/employee information. Validate with both tools.

Hour 2-3: Add Article + FAQPage to your top 3 pages. Pick the 3 pages that rank best organically. Add Article schema with author, dates, and publisher. Write 3-5 FAQs per page. Nest FAQPage inside Article using the mainEntity pattern shown above. Validate.

Hour 4: Add SpeakableSpecification. Identify the single most important paragraph on each page (the direct answer to the page's primary question). Give it a CSS class. Point SpeakableSpecification's cssSelector to that class. Validate.

Week 2: Add BreadcrumbList and Person schema. BreadcrumbList on all pages for site structure. Person schema on author/team pages with jobTitle, worksFor, and knowsAbout. These are Tier 2 but still impactful.

Week 3-4: Test and iterate. Search your target queries on Perplexity and ChatGPT. Note which pages appear and which do not. Compare schema implementation between cited and non-cited pages. Look for patterns. Adjust.

For the complete picture of how schema fits into answer engine optimisation, read our AEO guide. For how we use schema as part of broader AI systems, see our pillar guide. For real estate specific schema implementation, check our real estate SEO guide.

If you want a schema audit of your site with a prioritised implementation plan, start here. We will check your current markup, identify gaps, and give you the exact JSON-LD code to add. No guesswork.