FAQ Schema: What Changed, When It Still Helps, and How to Add It

For a few years, FAQ schema was the easiest visual win in SEO. Add some questions and answers to a page, mark them up, and your search result could expand into a tall block of dropdowns that pushed competitors down. Plenty of sites abused it, marking up sales pitches as "FAQs" on every page. In August 2023, Google limited FAQ rich results to a small set of well-known, authoritative government and health websites. For most businesses, those expanding dropdowns are gone.

So is FAQ schema dead? Not quite. It just stopped being a shortcut.

What FAQPage schema is

FAQPage is a Schema.org type that marks up a list of questions with one accepted answer each. It's meant for pages where the site itself provides the questions and answers, like a support FAQ or a section at the end of a service page.

It's different from QAPage, which is for pages where users submit answers, like a forum thread or community Q&A.

What it still does after 2023

• Helps machines parse the content. Structured Q&A pairs are easy for search engines and other systems to understand.
• Supports eligibility on sites that qualify. If you're a government or recognised health authority, the rich result may still show.
• Does no harm when used correctly. Google said sites don't need to remove the markup; unused structured data simply doesn't produce a rich result.

What it no longer does for most sites is change how your result looks. If someone sells you FAQ schema as a way to "take over the SERP", that pitch is outdated.

The FAQ section matters more than the markup

A well-written FAQ section on a page is still useful:

• It answers the follow-up questions that block a purchase or a booking.
• Clear question headings can be picked up for featured snippets and People Also Ask, which come from page content, not schema.
• It catches long-tail searches the main copy doesn't cover.

A Jaipur wedding photographer's package page might answer: Do you travel to Udaipur and Jodhpur? How many edited photos are included? When do we get the album? Is a pre-wedding shoot included? Each of those is a real search and a real objection.

Writing good FAQs

• Use real questions. Pull them from customer calls, WhatsApp chats, reviews and People Also Ask. Not "Why are we the best?"
• Answer directly. First sentence answers; the rest adds detail. Two to four sentences is usually enough.
• Don't repeat the page. If the answer is already in the body, the FAQ is padding.
• Keep it page-specific. The same generic FAQ block on 200 pages adds nothing and creates duplicate content across your site.

Adding FAQPage markup in JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you deliver eggless cakes outside Jaipur city?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We deliver within Jaipur city limits, including Vaishali Nagar, Malviya Nagar and Jagatpura. For Ajmer Road and areas beyond, call us to check availability."
      }
    },
    {
      "@type": "Question",
      "name": "How early should I place an order?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard cakes need four hours' notice. Photo cakes and tiered cakes need at least one day."
      }
    }
  ]
}
</script>

On WordPress, Yoast and Rank Math both include FAQ blocks that output this markup automatically. Many Shopify themes and apps do the same.

Rules Google applies

• The questions and answers must be visible on the page. Hidden-only markup breaks the guidelines.
• Each question should have a single answer written by the site.
• Don't use FAQ markup for advertising content.
• If the same question appears on many pages, mark it up only once on the site.
• Answers can include some HTML like links and lists, but keep them simple.

After adding markup, test with Google's Rich Results Test or the Schema.org validator. Search Console may still report FAQ markup under enhancements even if no rich result appears.

Should you add FAQ schema now?

My view: add it when you already have a genuine FAQ section and your CMS outputs the markup for free. Don't hire someone to retrofit it across hundreds of pages expecting a traffic change. The effort is better spent on the content of the answers and on the types that still earn visible results, covered in the schema markup guide.

Remove FAQ markup if:

• It's on pages where the FAQs are hidden or not shown at all.
• It marks up promotional statements rather than real questions.
• Two plugins are outputting duplicate FAQPage blocks.

Where FAQs fit on a page

Usually near the end of service, product and guide pages, after the main content. On support sites, a dedicated FAQ page organised by topic works well, with each answer linking to a detailed help article where one exists. The FAQ sections on this blog follow the same idea: short answers that add something the body didn't say.

If you're auditing several pages, combine this with the on-page SEO checklist. Your next step: open your top service page, look at the last ten customer questions you received, and turn the three most common into FAQ entries.