FAQPage · JSON-LD

FAQ Schema Generator

FAQPage schema marks up a list of questions and their answers so machines can read them as structured question-answer pairs rather than as ordinary paragraphs. Generate valid JSON-LD below, then read the part most generators leave out: what this markup actually earns you in 2026.

Open the schema generator

No rich result in 2026

FAQ rich results no longer exist. Google restricted them to authoritative government and health sites in August 2023, then retired the feature entirely on 7 May 2026. The FAQ report is being removed from Search Console during 2026. Any tool still promising you expandable FAQ dropdowns in search results is out of date.

Why it is still worth adding

The markup is still worth adding, just not for the reason it was originally sold. FAQPage gives AI answer engines a clean, unambiguous mapping of question to answer, which is exactly the shape a model needs when deciding what to quote. Rankealo tracks brand citations across ChatGPT, Perplexity, Gemini, and Claude, and structured question-answer content is consistently among the easiest content for those systems to lift. Treat FAQ schema as machine-readability for AI answers, not as a search-appearance trick.

A valid FAQPage example

Drop this in a <script type="application/ld+json"> tag in the page head or body, with your own values.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does SEO take to show results?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most sites see measurable movement in three to six months, though competitive terms take longer. New domains take longest because they have no authority to build on."
      }
    },
    {
      "@type": "Question",
      "name": "Do I need to publish weekly to rank?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Publishing cadence matters far less than whether each page answers a real query better than the pages already ranking for it."
      }
    }
  ]
}

Required and recommended properties

Property	Required	Notes
`mainEntity`	Required	An array of Question items. A single question is valid but unusual.
`Question.name`	Required	The question text, exactly as it appears on the page.
`Question.acceptedAnswer`	Required	One Answer object per question.
`Answer.text`	Required	The answer text. Basic HTML is allowed; it must match the visible answer.
`@id / url`	Optional	Useful when several FAQ blocks live on one page or you anchor-link individual questions.

Common FAQ schema mistakes

Marking up questions that are not visible on the page

Every question and answer in the markup must be present and visible to a user reading the page. Hidden or markup-only FAQs violate Google's structured data guidelines and have always been the fastest route to a manual action.

Bolting a generic FAQ block onto every page

This is the practice that got the feature killed. Padding pages with the same three questions to grab search real estate no longer earns anything and makes the page worse for the humans reading it.

Answer text that drifts from the visible copy

When the visible FAQ is edited but the JSON-LD is not, the two fall out of sync. Generate the schema from the same source as the rendered FAQ so they cannot diverge.

Generating it is the easy half

The harder part is keeping markup correct across a site as pages change. Rankealo's SEO agent audits structured data across your pages and ships the JSON-LD fixes as pull requests you review and merge, rather than handing you a list of errors to implement yourself.

See how the SEO agent ships fixes

FAQ schema questions

Does FAQ schema still work in 2026?

It still validates and machines still read it, but it no longer produces a rich result in Google Search. Google restricted FAQ rich results to authoritative government and health sites in August 2023 and retired the feature for everyone on 7 May 2026. The markup remains useful for AI answer engines and general machine readability, which is now the honest reason to add it.

Should I remove FAQPage markup from my site?

No. There is no penalty for keeping valid FAQPage markup, and it still helps machines parse your question-answer content, including the AI systems that increasingly sit between your page and the reader. What you should remove is any FAQ block you added purely to win a rich result, because those tend to be generic filler that makes the page worse.

What is the difference between FAQPage and QAPage?

FAQPage is for questions authored and answered by the site itself, which covers almost every marketing and documentation use. QAPage is for user-generated pages where a community submits an answer that others vote on, like a forum thread. Using QAPage for your own marketing FAQ is incorrect.

Other schema types

LocalBusiness

LocalBusiness schema generator and reference.

Product

Product schema generator and reference.

Service

Service schema generator and reference.

Review

Review schema generator and reference.

Or go back to the schema markup generator to build markup interactively.