Content
Turn your FAQs into schema AI engines can quote
Add your questions and answers and copy both the FAQPage JSON-LD and clean HTML. FAQ content is some of the most cited by AI answer engines.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": []
}
</script><!-- Add a question and answer to generate HTML -->Publish both: the JSON-LD gives AI engines a clean, machine-readable answer, and the HTML shows the same content to readers.
Why FAQ schema helps you get cited in AI answers
Google retired FAQ rich results on 7 May 2026, and most advice about FAQ markup has not caught up. If the accordion in the search result was your only reason for adding it, that reason is gone.
The reason that survives is extraction. An answer engine builds a response by lifting short passages that map onto a question, and FAQ markup hands it that shape directly: a question string, and an answer that stands alone without needing the paragraph above it for context. The same fact buried mid-section in prose forces the engine to cut the passage itself, and it either cuts badly or skips you for a page that already did the work.
This is the practical reason FAQ blocks turn up so often in cited sources. Engines are not rewarding the markup. The format already matches how they read.
Before and after
The same two facts, written both ways. The first is how most pages answer the question. The second is what the form above produces.
<p>
Pricing depends on how many sites you track. Most teams start on
the smaller plan and move up when they add a second domain, and
there is a trial before any of that so you can see it working
first.
</p>
<section class="faq">
<details>
<summary>Is there a free trial?</summary>
<p>Yes. Every plan includes a free trial, and no card is required to start it.</p>
</details>
<details>
<summary>How many sites can I track?</summary>
<p>One site on the smaller plan. Add a second domain by moving up a tier.</p>
</details>
</section>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Is there a free trial?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Every plan includes a free trial, and no card is required to start it."
}
},
{
"@type": "Question",
"name": "How many sites can I track?",
"acceptedAnswer": {
"@type": "Answer",
"text": "One site on the smaller plan. Add a second domain by moving up a tier."
}
}
]
}
</script>
The answer text in the JSON-LD has to match the answer a reader sees. Markup describing content that is not on the page breaches Google's structured data policy, which is why the form gives you both outputs from the same input.
FAQ schema questions
Google removed FAQ rich results. Is FAQ schema still worth adding?
Yes, for a different reason than before. The rich result is gone. The extraction benefit is not. Answer engines read the markup to find question and answer pairs, and a page offering them in that shape is easier to quote than one that does not. The cost is a block of JSON, and the downside case is that nothing happens.
How many questions should a page have?
Three to eight, and every one of them a question a buyer has asked out loud. Padding the list with questions nobody asks dilutes the page and gives an engine more chances to quote something irrelevant. Take them from sales calls and support tickets before you take them from a keyword tool.
Do the questions have to be visible on the page?
Yes. Markup describing content a reader cannot see breaches Google's structured data policy and risks a manual action. That is the reason the form hands you HTML alongside the JSON-LD: publish both, generated from the same answers.
Where should the FAQ block sit on the page?
Below the main content and above the footer. The exception is a page whose whole job is answering one question, where the answer belongs in the first hundred words and the FAQ block picks up the follow-ups.
Previews the Content Agent
Write a few FAQs here, or let the Content Agent draft the full set in your brand voice, publish them, and prove what they did to your traffic.