The AI prompts that win featured snippets and People Also Ask boxes tell the model to answer each FAQ question in one self-contained paragraph of roughly 40-60 words, leading with the direct answer before any elaboration. That structural rule matters more than ever now that Google has fully deprecated FAQ rich results: as of May 7, 2026, the expandable FAQ dropdown no longer appears in Search for any site, including the government and health sites that had kept the privilege since 2023. Featured snippets and People Also Ask boxes, however, are a separate and very much active feature that rewards exactly this kind of tightly structured answer, no schema markup required.
Why FAQPage Schema No Longer Guarantees a Rich Result
For years, marking up an FAQ section with FAQPage structured data was the easiest way to get an expandable accordion under your listing in Google Search. Google walked that back in two stages. First, in August 2023, it restricted the FAQ rich result to “well-known, authoritative government and health websites,” cutting every other publisher out overnight. Then, according to Search Engine Journal’s coverage of Google’s own documentation update, Google finished the job in 2026: FAQ rich results stopped appearing in Search entirely on May 7, 2026, with the FAQ search-appearance filter, the rich result report, and Rich Results Test support for the feature scheduled for removal by June 2026, and Search Console API support ending in August 2026.
You can still add FAQPage schema to a page without being penalized, but Google’s own guidance now confirms the payoff is gone: it will not produce a visible dropdown for anyone. That changes what “optimizing an FAQ section” should mean going forward. Instead of writing for a schema validator, you’re writing for two things that never depended on markup in the first place: the featured snippet and the People Also Ask box, both of which Google’s Search Central documentation describes as generated automatically by ranking systems that evaluate a page’s visible text, not its structured data.
What Actually Makes an FAQ Answer “Snippet-Friendly”?
Google’s featured snippet documentation is explicit that there is no markup, meta tag, or submission process that forces a passage into a snippet — its systems decide algorithmically whether a piece of text answers the query well enough to lead with. In practice, three traits show up again and again in the answers that do get pulled into snippets and PAA boxes:
- Self-contained: the answer makes sense with zero surrounding context — no “as mentioned above,” no pronouns referring back to an earlier paragraph.
- Direct-answer-first: the first sentence answers the question outright; supporting detail, caveats, and examples come after, not before.
- Right-sized: paragraph snippets tend to run about 40-60 words (two to three tight sentences); list snippets work best as four to eight short steps or items.
The question itself matters just as much — phrase it the way people actually type it into Google, since that phrasing is usually what shows up verbatim in a People Also Ask box, not how a copywriter would title a section for readability.
AI Prompts for Drafting Snippet-Ready Answers
The gap between a prompt that produces snippet-worthy copy and one that produces marketing fluff almost always comes down to whether you specify structure, length, and self-containment up front. Compare these two prompts for the same question.
Weak prompt: “Write an FAQ answer for ‘How much does email marketing cost?'”
Left this open-ended, most models produce a throat-clearing intro sentence and bury the actual price range in sentence three — exactly the shape that doesn’t get lifted into a snippet.
Strong prompt: “Answer the question ‘How much does email marketing cost?’ in one self-contained paragraph of 40-55 words. Start the first sentence with the direct answer (a price range), then add one sentence of context about what affects the price. Do not reference ‘this article’ or use filler transitions like ‘in general’ or ‘it depends.’ Write at an 8th-grade reading level.”
For process questions (“How do I set up X”), ask for a numbered list instead of a paragraph, since list-format answers are what Google typically surfaces for step-by-step queries:
Strong prompt: “Answer ‘How do I set up email authentication for cold outreach?’ as a numbered list of 5-6 steps, each step a single short sentence starting with an action verb. No intro sentence before the list — the list itself is the answer.”
AI Prompts for Turning “People Also Ask” Questions Into FAQ Content
Since PAA boxes are one of the clearest public signals of which exact phrasing Google already rewards for a topic, the fastest way to build a real FAQ section is to start from actual PAA questions for your target keyword (pulled straight from the search results page, or from a rank-tracking tool) and feed them to an AI model as raw material, not as a brainstorming prompt.
Prompt: “Here are 8 real ‘People Also Ask’ questions for the keyword [keyword]: [paste questions]. For each one, write a self-contained answer of 40-60 words that leads with the direct answer in the first sentence. Keep the original question wording exactly as I gave it — don’t rephrase the questions to sound more natural. Flag any question that genuinely can’t be answered honestly in under 60 words, instead of forcing a shallow answer just to hit the word count.”
That last instruction matters. Some PAA questions need a longer, more nuanced answer, and padding a fake 50-word answer just to chase a snippet produces weak content. It’s fine for one FAQ item to run three paragraphs when the topic actually requires it — you may not win the snippet on that particular question, and that’s an acceptable trade-off against publishing something misleadingly short.
How to Format the FAQ Section Now That Schema Doesn’t Display It
With the accordion rich result gone, there’s no SEO upside to hiding FAQ answers behind a JavaScript-only toggle that reveals text only on click — if anything, that risks making the full answer harder for Google’s ranking systems to read as visible page text. Use a real H3 heading for each question, phrased to match how people actually search, followed by a plain paragraph answer directly underneath it. A CSS-only accordion can still handle the visual collapsing for users who want it. When prompting an AI assistant to draft the section, ask it to output each item as a heading-plus-paragraph pair rather than as JSON-LD, and treat FAQPage schema (if you keep adding it) as an optional, invisible extra rather than the only place the answer text lives.
Frequently Asked Questions
Is FAQPage schema still worth adding in 2026?
Adding FAQPage schema in 2026 no longer produces a visible rich result for any site, since Google fully deprecated the feature on May 7, 2026. It won’t hurt your page to keep the markup for internal tooling or other platforms that still parse it, but it should no longer be treated as an SEO tactic on its own — put the effort into the visible answer text instead, since that’s what featured snippets and People Also Ask boxes actually pull from.
How long should a featured-snippet-friendly answer be?
Most paragraph-style featured snippets run around 40-60 words, or two to three short sentences, with the direct answer stated in the first sentence. List-style snippets tend to work best with four to eight short items. Google publishes no official minimum or maximum length, so treat these as practical targets to test against rather than hard rules — a genuinely useful longer answer can still rank well even if it never gets lifted into a snippet.
Do People Also Ask boxes still exist if FAQ rich results are gone?
Yes. People Also Ask and featured snippets are a completely separate system from FAQPage rich results, and neither one has ever required structured data to appear. They’re generated algorithmically from the plain text of any indexed page that answers the question well, which is why the deprecation of FAQ schema doesn’t reduce the value of writing clear, self-contained FAQ answers — it just means the accordion dropdown under your search listing is no longer the reward for doing it.
For the primary sources behind this guide, see Google’s own featured snippets documentation and Search Engine Journal’s report on the 2026 FAQ rich results deprecation. If you’re building a broader content plan around question-based queries, pair this with How to Write AI Prompts for SEO Content Briefs and Outlines and How to Optimize Content for AI Overviews and ChatGPT Search (GEO Prompts) so the rest of the page is structured for both traditional snippets and AI-generated answers.
Featured photo by Shixart1985, licensed under CC BY 2.0, via Wikimedia Commons.
