FAQ structured data

Will FAQ structured data get my FAQ shown in Google Search right away?

No. The expandable FAQ display in Google Search (FAQ rich results) is no longer shown. In August 2023, Google limited it to well-known, authoritative government and health websites, and from May 7, 2026 (2026-05-07) it stopped showing FAQ rich results altogether.

In June 2026, Google Search Central also took down its documentation for FAQ rich results. So the old advice that “adding FAQ structured data makes your search result bigger” no longer holds.

That doesn't make FAQPage markup useless. FAQPage is part of schema.org's shared vocabulary, so other search services and AI tools can use it to tell questions from answers, and above all, a page organized into questions and answers helps your customers.

When and how did Google's FAQ rich results change?

Google scaled back FAQ display in two steps, saying it wanted cleaner, more consistent search results. Around the same time, it also removed several other rich results, such as course info and special announcements.

These changes are about Google Search results. How Naver or AI answer services use FAQ markup varies by service, and most of them don't publish the details.

Some providers, unaware of this news, still promise to “expand your search results with FAQ structured data.” Know that as of 2026, you can't expect that effect in Google Search.

How do I create FAQ structured data?

The FAQPage format pairs each question (Question) with one accepted answer (acceptedAnswer). One page can hold several questions, and like other structured data, it's added as JSON-LD.

Once you have more than ten questions, group them by topic, such as booking, pricing and visiting info. Customers find their question faster, and machines can more easily tell which topic each question belongs to.

1. 01Write down the questions you get by phone and message for about 2 weeks, then pick the ones that come up most.
2. 02Write questions the way customers say them. “Can I park there?” beats “Parking availability.”
3. 03Open each answer with a direct “Yes,” “No” or a number, then add one or two sentences on any conditions.
4. 04Post the questions and answers on your website's FAQ page first.
5. 05Add the same questions and answers to the page code in FAQPage format.
6. 06Check for format errors with the schema.org validator (validator.schema.org).
7. 07When prices, hours or policies change, update the page and the structured data together on the same day.

What questions make a good FAQ?

The best ones are the questions customers hesitate over right before booking or visiting: price, hours, location, what to bring, cancellation policy. They have clear answers, and once customers hear the answer, they can move straight to the next step.

On the other hand, avoid promotional questions customers never actually ask, like “What makes our business special?” Questions whose answer ends with “please contact us” don't help customers or AI either.

A good answer is short but includes the conditions. For “Can I park there?”, answer what customers will wonder next in one go: “Yes, our private lot behind the building fits 4 cars. Spots fill up fast at weekend lunchtime.” That cuts down on phone inquiries.

• Cafes and restaurants: “Do you have high chairs?”, “What's the minimum group size for a group booking?”
• Hair salons: “Can I come in just for a consultation?”, “How long does the treatment take?”
• Craft workshops and classes: “It's my first time. Can I come on my own?”, “When do I get my finished piece?”
• Academies: “If I join partway through, can I keep up?”, “How do make-up classes work?”

What are the most common FAQ structured data mistakes?

The most common mistake is creating an FAQ expecting “a big spot on Google,” then abandoning it when that doesn't happen. The point of an FAQ is to answer customers' questions accurately, not to decorate search results, so outdated answers actually hurt you.

Ask your agency: “Are the FAQ page and the structured data generated from the same data?” If editing one question in the admin panel updates both places, there's less to keep track of.

If an FAQ answer links to another page, check that the link actually opens. If your booking page address changes but the link in the FAQ answer still points to the old one, customers get lost halfway.

• Copying the same FAQ onto every page
• Answers that just repeat ad copy without answering the question
• Using FAQPage on a Q&A board where customers each post their own answers: for question pages answered by multiple people, QAPage is the right type
• Closing days or prices changed, but the FAQ answers still show the old information

Does FAQ structured data help with AI answers?

It can, but there's no guarantee. Google has said there's no special structured data you need to add to appear in AI Overviews or AI Mode, and other AI services haven't disclosed in detail how they use FAQ markup.

What's certain is that short, clear questions and answers written on the page are easy for both people and machines to read. So think of FAQ structured data as “a nice-to-have supporting label” and the questions and answers on the page as “the must-have main content.”

Also keep in mind that AI answers may repeat your answers word for word. So instead of vague phrases like “it depends,” write verified numbers and conditions in your answers; that's safer for customers, too.