Free FAQ schema generator
- No signup
- Free
- Results in ~5 seconds
Missing required fields
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage"
}
</script>In Rank Math or Yoast, open the schema or custom code box and paste this. Or use WPCode to add a header snippet on that page only.
Want schema across the whole site, with an @graph and entity links? That is part of my technical SEO service.
FAQ schema is a list of questions and answers that are already on the page. Google no longer shows the old FAQ dropdown. The markup is still worth adding when the questions are real and visible.
When FAQ schema still makes sense
Use it when the page answers questions a buyer actually asks, and those questions are on the page in text a person can read. A pricing page, a service page, and a location page are the usual places. A blog post can use it too, if the answers are specific to that post and not a generic block you paste everywhere.
Google stopped showing FAQ rich results on 7 May 2026. The Search Central changelog dated 8 May 2026 says so. I do not build pages in the hope that the dropdown comes back. I mark up the questions because an AI system, a screen reader, and your own site search can use a clear question and answer pair.
Skip FAQ schema when you have nothing to say. Five questions that repeat the hero sentence do not help. One honest answer about price, area, or timing is better.
Rules: visible on the page, and not an ad
Every question and every answer in the JSON-LD must appear on the URL. If you hide the FAQ in a tab, the text still needs to be in the HTML, not loaded only after a click that fetches another document. If the generator drafts an answer, check it against the page. The draft is a starting point. You are responsible for what you publish.
Do not mark up reviews, promotions dressed as questions, or a question whose answer is only a link. Keep the list to what is on the page. More than about twenty questions is a sign you are marking up a whole help centre on a single URL. Split the page instead.
The generator escapes quotes so the JSON stays valid. Still paste the result into a validator. A missing comma from a later hand edit is the usual way a valid block becomes invalid.
Examples of questions worth marking up
Write the question the way a customer says it. "How much does a boiler service cost in Leeds?" is better than "Learn about our solutions." The answer should include the fact: the range, what is included, and what is not. If you do not publish a price, do not invent one in the schema.
A second useful pattern is the boundary of the service. "Do you cover York as well as Leeds?" with a straight answer. A third is the practical next step. "How long does the first visit take?" Machines repeat specific sentences. Give them a specific sentence that is also true.
How I write the questions
I take questions from sales calls, from the inbox, and from the way people phrase the service. I do not take them from a keyword list and then invent an answer. If I cannot answer in two or three sentences without leaving the page, the question belongs on its own URL.
Put the questions where a person will read them, usually under the main explanation, not in a footer that is the same on every page. Sitewide FAQ blocks create the same questions on hundreds of URLs. That does not make you look thorough. It makes the markup look copied.
When the generator drafts from a page, I delete anything the page does not say. I also delete soft claims. "We are the leading plumber" is not an answer. "We cover Leeds and we book weekday visits" is an answer.
After you paste the script, check that the questions on the screen and the questions in the JSON are the same list. Editors often update the visible FAQ and forget the script. The next audit then shows answers the business no longer gives.
A good answer names a constraint. Price bands, areas, and timings are useful. Adjectives are not. If the question is "how much", and you do not publish a number, say how you quote instead of inventing a fee. The schema is not a place to test an offer you have not decided.
I keep FAQ markup on the pages where the questions help a buyer choose. I remove it from pages that only exist to rank for a question the business does not want. Eligibility is gone. Usefulness is the remaining reason to bother.
Pair the questions with the service page they belong to, and link that page from the homepage. A FAQ that is only in the schema and not in the navigation is easy to forget. When you change a price or an area, update the visible answer and the script in the same edit. Then validate the live URL, not the draft in the generator.