If you want to increase the chances of AI quoting your page, combine visible Q&A blocks with proper `FAQPage` schema. Models and search engines can more easily map the question to a specific answer. In practice, check: the question in H2/H3, the answer in the first 40-80 words, visible text on the page, JSON-LD `FAQPage`, no repetitions, and the current modification date.
Template to copy:
> If [the customer asks a specific question], answer first in [1-2 sentences], then add [details, conditions, examples], and mark it in JSON-LD as [FAQPage / Question / Answer], because [AI needs a question-answer pair, not a wall of text]. In practice, check [content visibility, JSON-LD compliance with the text, lack of advertising, and currency].
The customer asks Google or ChatGPT: "Can I return shoes after trying them on?" If your page only has a policy spread over 12 screens, AI might choose a competitor with a short answer. If you have a FAQ block with a clear answer and the same text in `FAQPage` schema, you have better material for citation.
Key takeaways
- FAQ schema does not guarantee visibility in AI Overviews. Google states that there are no special requirements for AI Overviews beyond good SEO basics.
- Classic FAQ rich results on Google are mainly limited to well-known authoritative health and government sites.
- Despite this,
FAQPageremains useful as machine-readable structure: it clearly links questions to single answers. - Answer Capsule is a visible block on the page: a question, a short answer, details, limitations, and possibly an example.
- At Audit AI, we check two separate elements:
FAQPage schemaandAnswer Capsules (Q&A blocks).
Why This Matters in 2026
Google Search Central describes AI features as follows: best SEO practices remain important, and there are no additional requirements just to appear in AI Overviews or AI Mode. This statement is important because it cools promises like "add schema and you'll have an AI Overview."
At the same time, Google documentation for FAQPage precisely outlines how to mark questions and answers: FAQPage contains a list of Question, and each Question has an acceptedAnswer of type Answer. Google also requires that FAQ content be visible to users on the page. This is a practical tip: it's not enough to hide JSON-LD in the code.
Polish SEO sources are moving in a similar direction. Evolve Poznań describes AEO as creating unambiguous answers to user questions that AI can more easily utilize. KS discusses the principle of short answers under headings, meaning an answer in 1-2 sentences before you expand.
Conclusion for small business owners: do not build FAQs just for Google. Build answers for customers, adding schema so that machines don’t have to guess which sentence answers which question.
FAQ schema vs Answer Capsules
FAQ schema is structural data. It is most often added as JSON-LD in the <head> or in the body of the page.
Answer Capsule is visible content. It is a small block of answers that can be read without context.
| Element | What it does | Where it lives | Biggest mistake | | -------------- | --------------------------------------------------- | -------------------------------- | ----------------------------- | | FAQ schema | Marks questions and answers for machines | JSON-LD in the code | schema does not match content | | Answer Capsule | Provides humans and AI with a short answer | visible page content | answer is too general | | QAPage | Describes a page with one question and user answers | forums, Q&A, support | using it on a regular FAQ | | Direct Answer | Answers immediately under the heading | first 40-80 words of the section | too long introduction |
Google distinguishes between FAQPage and QAPage. FAQPage is for questions and answers prepared by the website owner, without alternative user answers. QAPage is for forum or support-type pages where users can add answers to a single question.
Step by step: how to create quotable Q&A
- Choose questions from real customer decisionsBad"Why should you choose our company?"Better"Can I return shoes after trying them on at home?"
The question should pertain to decisions, not self-promotion. The customer asks about price, delivery, returns, timing, risks, contraindications, guarantees, size, location, or differences between options.
For a cosmetics store, a good question might be: "Is SPF 50 cream suitable under makeup?" For a physiotherapist: "Can I come for sports massage with acute back pain?" These are questions that AI may receive from a customer.
- Start the answer with specifics
Bad:
Returns are a very important aspect of customer service and we strive to make the process as convenient as possible.
Better:
Yes, you can return shoes after trying them on at home within 30 days, as long as they haven't been worn outside and you send them back in the original box.
The first sentence should directly answer the question. Only then add conditions, examples, or links to the policy. This is exactly what an Answer Capsule does.
- Add a condition or limitationBad"The product is suitable for everyone."Better"The product is good for dry and normal skin, but we do not recommend it if there is active irritation from cosmetic procedures."
AI likes short answers, but short does not mean unconditional. Limitations build credibility. If you run a clinic, salon, or a store selling supplements, limitations are essential.
Example for a service:
Sports massage can help relieve muscle tension after training, but it is not a good choice for fresh injuries, fever, or acute inflammation. In such cases, first consult a doctor or physiotherapist.
- Mark visible FAQs as JSON-LDBadFAQ is only in an accordion, and JSON-LD contains different questions.Betterthe questions and answers in JSON-LD are the same text that users see on the page.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Can I return shoes after trying them on at home?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, you can return shoes after trying them on at home within 30 days, as long as they haven't been worn outside and you send them back in the original box." } }, { "@type": "Question", "name": "Is SPF 50 cream suitable under makeup?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, SPF 50 cream is suitable under makeup if you apply a thin layer and wait 5-10 minutes before applying foundation. For oily skin, choose a lighter formula." } } ] } </script>Google allows basic HTML in responses, but to start, stick to simple text. Fewer elements can malfunction.
- Do not use `FAQPage` where `QAPage` fitsBada forum with multiple user answers marked as `FAQPage`.Bettera page with a single question and community answers uses `QAPage`, while a classic FAQ section uses `FAQPage`.
If you have a store, blog, service page, or landing page, you will almost always use `FAQPage`. If you run a forum, knowledge base with user answers, or support community, check `QAPage`.
This is important because Google explicitly mentions in the documentation for `QAPage`: do not use `QAPage` for a regular FAQ, blog post, or guide answering a question.
- Implementation in WordPressBadyou paste JSON-LD into the editor as regular text and show it to users.Betteryou add schema via an SEO/schema plugin or through a safe code block in the header of the page.
If you are using a plugin like Rank Math, Yoast SEO, SEOPress, or a dedicated schema plugin, check if the generated JSON-LD contains `FAQPage`, `Question`, `acceptedAnswer`, and `Answer`. Do not assume that a simple FAQ block in the editor always creates schema.
If you're adding it manually through a theme, the direction looks like this:
add_action('wp_head', function () { if (!is_page('faq-delivery-and-returns')) { return; } ?> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How long does delivery take?", "acceptedAnswer": { "@type": "Answer", "text": "Delivery by courier usually takes 24-48 hours from the time the package is sent." } } ] } </script> <?php });This is an example for a developer. If you do not edit `functions.php`, use a plugin or a field for code in the header.
- Implementation in ShoperBadFAQ is an image or description without headings.Betterquestions are visible as text on the product, category, or help page, and you add JSON-LD through a space for custom code if your template or application allows it.
In Shoper, start with content you can edit without code:
### Will the product arrive before Friday? Yes, if you order by Wednesday at 13:00 and choose a courier. Delivery usually takes 24-48 hours.
Then add the corresponding JSON-LD in a place where the store allows you to paste your HTML/JS code for that page or template. If you don’t have such access, pass the JSON-LD to the person handling your template.
Do not paste one global FAQ on all products. Google warns that repeating FAQs should only be marked once within the website. For products, use questions that are truly related to that specific product.
Ready templates
Answer Capsule template:
### [Customer's question?] [Answer yes/no or specifics in the first sentence]. [Condition, number, price, time, or limitation]. [What the customer should do next].
Example for a store:
### Can I return shoes after trying them on? Yes, you can return shoes after trying them on at home within 30 days, as long as they haven't been worn outside. Send them back in the original box and keep the proof of shipping.
Example for a service:
### Is hydrogen cleansing good for sensitive skin? It can be good for sensitive skin, provided you have no active inflammation or fresh irritation. The beautician should conduct a brief interview and adjust the treatment's intensity beforehand.
Implementation checklist
- Choose 5-8 real customer questions.
- Write each question as a complete sentence starting with "can", "how", "what", "when", or "for whom".
- Answer with the first sentence without an introduction.
- Add one number, condition, deadline, price, or limitation.
- Do not use FAQ for advertising.
- Do not promise results you cannot prove.
- Ensure the FAQ is visible to users.
- Do not add questions in JSON-LD that do not appear on the page.
- Use `FAQPage` for classic FAQs.
- Use `QAPage` only for pages with a single question and user answers.
- Add `Question.name` as the full question.
- Add `acceptedAnswer.text` as the full answer.
- Check JSON-LD in the Rich Results Test.
- Check for errors in Search Console.
- Update the FAQ after any change in pricing, delivery, returns, or policies.
- Remove duplicate FAQs repeated across multiple pages.
- Add Answer Capsules on product, category, and service pages.
- Run an audit on `auditai.cc` and check `FAQ schema` and `Answer Capsules`.
7-day mini plan
write down 20 questions from emails, chats, phone calls, contact forms, and Google Search Console.
select 5 questions for one product page, category, or service.
write answers in Answer Capsule format: specifics in the first sentence, condition in the second.
add the FAQ as visible text on the page.
add JSON-LD `FAQPage` matching the visible content.
test Rich Results Test, Search Console, and manually check the HTML.
run [Audit AI](https://auditai.cc), fix errors, and save the template for future pages.
Common mistakes
<script type="application/ld+json">
{
"@type": "FAQPage",
"mainEntity": [...]
}
</script>{
"@type": "QAPage"
}Our company has been providing top-notch customer service for years...
Returns usually take 3-5 business days from the moment the package returns to the warehouse.
How to measure the effects
The first signal: Audit AI detects FAQPage schema and good Answer Capsules.
The second signal: Rich Results Test shows no errors in FAQPage, even if Google does not show a rich result.
The third signal: Search Console reports no structural data errors for FAQs.
The fourth signal: manual test in ChatGPT, Gemini, or Perplexity with the page URL returns correct answers to FAQ questions. This tests readability, not a guarantee of citation.
The fifth signal: customers ask fewer and fewer of the same basic things: delivery, returns, size, service time, contraindications.
Who this advice is not good for
Do not start with FAQ schema if the page has outdated pricing, incorrect policies, or conflicting delivery information. Schema does not fix content. It only describes content.
Do not use FAQ schema for aggressive marketing, artificial keyword stuffing, or hiding text from users. This could be detrimental.
Do not assume that FAQ schema will give a rich result. Google limits FAQ rich results mainly to well-known authoritative government and health sites. For a small business, the main value is clarity for AI, customers, and technical audit.
FAQ
Does FAQ schema still make sense in 2026?
How many questions should an FAQ have?
Can answers be hidden in an accordion?
Must FAQ be identical in HTML and JSON-LD?
Can I add FAQ on a product page?
Summary
FAQ Schema and Answer Capsules are not a magical route to AI Overview. They are a means to ensure your page answers clearly, and machines see the question-answer relationship.
Start with 5 real customer questions, write short answers with specifics, display them on the page, and add matching JSON-LD. Then check the result on auditai.cc before implementing this schema on subsequent pages.
