FAQ Schema Generator

What happened to FAQ rich results

The timeline, from Google's own announcements:

• August 2023: Google's Search Central post "Changes to HowTo and FAQ rich results" restricted FAQ rich results to well-known, authoritative government and health websites. Every other site lost the expandable questions under its listing.
• 8 May 2026: the Search Central documentation changelog added a deprecation notice: the feature "will no longer appear in Google Search starting May 7, 2026."
• 15 June 2026: the changelog records that FAQ rich results are "no longer shown in Google Search results" and that the FAQ structured data documentation has been removed.

If an agency or plugin still sells FAQ schema as a way to "take up more space in Google", that advice is out of date.

What FAQ schema is still useful for

• Describing the page precisely. Google says structured data provides "explicit clues about the meaning of a page" (structured data introduction). FAQPage is still part of the schema.org vocabulary, and any system that reads JSON-LD can tell which text is a question and which is its answer.
• Keeping your Q&A disciplined. Writing schema forces one clear question per answer, with the full answer visible on the page. Those self-contained blocks are also what AI answer engines tend to quote, but it is the visible text that gets quoted, not the JSON-LD. No major AI search provider has documented using FAQPage markup as a ranking or citation signal.
• Existing markup. There is no need to rip valid FAQPage markup out in a hurry, but stop adding it for a Google feature that no longer exists. If it has drifted out of sync with the visible answers, fix it or remove it.

Our guide on structured data for AI search covers which schema types still affect Google results, such as Product, Organization and LocalBusiness.

How to use the FAQ schema generator

1. Type a question in the Question field and its full answer in the Answer field.
2. Click Add question for each further pair. Rows with an empty question or answer are skipped, so a blank row will not create a broken entry.
3. The JSON-LD updates as you type. Click Copy JSON-LD.
4. The tool outputs only the JSON object. Wrap it in <script type="application/ld+json"> … </script> before pasting it into the page's head or body.
5. Paste the result into the Schema Markup Validator to check the syntax.

The JSON-LD explained, with a worked example

A dental clinic in Noida has two FAQs on its implants page. Entered into the tool and wrapped in a script tag, the output is:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much does a dental implant cost in Noida?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A single implant at our clinic costs ₹28,000–₹45,000 including the crown, depending on the implant brand and whether bone grafting is needed."
      }
    },
    {
      "@type": "Question",
      "name": "Do you accept insurance or EMI?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We offer no-cost EMI for 6 months on treatments above ₹20,000. Most dental insurance covers only accident-related treatment."
      }
    }
  ]
}
</script>

• "@context": "https://schema.org" says which vocabulary the names come from.
• "@type": "FAQPage" declares that the page is a list of frequently asked questions written by the site owner (not a forum where users answer, which would be QAPage).
• mainEntity is the array of questions, in the order they appear on the page.
• Each Question has a name (the question text) and one acceptedAnswer whose text is the full answer.

The tool uses JSON.stringify, so quote marks and line breaks in your answers are escaped automatically and the JSON stays valid.

Common mistakes and how to fix them

• Pasting the raw JSON without a script tag. It then shows as text on the page and is not read as structured data. Always wrap it.
• Schema answers that differ from the page. A price updated on the page but not in the JSON-LD (₹28,000 visible, ₹25,000 in the markup) is misleading markup. Regenerate whenever you edit the visible FAQ.
• Marking up hidden or invented FAQs. Only mark up questions that a visitor can read on that page. Accordions are fine; content that exists only in the schema is not.
• Ad copy disguised as answers. "Why are we the best clinic in Noida?" is not a question people ask. Answer real queries from calls, WhatsApp chats and Search Console.
• Same FAQ block on every page. Put each question on the one page it best belongs to.
• Two FAQPage blocks. A plugin adds one automatically and you paste another. Keep a single block per page.

Practical use cases

• Clinic: treatment pages answering cost, recovery time and insurance questions patients actually ask on calls.
• Real-estate developer: project pages covering RERA number, possession date and payment plan, kept in sync with the brochure.
• B2B SaaS: pricing-page FAQs on GST invoices, annual billing and data residency in India.
• Education institute: admission FAQs on eligibility, fees and hostel, refreshed every admission cycle.

For how answer engines pick sources, read citation-worthy content for AI search, or see our AEO and GEO services.

The generator runs in your browser — the questions and answers you type are not sent to our servers.