The FAQ widget for website with search, categories, and FAQPage Schema.

On August 8, 2023, Google announced it was reducing the visibility of FAQ rich results to a narrow set of well-known authoritative government and health sources. Marketing forums lit up with declarations that FAQPage schema was dead. The truth is more nuanced and matters a lot for how you ship FAQ blocks today. FAQPage JSON-LD is still parsed by Google on every site, still feeds the AI Overview answer box, still powers 'People also ask' alignment, still surfaces in Google's experimental Search Generative Experience, and still shows up as featured snippets even when the gold accordion does not render in the regular ten-blue-links view. Sites that removed their FAQPage markup after the announcement saw measurable losses in zero-click visibility, AI citation rate, and 'People also ask' inclusion. Independent studies from Aleyda Solis, Search Engine Land, and SISTRIX all confirm the same pattern: removed schema correlates with reduced presence in answer-box surfaces, even on pages whose ranking did not change. The right move from Poper is to keep injecting valid FAQPage JSON-LD on every FAQ block you ship. The downside is zero. The upside is the long tail of question-style queries that now resolve through generative answer boxes rather than blue-link rich cards. Google's own developer documentation continues to list FAQPage as a supported structured-data type with no plans to deprecate the spec, only the gold accordion rendering. Validate every page after launch using Google Search Console, the Rich Results Test, and the new AI Overviews search-console insight panel. If your questions appear in the parsed-entities list, you have done the work correctly.

'People also ask' (PAA) blocks now appear on roughly 48% of US English desktop SERPs and 53% of US English mobile SERPs (BrightEdge 2026 study). Each PAA block expands into a featured-snippet-style answer pulled from a single source page, and clicking 'show more' reveals related questions in an effectively-infinite chain. Sites whose FAQ blocks contain the exact question phrasing that PAA surfaces win the citation slot. The optimization is mechanically straightforward: research PAA queries for your topic with tools like AlsoAsked, AnswerThePublic, or Ahrefs' Questions report; mirror the exact wording in your FAQ widget questions; write the answer in 40 to 60 words because PAA snippets truncate beyond that; lead with the direct answer in the first sentence so it survives truncation; and let Poper's FAQPage JSON-LD give Google the structured signal it needs to associate your answer with the question. Sites that do this well earn 30 to 60% of their organic clicks from PAA panels rather than from the main ten blue links, and the click-through rates from PAA tend to be higher because the visitor has already seen a good answer and clicked through wanting more. The 'People also ask' surface is also the primary feeder for Google's AI Overview answer panels and for ChatGPT's Bing-grounded search results. Question alignment is not just a Google play, it is the same alignment ChatGPT, Perplexity, and Claude use to decide which page to cite when a user asks a question in a chat thread.

The Poper FAQ widget ships three layouts, and choosing between them is almost always context-dependent. The Accordion layout keeps every answer collapsed until a visitor clicks, which saves vertical space and signals 'pick what you need'. The List layout stacks every question and answer in one open column and signals 'every answer is right here, scan freely'. The Columns layout splits the questions into a multi-column grid on desktop, which works for reference-heavy pages where a visitor wants to scan the whole set quickly. On pricing pages and product pages, where visitors are comparison-shopping and have specific friction questions, the Accordion layout wins because it lets the buyer self-select the question they care about without scrolling through irrelevant ones. The closed-by-default state also forces the visitor to make a tiny commitment, a click, which raises engagement. On legal, terms, refund, privacy, and policy pages, where reviewers expect every answer visible and visitors often print or save the page, the List layout wins because printing-to-PDF works correctly only when answers are open. On dense help-center and reference pages, the Columns layout reduces scan length by putting more questions in view at once. Poper supports all three from the same config, so you can experiment without rewriting content, and the Accordion layout adds its own controls for icon style, whether the first question opens by default, and whether multiple answers can stay open at once.

FAQ blocks are conversion levers, not just SEO assets, and treating them as one of the two means leaving the other on the table. Studies from Baymard Institute, Nielsen Norman Group, Shopify's internal merchant data, and Stripe's checkout-optimization research converge on a 15 to 35% conversion lift when an FAQ block appears below the buy button, beneath the pricing table, or alongside the demo-request form. The mechanism is straightforward: visitors with unanswered objections leave, and visitors whose objections are addressed inline complete the action. The highest-impact FAQ entries on most pages are not product-related, they are policy-related: refund window, shipping cost, cancellation terms, contract length, support response-time SLA, data-residency commitments, and the existence-and-duration of a free trial. Audit your top exit-intent popup triggers, your top pre-purchase support tickets, your top live-chat opening messages, and your sales team's most-repeated objection-handling lines, then convert the top 8 to 12 questions into FAQ entries written in the visitor's language rather than your marketing copy. Keep the set tight: 8 to 12 questions per surface scans better than 40, and a smaller set means each answer earns more attention. Iterate every quarter as your support tickets and objections shift. The FAQ block on a high-traffic page is one of the highest-ROI surfaces on your entire site for sustained CRO investment.

FAQ widgets are not a substitute for a knowledge base, a help-center search engine, a community forum, or a chat agent. They cover the predictable 80% of questions that visitors ask before converting and during the first week of using a product. The remaining 20% (specific account states, edge-case integrations, billing disputes, multi-step debugging) belong in a help center, in a status page, or in front of a human support agent. The fastest-converting FAQ blocks on the modern web are short (8 to 12 questions per surface), grouped into 2 to 4 categories at most when categories are used, written in plain language that mirrors the visitor's actual phrasing rather than your internal terminology, and linked out to deeper documentation for any long-tail questions that one in twenty visitors might want. Do not try to put 100 questions in your FAQ widget. The page becomes harder to scan, the FAQPage schema signal dilutes across so many entries that no single one earns featured-snippet treatment, and the visitor stops trusting that there is a curated answer for their specific problem. The right pattern is to pick the 8 to 12 highest-impact questions for the page you are working on, ship them with FAQPage schema and stable anchor links, link the long tail to a help center or knowledge base, and treat the FAQ widget as a conversion-rate optimization tool rather than a knowledge dump. That is the configuration that ranks in 2026, captures 'People also ask' real estate, gets cited by AI Overview, and lifts conversion on the pages that drive your revenue.