S SCHEMA.BIZ

Last updated:

FAQ Schema Generator

This FAQ schema generator turns the questions and answers on your page into FAQPage JSON-LD as you type. Add one entry per question, paste each answer as the page words it, then copy the script tag. Google no longer shows FAQ rich results, so read what the markup still does before you add it.

Reference: FAQ schema

FAQ Page: Use when your page has a list of questions and answers. Google no longer shows FAQ rich results, so this describes the page's structure for other tools; it doesn't change your Google result.

Basic Info
Questions

What Google shows for FAQ markup

  • FAQ: retired: Google stopped showing it on May 7, 2026.

Google stopped showing FAQ rich results on May 7, 2026 and has since taken down the feature's documentation, so FAQPage markup no longer puts expandable answers under your listing. However clean the code is, it earns no search feature today. What Google said when it first cut FAQ results back still applies: markup it doesn't use causes no trouble in Search, and there's no need to strip it from pages that already carry it.

So there are two honest reasons to generate it. Software other than Google that reads schema.org can use it to tell which text answers which question, without guessing from your headings. And writing it is a check on the page: a question with no clear, complete answer on the page isn't ready to be marked up. Google's AI features guide states that no special schema.org markup is needed for them, so don't add FAQPage hoping to appear there.

How to fill in each field

Page title and URL

Both are optional. The page title becomes the FAQPage's name, so use the heading the page itself shows, such as Shipping and returns, not a string of keywords. The URL should be the page's canonical address in full, starting with https://, the same one its canonical tag gives. Leave both empty and the generator writes only the questions, which is still valid.

Questions

Add an entry for each question on the page, in the order a reader meets them, with the add button under the list; Remove takes one out. Type the question exactly as it's printed, question mark included. An entry missing its question or its answer is left out of the code, so a half-filled entry won't break the output, but it won't show up either. Google's general guidelines ask you to mark up only what readers can see, so don't add questions that exist only in the code.

Answers

Paste the full answer, not a summary: the markup should say what the page says. The answer field accepts HTML, so a link, a list or bold text can stay, written as <a href="https://example.com/returns/"> or <ul>. The generator puts it in acceptedAnswer.text and escapes the quotes for JSON. Use absolute links rather than /returns/, because whatever reads the answer may read it away from your page.

The form marks 1 field as required and 0 as recommended:

  • Questions & Answers (required): Add your frequently asked questions. Each needs a question and an answer.

Example: A shop's shipping and returns FAQ

Four questions from a help page, with the page title and URL filled in and one answer that keeps its link as HTML.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "name": "Shipping and returns",
  "url": "https://shop.example.com/help/shipping-returns/",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much does delivery cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Delivery is free on orders over $60. Below that, standard delivery costs $5.95 anywhere in the US."
      }
    },
    {
      "@type": "Question",
      "name": "When will my order arrive?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Orders placed by 1 p.m. Eastern ship the same weekday and arrive in 2 to 4 business days."
      }
    },
    {
      "@type": "Question",
      "name": "How do I send something back?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Start a return from <a href=\"https://shop.example.com/account/returns/\">your returns page</a> within 45 days, print the label and drop the parcel at any post office."
      }
    },
    {
      "@type": "Question",
      "name": "How long do refunds take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We refund the original payment method within 3 business days of the parcel reaching our warehouse."
      }
    }
  ]
}

5 common mistakes

  1. Expecting a rich result. Google stopped showing FAQ rich results on May 7, 2026. The markup won't add answers under your listing, however well it validates.
  2. Questions that aren't on the page. Every question in the code should be one a reader can see on the page, in the same words. Extra questions written only into the markup misdescribe the page.
  3. The same FAQ block on every page. An FAQPage describes the page it's on. Pasting a site-wide set of questions into a shared template marks up text most of those pages don't show.
  4. Answers cut short. A one-line answer in the code under three paragraphs on the page isn't a true picture of it. Copy the answer in full, HTML included.
  5. FAQPage for a community thread. A page where visitors ask a question and others answer it is a Q&A page, which schema.org describes with QAPage. This form doesn't write that type.

How to test your FAQ markup

The panel beside the code checks it as you type and, for this type, notes that Google has retired the FAQ result while the markup stays valid schema.org. For a fuller report, paste the code into the Schema Validator, which checks each Question and its Answer against schema.org. If the same page carries other markup, such as a breadcrumb or an organization, test the live page in Google's Rich Results Test for those; it won't show an FAQ result.

Frequently Asked Questions

Is FAQ schema still worth adding?

Not for how your result looks in Google: FAQ rich results ended on May 7, 2026. It's worth adding if you want the page's questions and answers described in a standard form for other software that reads schema.org, or if your site already writes it on every help page. If the rich result was the only reason, you can skip it.

Should I remove the FAQPage markup I already have?

You don't have to. When Google cut FAQ results back in 2023, it said there was no need to remove the markup and that structured data it doesn't use causes no problems in Search. Do fix or remove it if the answers in the code no longer match the page.

Will I lose my questions if I close the tab?

No. The Generator saves the form in your browser as you type, so it's there when you come back to this page on the same device. To move it to another device or send it to someone, use Share: the link carries the form after the #, a part of the address browsers don't send to the server.

Other schema generators