Convert question and answer pairs into FAQPage structured data. Mark up an FAQ that readers can already see on your page.
How to use
Enter a JSON array with question and answer strings, then copy the generated JSON into an appropriate structured data script on the matching page.
Example
Use [{"question":"Is booking required?","answer":"Yes, book before visiting."}] for a visible answer with the same meaning.
FAQ
Will Google show an FAQ rich result?
No. Google stopped showing FAQ rich results on May 7, 2026. The markup still describes question and answer content, but it does not restore that search feature.
Related tools
Google Search: FAQ rich result update
A practical task
Keep the markup aligned with the visible FAQ after every edit. If a cancellation rule changes on the page, update its structured answer too. Do not use the markup to publish a longer or more favorable answer than readers can see.
Another useful question
Does adding questions increase search eligibility now?
Google no longer shows FAQ rich results. Use the format to describe genuine visible questions, not as a promise of extra search features.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Structured data | Structured data describes entities and facts in a machine readable format. It must match visible page content. A valid JSON document is not proof of eligibility for a search feature or a promise of richer display. |
| Strict JSON syntax | JSON needs double quotes around keys and string values. Objects use braces and arrays use square brackets. Comments and trailing commas belong to other formats, so remove them before treating a source as JSON. |
| Strings and values | The JSON string "12" differs from the number 12, and "false" differs from false. Type changes affect comparisons and imports. Keep identifiers as strings when their leading zeros or exact digits matter. |
| Syntax and schema | A document can be syntactically valid yet contain the wrong fields or types for an application. Syntax checks confirm the format; schema and business rules determine if the receiving system can use the data. |
| Visible FAQ content | A useful FAQ answers questions that remain after the main instructions. Keep answers specific and based on real facts. Adding FAQ markup does not compensate for an unanswered question or an inaccurate service policy. |
| Metadata and page content | A title and description should summarize the page a visitor will actually find. Search engines can choose other wording for a query. Clear, distinct summaries are more useful than repeating a keyword in every available field. |