JSON-LD FAQ Generator

Questions and answers

One pair per line as 'Question | Answer'.

Result

The markup<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Как посчитать процент от числа?", "acceptedAnswer": { "@type": "Answer", "text": "Умножьте число на процент и разделите на сто: 15 % от 200 — это 200 × 15 ÷ 100 = 30." } }, { "@type": "Question", "name": "Как найти, сколько процентов одно число от другого?", "acceptedAnswer": { "@type": "Answer", "text": "Разделите первое на второе и умножьте на сто." } } ] } </script>
Questions2
Answer checkThe answers are substantial enough.
Average answer length65
First questionКак посчитать процент от числа?
What mattersThe markup has to mirror text that is actually visible on the page: a hidden FAQ is a violation and loses the rich result.

The markup has to mirror visible text

Builds FAQPage structured data in JSON-LD from a list of questions and answers, ready to paste into a page.

FAQPage markup tells a search engine that a page carries a block of questions and answers. It used to earn an expandable rich result; today that appears selectively, but the markup still helps an engine understand the page's structure.

The key requirement is correspondence. Questions and answers in the markup have to match what a visitor actually sees. Markup without a visible block is a violation, and it costs a site its rich results across the board.

What this calculator shows

A ready JSON-LD block for the head or the end of the body
The number of questions and the average answer length
A check on whether the answers are too thin

What to keep in mind

The input format is one pair per line: question, a vertical bar, answer.
Quotes and line breaks in answers are escaped automatically so the JSON stays valid.

FAQs

Where does the markup go?

In the head or at the end of the body — the engine does not mind. What matters is that the script arrives in the source HTML rather than being drawn in by client-side JavaScript.

Does the FAQ have to be visible on the page?

Yes. Markup without a visible counterpart breaks the rules, and it costs a site its rich results site-wide.

How many questions should I mark up?

As many as genuinely exist on the page — usually four to six substantial ones. Padding the list serves no purpose.

Does FAQ markup still work?

Google has shown the rich result selectively since 2023, mostly for authoritative sites. The markup remains useful for conveying page structure.

Worked example

Two questions about percentages

Input: Two lines in 'Question | Answer' form

Output: A FAQPage block with two Question entries

Note: Both answers run past forty characters, which is enough for a rich result. One-word answers like 'Yes' do not break the markup, but they will never earn a place in the results either.

Useful links

All tools in Dev Tools

JSON-LD FAQ Generator

Result

Related tools

Meta Tag Length Checker

Open Graph Generator

Robots.txt Generator

Useful links