Structured data that gets you cited: beyond basic schema

Why basic schema is not enough#

Organization, Article, and FAQPage schema cover the fundamentals. They tell AI engines who you are, when you published, and what questions you answer. Most guides stop there. But advanced schema patterns can push your citation rate significantly higher.

Pages with FAQ schema receive roughly 40% more citations than pages without it. Now imagine stacking FAQ schema with Speakable schema, sameAs entity linking, and nested schema types. Each layer gives AI engines more context about your content, your brand, and the specific claims you make.

These advanced patterns are not theoretical. They are used by the top-cited domains across AI platforms. The 30 domains that capture 67% of citations within most topics implement schema at a level most competitors never reach. This guide covers the patterns that separate their implementation from the baseline.

Speakable schema: marking content for voice and AI extraction#

Speakable schema marks specific sections of your content as ideal for text-to-speech and AI extraction. Originally designed for Google Assistant voice search, it signals to any AI system that these blocks are the most concise, self-contained, and citation-worthy parts of your page.

Add Speakable schema to the sections of each page that contain your most direct, citation-ready answers. A 3,000-word guide might have three Speakable blocks: one defining the topic, one answering the most common question, and one providing the key recommendation.

The content within Speakable blocks should be 20-60 words, factually complete, and comprehensible without surrounding context. These are the blocks AI engines will extract and present as citations.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "AI Visibility Guide",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [
      ".citation-block-intro",
      ".citation-block-definition",
      ".citation-block-recommendation"
    ]
  }
}
</script>

<!-- In your HTML, mark citation-ready blocks -->
<p class="citation-block-intro">
  AI visibility measures how often AI search engines cite your brand
  when users ask relevant questions. It covers ChatGPT, Claude,
  Perplexity, Gemini, and other AI platforms.
</p>

sameAs: building your entity graph#

sameAs properties in your Organization schema link your brand to its profiles across the web. AI engines use these links to build a comprehensive entity representation of your brand, connecting your website to your Wikidata entry, Wikipedia page, LinkedIn profile, and other authoritative sources.

Most sites include two or three social media URLs in their sameAs array. The advanced approach includes every authoritative reference to your brand entity across the web: Wikidata, Wikipedia, Crunchbase, LinkedIn, industry directories, review platforms, and government registries.

Each sameAs URL strengthens your entity graph. When AI engines see that your website's sameAs array connects to the same entity on Wikidata, Crunchbase, and three industry directories, they have higher confidence in your entity identity. That confidence translates to more consistent citation behavior.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yourdomain.com",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q123456",
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.crunchbase.com/organization/your-brand",
    "https://www.linkedin.com/company/your-brand",
    "https://twitter.com/yourbrand",
    "https://github.com/yourbrand",
    "https://www.g2.com/products/your-brand",
    "https://www.trustpilot.com/review/yourdomain.com"
  ]
}
</script>

FAQ stacking: multiple schema types on one page#

FAQ stacking combines FAQPage schema with Article schema and, where applicable, HowTo schema on the same page. Each schema type gives AI engines a different extraction pathway. The Article schema provides context and recency. The FAQPage schema provides structured Q&A pairs. The HowTo schema provides step-by-step instructions.

A single page can legitimately carry all three: an Article about implementing schema markup that includes a FAQ section and a step-by-step implementation guide. Each schema type maps to different query patterns. Article schema captures "what is schema markup" queries. FAQPage captures "how much does schema markup cost" queries. HowTo captures "how to add schema markup to my site" queries.

The combined effect is more citation entry points from a single page. Instead of one schema type mapping your page to one query pattern, three types map it to three patterns.

<script type="application/ld+json">
[
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "Schema Markup Implementation Guide",
    "author": { "@type": "Person", "name": "Author Name" },
    "datePublished": "2026-03-15",
    "dateModified": "2026-04-01"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How much does schema markup cost?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Schema markup costs $500-$5,000 for most SMBs."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "HowTo",
    "name": "How to implement schema markup",
    "step": [
      {
        "@type": "HowToStep",
        "name": "Choose schema types",
        "text": "Select Organization, Article, and FAQPage."
      }
    ]
  }
]
</script>

Author entity schema for E-E-A-T#

AI engines evaluate author credibility as part of their citation decisions. Author schema connects your content to a specific expert entity rather than an anonymous publisher.

Create a detailed author profile page on your site with Person schema that includes the author's name, job title, organization, sameAs links to their LinkedIn and other professional profiles, and a description of their expertise.

Then reference this author entity from every Article schema on content they authored. The AI engine can now trace a chain: "This article about AI visibility was written by [Name], who is the [Title] at [Organization], with expertise documented across LinkedIn, industry publications, and speaking engagements."

This chain of entity relationships is how AI engines evaluate E-E-A-T at scale. Anonymous content without author schema cannot demonstrate Experience, Expertise, Authoritativeness, or Trustworthiness through structured data. Named authors with rich entity schemas can.

<!-- Author profile page schema -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jane Smith",
  "jobTitle": "Head of AI Strategy",
  "worksFor": {
    "@type": "Organization",
    "name": "Your Brand"
  },
  "sameAs": [
    "https://linkedin.com/in/janesmith",
    "https://twitter.com/janesmith"
  ],
  "description": "AI visibility strategist with 8 years of experience in search optimization. Published researcher on generative engine optimization."
}
</script>

<!-- Reference author from Article schema -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "author": {
    "@type": "Person",
    "name": "Jane Smith",
    "url": "https://yourdomain.com/team/jane-smith"
  }
}
</script>

Testing and validating advanced schema#

Advanced schema implementations carry higher risk of errors. A single syntax mistake can invalidate the entire schema block, making it invisible to AI engines.

Validate every schema block using Google's Rich Results Test (search.google.com/test/rich-results). It catches structural errors, missing required properties, and invalid values. Test after every change, not just during initial implementation.

Use Schema.org's validator (validator.schema.org) for types that Google's tool does not cover. Some advanced schema patterns (Speakable, nested sameAs arrays) may not generate Rich Results but are still parsed by AI engines.

Check your implementation in Google Search Console under the Enhancements section. Search Console reports schema errors and warnings at the site level, catching issues across all your pages.

Run a BrandCited audit after implementing advanced schema. The audit checks not just whether schema exists but whether AI engines successfully parse and use it for citation decisions. A valid schema that does not affect citation behavior might need content-level improvements to become effective.