Are We Agent Ready? — the Agent Readiness audit platform

Standard · recommendation

FAQPage schema

If you have an FAQ section, mark it up with FAQPage + Question/Answer JSON-LD. Highest-leverage AEO win — directly fuels Google AI Overviews and ChatGPT search citations.

Get your free Agent Readiness Score Upgrade to Pro — $49/year

What is FAQPage schema markup?

FAQPage schema is a JSON-LD markup format that tells search engines and AI systems "this page contains a list of frequently asked questions." You embed it in your HTML—usually in a <script type="application/ld+json"> tag—and declare an array of questions with their corresponding answers. The markup follows the FAQPage vocabulary from schema.org, the same structured-data standard that powers Google's rich snippets.

Technically, you create a JSON-LD object with @type: "FAQPage" and a mainEntity array. Each item is a Question object with a name (the question text) and an acceptedAnswer of type Answer containing the response. Minimum viable implementation is three questions. The questions must be phrased in natural language—"How do I cancel my subscription?" not "Cancellation"—and answers must be self-contained, meaning they make sense without reading the surrounding page.

Why does FAQPage schema matter for AI agents and answer engines?

AI systems scraping the web for answers—ChatGPT search, Perplexity, Google AI Overviews, Claude with web access—are trained to recognize structured data. FAQPage markup is the single highest-leverage schema type for question-answering flows. When ChatGPT or Perplexity encounters a well-marked FAQ, it can extract the exact question-answer pair and cite your page directly. Without the markup, the same content might be buried in paragraph tags or table rows, forcing the model to guess what's a question and what's an answer. That ambiguity lowers your citation rate.

The business outcome is straightforward: if your FAQ answers "How do I return a product?" and it's marked up correctly, an agent can surface that answer inline and link to your page as the source. If it's unmarked, the agent might hallucinate a policy from a competitor's page or skip you entirely. This matters for support deflection (fewer tickets), commerce flows (fewer abandoned carts due to unanswered questions), and brand authority (you get the citation, not a third-party review site).

Is FAQPage schema required, recommended, or optional for my site?

This check is recommended for any site that publishes an FAQ section—SaaS products, e-commerce stores, documentation hubs, service businesses. It's not legally required, and your site won't break without it, but the effort-to-reward ratio is unusually favorable. Two hours of work can materially increase your citation rate in AI-assisted search.

The recommendation weakens if you have no FAQ content at all, or if your FAQ is paywalled or gated behind authentication (agents typically can't index protected content). It also matters less if your primary traffic comes from branded queries where users land directly on your homepage, though even there, agents doing research on your behalf benefit from the markup.

What the FAQPage schema standard says

The schema.org FAQPage spec is maintained by the Schema.org community and recognized by Google, Microsoft, Yandex, and other search engines. Key requirements:

Minimal valid example:

What good FAQPage schema implementation looks like

Zapier publishes FAQPage markup on their pricing FAQ, covering questions like "Can I change my plan later?" and "What happens if I go over my task limit?" They embed the JSON-LD in the page head and ensure answers are complete sentences, not fragments.

Stripe's documentation FAQ sections mark up developer-focused questions like "How do I test webhooks locally?" with code snippets included in the answer text field. The answers don't assume you've read the prior paragraph—they're genuinely self-contained.

How do I add FAQPage schema to my website?

1. Identify your FAQ content. If you have a dedicated /faq page, start there. If FAQs are scattered across product pages or docs, prioritize the most-trafficked ones.

2. Draft the JSON-LD. Use the minimal example above as a template. Replace placeholder questions and answers with your real content. Ensure each answer is at least one complete sentence.

3. Embed in your HTML. Add a <script type="application/ld+json"> tag in the <head> or at the end of <body>:

4. If you're using Next.js, add the JSON-LD to your page component's <Head> or use next-seo's FAQPageJsonLd component. For static site generators like Hugo or Jekyll, template the JSON-LD in your FAQ page layout.

5. Validate with Google's Rich Results Test to catch syntax errors.

How can I test my FAQPage schema implementation?

Look for "@type": "FAQPage" in the output. If it's missing, the markup isn't present or isn't valid JSON-LD.

Or just run a free scan and we'll check this for you alongside 30+ other agent-readiness signals.

Frequently asked questions

Does FAQPage schema still work if my FAQ uses an accordion or expandable UI?

Yes. The visual presentation doesn't matter—you can use accordions, tabs, or plain HTML. What matters is that the JSON-LD markup contains the full question and answer text. AI agents read the structured data, not the DOM. Just ensure your acceptedAnswer text matches what users see when they expand the accordion.

Can I use FAQPage schema on a SaaS pricing page that includes a few common questions?

Absolutely. Many SaaS companies add FAQPage schema to pricing pages to mark up questions like "Can I cancel anytime?" or "What payment methods do you accept?" This helps AI agents surface pricing FAQs when users research your product, increasing citation likelihood in tools like Perplexity or ChatGPT search.

Is FAQPage schema the same as the QAPage schema type?

No. FAQPage is for pages where *you* publish a curated list of questions with official answers. QAPage is for community Q&A platforms like Stack Overflow, where multiple users post questions and answers. Use FAQPage for owned FAQ sections; use QAPage for forum threads or user-generated Q&A.

Will Google show rich snippets for my FAQ if I add FAQPage schema?

Possibly, but not guaranteed. Google uses FAQPage schema as an eligibility signal for rich results, but final inclusion depends on content quality, page authority, and query intent. AI agents like ChatGPT and Perplexity consume the markup more reliably than Google displays rich snippets, so the agent-readiness benefit is often larger.

Do e-commerce product pages need FAQPage schema, or is it only for dedicated FAQ pages?

You can use FAQPage schema on product pages if they include a product-specific FAQ section (e.g., "Is this dishwasher safe?" or "What sizes are available?"). It works alongside Product schema. Many e-commerce sites embed both schema types on the same page to maximize structured data coverage.

Can I auto-generate FAQPage schema from my existing FAQ HTML, or do I need to hand-code it?

You can auto-generate it. Tools like schema-dts (TypeScript), WordPress plugins (Yoast, RankMath), and headless CMS integrations (Contentful, Sanity) can extract FAQ content from your CMS and output valid JSON-LD. Just validate the output with Google's Rich Results Test to confirm it's spec-compliant.

Does FAQPage schema help with voice search or smart assistants like Alexa?

Indirectly. Voice assistants often pull answers from search engines that index structured data, so well-marked FAQs increase your odds of being selected as a source. However, voice assistants also use proprietary knowledge graphs and may not cite your page audibly. The clearer win is citation in text-based AI tools.

How does FAQPage schema work with Next.js or other server-side rendering frameworks?

In Next.js, you can inject JSON-LD in the <Head> component using dangerouslySetInnerHTML, or use libraries like next-seo which provide a FAQPageJsonLd component. Server-side rendering ensures the markup is present in the initial HTML, so crawlers and AI agents see it immediately without JavaScript execution.

← Back to all standards