Schema FAQ para resultados ricos do Google (guia de 2026)

FAQ schema tells search engines which questions and answers appear on a page, but since 2023 Google shows FAQ rich results for very few sites.

Google's FAQ rich results used to add expandable questions under a search listing, which made it take up far more space. In August 2023 Google limited them to a small group of sites, and many tutorials still haven't caught up. This guide explains what FAQ schema markup does in 2026, who can still get FAQ rich results, what the alternatives really are, and gives you a FAQ JSON-LD example you can validate yourself.

What is FAQ schema?

FAQ schema is structured data, written with the Schema.org FAQPage type, that tells search engines "this page contains a list of questions with one answer each, written by the site". Each question is a Question item and each answer an acceptedAnswer. When Google decided to show it, the questions appeared as dropdowns directly under your listing.

What Google changed in August 2023

In August 2023 Google announced two changes at once:

• FAQ rich results are now shown only for well-known, authoritative government and health websites. For every other site, FAQ dropdowns no longer appear in Google Search.
• HowTo rich results were deprecated entirely, first on mobile and then on desktop, so HowTo markup no longer produces a rich result for anyone.

This means there is no "workaround" that brings FAQ dropdowns back for a typical business or blog. Nesting questions inside HowTo markup doesn't help, because HowTo rich results are gone too. And Product markup doesn't have a question feature that Google shows in search.

Is FAQ schema still worth adding?

It depends on what you expect from it. If you searched for Google rich results FAQ eligibility, the short answer is that most sites no longer qualify.

• If you're a government or health site recognised as authoritative, FAQ rich results may still show for you, and FAQ schema is worth adding to pages with genuine FAQs.
• For everyone else, FAQ schema markup won't produce dropdowns in Google. It's still valid Schema.org, it costs little to add, and other search engines or tools may read it, but none of them publish a promise to use it. Don't add it expecting extra space or more clicks from Google.
• The visible FAQ content is what matters. A clear question-and-answer section on the page can still help readers and give Google straightforward text to understand. Google hasn't said that FAQ markup feeds its "People also ask" boxes, so write the answers for people first.

What about rich results in general?

Rich results for other types are very much alive. Google's own introduction to structured data cites case studies such as Rotten Tomatoes measuring a 25% higher click-through rate on pages with structured data, and Nestlé measuring an 82% higher click-through rate on pages that appear as rich results. Those are general rich-result figures from specific companies, not FAQ-specific ones, and your results may differ. Product, Article, Review snippet, Breadcrumb, Event and LocalBusiness markup all still have Google features where they apply.

When QAPage is the right type instead

QAPage is a different type for a different kind of page: one question, with answers submitted by users, like a forum thread or a community support question. Google still supports Q&A rich results for these pages. Google's guidelines are explicit that QAPage is not for FAQ pages written by the site owner, so switching your company FAQ to QAPage would be the wrong markup, not a loophole. Use QAPage only if your page really is one user question with user answers.

A FAQ JSON-LD example you can copy

Here is a minimal, valid FAQPage block. Paste it into the page's <head> or body, and make sure the same questions and answers are visible on the page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you ship internationally?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We ship to most countries. Delivery usually takes 5 to 10 business days."
      }
    },
    {
      "@type": "Question",
      "name": "Can I return an item?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "You can return unused items within 30 days for a full refund."
      }
    }
  ]
}
</script>

The rules that matter, from Google's FAQ structured data guidelines:

• The content must be visible. Every question and answer in the markup must appear on the page for visitors to read.
• One answer per question, written by you. If users can submit answers, it's a QAPage, not a FAQPage.
• No advertising. FAQ markup isn't meant for promotional copy.
• Repeated questions. If the same question appears on several pages of your site, mark it up on one page only.

How to add FAQ schema to your site

1. Write the FAQ section on the page first. Use real questions your customers ask, in plain language, with direct answers.
2. Generate the JSON-LD. Use a FAQ schema generator such as FeedPulse's schema markup generator: pick FAQPage, type your questions and answers, and copy the output. It builds the markup from what you type but doesn't validate it for you.
3. Paste it into the page. In WordPress, use your SEO plugin's custom schema field or a header-code plugin; in Shopify, add it to the relevant theme template; in Webflow, use a custom code embed.
4. Test it. Run the live URL through Google's Rich Results Test and through validator.schema.org. Fix any errors. Note that for most sites the Rich Results Test will now say the page isn't eligible for FAQ rich results, even when the markup itself is correct. That's the 2023 policy, not a bug in your code.
5. Ask Google to recrawl. In Search Console, use URL Inspection and "Request indexing" so Google picks up the change sooner.

Common FAQ schema mistakes

Marking up content nobody can see

Hidden FAQs, or answers that only exist in the markup, go against Google's structured data guidelines. At best Google ignores them; at worst they can lead to a manual action for spammy structured data.

Answers that don't answer

"Great question! Contact us to find out" isn't an answer. Each acceptedAnswer should resolve the question in a sentence or two, with the detail on the page if needed.

Expecting markup to fix rankings

Structured data isn't a ranking factor on its own. It helps Google understand and present a page, but it won't move a page from page three to page one.

Choosing the wrong type to chase a feature

Using QAPage for a company FAQ, or HowTo for anything at all in 2026, won't bring back rich results. Pick the type that honestly describes the page.

Using the FeedPulse schema markup generator

The FeedPulse schema markup generator is free, needs no signup and covers four types: Article, Product, FAQPage and LocalBusiness. You fill in a form, the JSON-LD updates as you type, and one button copies the snippet and opens Google's Rich Results Test for your URL. It doesn't cover HowTo, QAPage, Event or Recipe; for those, write the markup from Google's documentation or use a generator that supports them.

Wrapping up

FAQ schema still exists, but Google's FAQ rich results are now reserved for well-known government and health sites, and HowTo rich results are gone. For most sites, the honest approach is simple: write a genuinely useful FAQ section, add FAQPage markup if you like because it's cheap and accurate, and put your structured data effort into the types Google still shows, such as Product, Article and Breadcrumb.