
Generate FAQPage JSON-LD from real question-and-answer pairs, avoid placeholder text, and set honest expectations about rich results.
Structured data is a labelled summary of a page that machines can read: this block is a question, that block is its answer. Writing the JSON by hand invites missing commas and mismatched brackets. Schema Generator builds valid FAQPage markup from the questions you type, and hands you a ready-to-paste script tag.
The short version: pick FAQ Page, replace the sample questions with your own, copy the script tag, paste it into the page, and test the live URL. The clip below walks through generating JSON-LD.
Take a small shop, Harbour Street Cycles, with a repair page that already shows three questions to customers. The markup should describe those same three questions and nothing else.
Choose FAQ Page in the Schema Type menu. The form opens with two sample rows about another site, which you must replace. This is the easiest mistake to make: leave the defaults in place and your page declares answers that appear nowhere on it.
Type the three pairs:
Use the Add Question button for the third row. The generated panel then shows a JSON object with "@context": "https://schema.org" and "@type": "FAQPage", and a mainEntity list holding three Question objects. Each has a name (the question) and an acceptedAnswer of type Answer with a text field. Press Copy as Script Tag and the clipboard holds that JSON wrapped in <script type="application/ld+json">.
Paste the script tag into the HTML of the page it describes, in either the head or the body. It is invisible to visitors. Wording must match the visible page: if the page says "two working days", the markup should too. When you edit the page copy later, update the markup in the same sitting, since stale structured data is a common reason for it being ignored.
Markup describes a page; it does not guarantee a special listing. Google has said it now shows FAQ rich results only for a limited set of well-known authoritative sites, so a small business should not expect expanded results from this alone. The tool's own note says the same: structured data helps search engines understand a page, with no promise of a special result. Reasonable reasons to add it anyway are tidier machine-readable content, and a page that is easy to audit later. If someone promises guaranteed rankings from schema, be sceptical.
Rules that hold regardless of rewards: only mark up questions that are visible on the page, write answers as plain text, and do not use FAQ markup for advertising copy. Keep </script> out of your answers, since the tool writes your text as typed. Quotation marks and line breaks are escaped for you in the JSON.
The same menu offers Article, Product, Local Business and Recipe, each with its own fields. A few specifics worth knowing:
PT15M to work out total time. A value in another format counts as zero.Fill the right type for the right page. A shop page with a single product is a Product; the shop's contact page is a Local Business; this guide's page would be an Article.
If you want to look at the object in a more readable layout or confirm that your edits still parse, JSON Formatter validates and indents it. Titles and descriptions belong in Meta Tag Generator, and crawl rules plus a sitemap come from Robots Sitemap, which has its own launch-day guide. The rest of the toolkit is in SEO tools.
The generator builds everything in your browser from the fields you fill in, and only the copy action counts as a trial use, so you can adjust the text as often as you like before copying. Keep a text copy of your questions and answers beside the page source; it makes later updates quick.
Which page on your site has a real FAQ that is not marked up yet, and what do customers ask most? Tell us on the contact page.