Ask real questions
Take them from support tickets, sales calls and search suggestions, in your customers’ words.
Turn your questions and answers into valid FAQPage JSON-LD. Type them in or paste a whole list, then copy the schema and a matching HTML accordion, so the markup and the visible page always agree. Free, no sign-up, and nothing leaves your browser.
Google no longer shows FAQ rich results. Read what that means.Works with Q: and A: lines, Question | Answer or a tab on each line, or blocks separated by a blank line where the first line is the question.
Also used as the heading in the HTML accordion.
FAQ schema is structured data, based on the schema.org FAQPage type, that marks up the questions and answers on a page. Each question is a Question with a name, and its answer is an Answer with a text, all inside the page’s mainEntity.
The markup lets search engines and other tools read your Q&A content directly instead of guessing it from the page layout. It describes the content; it does not change what visitors see.
FAQ schema is also called FAQPage schema, FAQ markup or FAQ structured data. All of these mean the same JSON-LD that this generator produces.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is your return policy?",
"acceptedAnswer": {
"@type": "Answer",
"text": "You can return unused items within 30 days of delivery for a full refund."
}
},
{
"@type": "Question",
"name": "Do you ship internationally?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, we ship to more than 50 countries."
}
}
]
}No. Google limited FAQ rich results to well-known government and health sites in August 2023, and stopped showing them in Search on 7 May 2026. Reporting and testing support in Search Console and the Rich Results Test followed.
The markup itself was not deprecated. FAQPage is still valid schema.org vocabulary, and Google has said unused structured data causes no problems in Search, so there is no need to remove accurate FAQ markup. Other search engines, site search and content tools can still read it.
For AI Overviews and AI Mode, Google says no special markup is needed. What helps there is clear, visible question-and-answer content, which is why this generator also gives you a matching HTML accordion.
It is optional. Add it when it accurately describes real Q&A on the page, and skip it when you were only adding it for the old Google snippet.
When the page has genuine FAQs
When it only chases a search feature
Both mark up questions and answers. The difference is who writes the answers.
<section class="faq">
<h2>Shipping and returns FAQs</h2>
<details>
<summary>What is your return policy?</summary>
<p>You can return unused items within
30 days of delivery for a full refund.</p>
</details>
<details>
<summary>Do you ship internationally?</summary>
<p>Yes, we ship to more than 50 countries.</p>
</details>
</section>The markup is only as useful as the content behind it. These four habits matter more than any schema.
Take them from support tickets, sales calls and search suggestions, in your customers’ words.
Lead with the direct answer, then add detail. Short, self-contained answers are easy to quote.
The schema text should be the same as the visible answer. The HTML tab keeps them in sync.
Update the page and the markup together, and remove questions that no longer apply.
The generator above writes both the markup and the visible HTML. These four steps take them live.
Type each question and answer, or paste the whole list at once.
Use the HTML tab if the page does not show the FAQs yet.
Copy the script tag, or download the JSON file.
Add both to the page, then check the markup in the Schema.org validator.
Use one FAQPage block per page. Google’s Rich Results Test no longer checks FAQ markup, so use validator.schema.org or our Schema Markup Validator instead. On WordPress, Yoast and Rank Math FAQ blocks add this markup automatically, so check your page source before adding another copy.
Short answers on Google’s changes, validation and best practice.
FAQPage schema marks up the questions and answers on a page as structured JSON-LD, so search engines and other tools can read them directly. It describes the content and does not change what visitors see.
No. Google limited FAQ rich results to well-known government and health sites in August 2023, then stopped showing them in Search on 7 May 2026. FAQPage is still valid schema.org markup, and existing markup can stay on the page.
There is no need to, as long as it accurately describes questions and answers visible on the page. Google has said unused structured data causes no problems. Remove it only where it describes content that is no longer on the page.
Google says AI Overviews and AI Mode need no special markup, so FAQ schema is not a way into them. Clear, visible question-and-answer content matters most, and the markup does not guarantee being cited.
Use the Schema Markup Validator at validator.schema.org or the Search Savvy Schema Markup Validator. Google’s Rich Results Test no longer supports FAQ markup.
FAQPage is for questions answered by the site owner, such as a help page. QAPage is for a single question with answers submitted by users, such as a forum thread.
There is no fixed limit. Include every question and answer that is visible on the page, and nothing that is not.
Yes. Open “Paste a whole list instead” and paste Q: and A: lines, Question | Answer lines, tab-separated rows from a spreadsheet, or blocks separated by blank lines.
Structured data must match content visitors can see. The HTML tab produces an accessible accordion with the same questions and answers, so the page and the markup never drift apart.
Yes. It is completely free, with no sign-up and no limit. Everything runs in your browser, so your content is never uploaded to a server.
If you added FAQ markup for search features, these types still have rich results in Google.
Search Savvy audits your schema, removes what no longer helps and implements the types that still earn rich results and clear answers.