FAQ Schema and AI Citations: What the Markup Does, What We Know, How to Add It

FAQPage JSON-LD marks up the question-and-answer pairs on a page in a machine-readable way. Below: what the markup does, what open sources say about it, what nobody knows yet, and how to add it.

What the markup does

FAQPage JSON-LD tells a machine directly: this is a question, this is its answer. A search engine or AI crawler does not have to guess the structure from the layout. It is ordinary Schema.org markup like any other type: it describes the page and promises nothing about how the page is used.

Why it is still worth adding

• For people and search. Questions and answers on a page help visitors whatever the markup. The markup makes them unambiguous for any parser.
• For AI crawlers. The answers sit in the page source, so a crawler that does not run scripts can read them without executing anything. Whether crawlers use them is not known.
• The cost is low. It is one block of code per page, which Causabi generates from your site’s own text.

How to Implement FAQPage JSON-LD

Add this to your <head> or as a <script type="application/ld+json"> block in the page body:

Or build the block with your own questions in the schema markup generator, then run it through the schema validator, which checks the questions against the page text.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is [your product/service]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Clear, complete answer in 2-4 sentences. Include your brand name naturally."
      }
    },
    {
      "@type": "Question",
      "name": "How does [your product] work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Step-by-step explanation. Concrete and specific."
      }
    },
    {
      "@type": "Question",
      "name": "How much does [your product] cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Include pricing tiers or ranges. A specific answer is more useful than a vague one."
      }
    }
  ]
}
</script>

What Questions to Include

The specific questions matter as much as the schema itself. Base your FAQ on how users actually search:

1. What is [your product]? — The definition question. Include your full brand name and primary use case.
2. How does [your product] work? — Mechanism question. Visitors almost always ask it.
3. Who is [your product] for? — Audience question. Tells the reader at once whether the product fits.
4. How much does it cost? — Pricing question. People ask it constantly, and the answer should be specific.
5. What are the main features? — Feature enumeration. Use a list-style answer.
6. What alternatives exist? — Competitive question. An honest answer that names competitors is useful to the reader.
7. How does it compare to [competitor]? — Include 1-2 specific comparisons.
8. Is there a free trial/free tier? — Conversion question.

FAQ Content Quality Rules

The markup alone settles nothing. What matters is the quality of the answers:

• Each answer should be 50-300 words — complete enough to stand alone, short enough to be quoted directly
• First sentence must answer the question directly — no preamble or "Great question!"
• Include specific numbers, names, and facts — a specific answer can be quoted, a vague description cannot
• Don't duplicate the question text in the answer — start with the substance
• Use your brand name naturally in 2-3 answers (not all of them)
• Match the language users actually use, not your internal terminology

Where to Place the FAQ

Place FAQ schema on pages with informational intent, not just your homepage:

• Homepage — general product FAQ (what it is, how it works, pricing)
• Feature pages — feature-specific questions
• Pricing page — FAQ about plans, billing, cancellation
• Blog posts — if the article answers a common question, wrap the key answer in FAQ schema

Avoid adding FAQ schema to pages that are purely transactional (checkout, login) or have no informational content.

Validate and Monitor

After implementation:

1. Validate with schema.org validator — zero errors required
2. Make sure the questions and answers in the markup match the visible text on the page (Google asks this of structured data)
3. See whether AI services mention you with Causabi monitoring — we ask ChatGPT, Gemini, Grok and Claude real questions through their official APIs and report whether your business is mentioned (paid plans)

Other tools

• Causabi schema markup generator — free: builds FAQPage, Organization and LocalBusiness JSON-LD in your browser and checks required fields
• Causabi schema validator — free: JSON-LD errors, and a check of the markup against the visible page text
• Schema.org Markup Generator — free tool to generate FAQPage JSON-LD without coding
• Yoast SEO (WordPress) — includes FAQ block with automatic JSON-LD generation. The shortest path for a WordPress site.
• Rank Math (WordPress) — similar to Yoast, includes schema builder with FAQ support
• Google Rich Results Test — checks other rich result types (search.google.com/test/rich-results); per Google's notice, FAQ support is being dropped

Related reading