Meta Tag Generator
Fill four fields and copy a block of head meta tags.
Paste Q: and A: lines and copy a FAQPage JSON-LD script. Note: Google retired FAQ rich results in 2026, so this is for understanding, not the old accordion.
Your browser is preparing the tool. It runs 100% locally.
Paste your questions and answers as Q: and A: lines and the tool builds FAQPage JSON-LD: a mainEntity list of Question and Answer pairs, ready to paste into your page. Note that Google stopped showing FAQ rich results (the expandable accordion in search) on 7 May 2026, so this markup no longer earns that feature for normal sites. FAQPage is still valid schema.org and can help search engines and AI understand your page. Your browser does all the work.
Enter any number of question-and-answer pairs, one Q: line followed by its A: line, and the tool assembles them into a single FAQPage object, where each pair becomes a Question with an acceptedAnswer, wrapped in a JSON-LD script you copy into the page.
Here is what that markup gets you now. Until 2023, FAQPage markup could show an expandable FAQ directly in Google's results; Google then limited that to government and health sites, and on 7 May 2026 removed the FAQ rich result entirely. The markup is still valid and Google says it keeps using FAQ data to understand pages, but the visible accordion is gone.
The tool reads your text line by line: a line starting with Q: opens a question, the next line starting with A: supplies its answer, and the pair is added to the FAQPage's mainEntity list. It repeats for every pair and wraps the lot in an application/ld+json script.
The output follows schema.org's FAQPage shape: Question objects, each holding an acceptedAnswer of type Answer. That part has not changed. Google has only stopped rendering it as a rich result.
a FAQPage with a mainEntity list, one entry per pair:
Question (name = your question)
acceptedAnswer = an Answer (text = your answer)Unlimited question-and-answer pairs (the type dropdown in the general schema tool caps FAQPage at two). Since 7 May 2026 Google no longer shows this as a rich result, but the markup is still valid schema.org.
| Input | Q: and A: line pairs (any number) |
|---|---|
| Output | FAQPage JSON-LD (application/ld+json) |
| Structure | mainEntity list of Question and acceptedAnswer Answer |
| Rich result | retired by Google (7 May 2026) |
| Markup validity | still valid schema.org |
| Placement | in the head or body of the page |
| Where it runs | In your browser, nothing uploaded |
The main reason people added FAQ markup, the expandable FAQ in Google's results, is gone. Google limited it to authoritative government and health sites in August 2023 and dropped it for all sites on 7 May 2026, with the report and Rich Results Test support following in mid-2026. Do not add this expecting the accordion.
The markup is still valid and not harmful. Google has said it continues to use FAQ structured data to understand a page, and FAQ content can help with AI-driven and conversational search, so there is a case for keeping it, though not for the old rich result.
The questions and answers must be visible on the page. FAQPage markup for question-and-answer pairs that a visitor cannot see violates Google's guidelines. Mark up a real, on-page FAQ section only.
It pairs strictly by line: a Q: line then an A: line. A question without a following answer, or stray formatting, is skipped, so keep one question and one answer per line, in order.
It does not validate or de-duplicate. Run the output through a structured-data validator, and make sure each answer matches its question and the page.
Mark up a visible FAQ so engines and AI assistants can parse the questions cleanly.
Structure a support or help page's questions and answers as machine-readable data.
Add FAQPage data to a visible product FAQ for clearer comprehension.
Convert an on-page FAQ into JSON-LD to keep the structured data current.
Wanted the search accordion? It no longer exists for normal sites, so put the effort into a clear on-page FAQ. Need other schema types? Use the schema markup generator. Adding a breadcrumb? Use the breadcrumb schema generator.
Builds valid FAQPage JSON-LD from question-and-answer lines, but states the current reality plainly: Google retired the FAQ rich result on 7 May 2026, so this is for understanding and AI, not the old search accordion.
Fill four fields and copy a block of head meta tags.
Top words in your content and the share each one takes.
Add utm_source, utm_medium and utm_campaign to any URL.
Write the og: tags that control link previews on social apps.
See roughly how a title and description could look in Google.
schema.org JSON-LD for articles, products, FAQs and more.
It's free, needs no account, and nothing you enter is sent to a server.