--- title: "FAQ Schema for AI Search: A Practical 2026 Playbook" description: "FAQ schema still matters in 2026 — not for Google Rich Results, but for ChatGPT, Claude, Perplexity, and AI Overviews. Real JSON-LD code, validation, and deployment." lang: en json-ld: | [ { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://alicelabs.ai/#organization", "name": "Alice Labs", "alternateName": [ "Alice Labs AB", "AliceLabs" ], "legalName": "Alice Labs AB", "identifier": "559443-5470", "foundingLocation": { "@type": "Place", "name": "Stockholm, Sweden" }, "url": "https://alicelabs.ai", "logo": { "@type": "ImageObject", "@id": "https://alicelabs.ai/#logo", "url": "https://alicelabs.ai/images/alice-logo.png", "contentUrl": "https://alicelabs.ai/images/alice-logo.png", "width": 2000, "height": 2027, "caption": "Alice Labs" }, "image": { "@id": "https://alicelabs.ai/#logo" }, "description": "Alice Labs är en svensk AI-byrå som hjälper företag implementera AI - från strategi till skalning.", "slogan": "From AI strategy to measurable results.", "foundingDate": "2023", "email": "hej@alicelabs.ai", "telephone": "+46734157476", "address": { "@type": "PostalAddress", "streetAddress": "Hammarbybacken 27", "addressLocality": "Stockholm", "postalCode": "120 30", "addressCountry": "SE" }, "contactPoint": [ { "@type": "ContactPoint", "contactType": "customer service", "email": "hej@alicelabs.ai", "telephone": "+46734157476", "areaServed": [ "SE", "EU" ], "availableLanguage": [ "Swedish", "English" ] } ], "areaServed": [ { "@type": "Country", "name": "Sweden" }, { "@type": "Place", "name": "Europe" } ], "knowsAbout": [ "AI strategy", "AI implementation", "AI agents", "AI automation", "Generative AI", "AI governance", "AI training", "Machine learning", "Large language models", "RAG", "AI consulting", "Digital transformation", "AI search optimization", "LLMO", "AI for enterprise" ], "founder": [ { "@id": "https://alicelabs.ai/#linus" }, { "@id": "https://alicelabs.ai/#eric" } ], "sameAs": [ "https://www.linkedin.com/company/alicelabsai", "https://www.trustpilot.com/review/alicelabs.ai", "https://www.wikidata.org/wiki/Q140369570" ] }, { "@type": "Person", "@id": "https://alicelabs.ai/#linus", "name": "Linus Ingemarsson", "givenName": "Linus", "familyName": "Ingemarsson", "jobTitle": "Co-Founder", "description": "Co-founder of Alice Labs. Architects AI agent systems and automation in production for clients across financial services, media, and the public sector.", "url": "https://alicelabs.ai/en/linus-ingemarsson", "sameAs": [ "https://www.linkedin.com/in/linus-ingemarsson/", "https://www.wikidata.org/wiki/Q140369914" ], "knowsAbout": [ "AI agents", "agent orchestration", "AI implementation", "LangGraph", "RAG systems", "AI strategy", "enterprise AI", "AI search optimization", "LLMO", "Nordic AI ecosystem" ], "worksFor": { "@id": "https://alicelabs.ai/#organization" } }, { "@type": "Person", "@id": "https://alicelabs.ai/#eric", "name": "Eric Lundberg", "givenName": "Eric", "familyName": "Lundberg", "jobTitle": "Co-Founder", "description": "Co-founder of Alice Labs. Designs AI automation systems and agent workflows that remove repetitive work and make day-to-day operations more reliable.", "url": "https://alicelabs.ai/en/eric-lundberg", "sameAs": [ "https://www.linkedin.com/in/eric-lundberg-3530451bb/", "https://www.wikidata.org/wiki/Q140369978" ], "knowsAbout": [ "AI automation", "agent workflows", "AI integrations", "process automation", "knowledge systems", "AI engineering", "enterprise AI", "Nordic AI ecosystem" ], "worksFor": { "@id": "https://alicelabs.ai/#organization" } }, { "@type": "Person", "@id": "https://alicelabs.ai/#alice", "name": "Alice Holmgren", "givenName": "Alice", "familyName": "Holmgren", "jobTitle": "CEO", "description": "CEO of Alice Labs. Leads strategy and growth across the Nordic AI consulting market.", "url": "https://alicelabs.ai/en/alice-holmgren", "knowsAbout": [ "AI strategy", "AI consulting leadership", "business development", "Nordic AI ecosystem", "enterprise AI adoption", "AI program management" ], "worksFor": { "@id": "https://alicelabs.ai/#organization" } }, { "@type": [ "LocalBusiness", "ProfessionalService" ], "@id": "https://alicelabs.ai/#localbusiness", "name": "Alice Labs", "description": "AI-konsult i Stockholm. Vi hjälper företag implementera AI - från strategi till skalning. Boka möte för en kostnadsfri AI-genomgång.", "url": "https://alicelabs.ai", "logo": { "@id": "https://alicelabs.ai/#logo" }, "image": { "@id": "https://alicelabs.ai/#logo" }, "telephone": "+46734157476", "email": "hej@alicelabs.ai", "priceRange": "$$$", "currenciesAccepted": "SEK, EUR, USD", "paymentAccepted": "Invoice", "address": { "@type": "PostalAddress", "streetAddress": "Hammarbybacken 27", "addressLocality": "Stockholm", "postalCode": "120 30", "addressRegion": "Stockholms län", "addressCountry": "SE" }, "geo": { "@type": "GeoCoordinates", "latitude": 59.3018, "longitude": 18.1003 }, "areaServed": [ { "@type": "City", "name": "Stockholm" }, { "@type": "City", "name": "Göteborg" }, { "@type": "City", "name": "Malmö" }, { "@type": "City", "name": "Uppsala" }, { "@type": "Country", "name": "Sweden" } ], "openingHoursSpecification": [ { "@type": "OpeningHoursSpecification", "dayOfWeek": [ "Monday", "Tuesday", "Wednesday", "Thursday", "Friday" ], "opens": "08:00", "closes": "18:00" } ], "hasOfferCatalog": { "@type": "OfferCatalog", "name": "AI-tjänster", "itemListElement": [ { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "AI-konsult" } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "AI-strategi" } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "AI-implementation" } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "AI-utbildning" } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "AI-agenter" } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "AI-automation" } } ] }, "knowsAbout": [ "AI-konsult", "AI-strategi", "AI-implementation", "AI-utbildning", "AI-agenter", "AI-automation", "Generative AI", "Machine learning", "RAG", "Large language models", "AI governance" ], "parentOrganization": { "@id": "https://alicelabs.ai/#organization" }, "sameAs": [ "https://www.linkedin.com/company/alicelabsai" ] }, { "@type": "WebSite", "@id": "https://alicelabs.ai/#website", "url": "https://alicelabs.ai", "name": "Alice Labs", "alternateName": [ "Alice Labs AB" ], "description": "AI consulting, implementation and training for businesses.", "publisher": { "@id": "https://alicelabs.ai/#organization" }, "inLanguage": [ "sv-SE", "en-US" ], "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://alicelabs.ai/?q={search_term_string}" }, "query-input": "required name=search_term_string" } } ] }, { "@context": "https://schema.org", "@graph": [ { "@type": "HowTo", "@id": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#article", "headline": "FAQ Schema for AI Search: The 2026 Playbook for LLM Citations", "description": "FAQ schema still matters in 2026 — not for Google Rich Results, but for ChatGPT, Claude, Perplexity, and AI Overviews. Real JSON-LD code, validation, and deployment.", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search", "datePublished": "2026-05-06", "dateModified": "2026-05-13", "expires": "2026-08-11", "author": { "@id": "https://alicelabs.ai/#linus" }, "reviewedBy": { "@id": "https://alicelabs.ai/#eric" }, "dateReviewed": "2026-05-13", "publisher": { "@type": "Organization", "name": "Alice Labs", "url": "https://alicelabs.ai", "logo": { "@type": "ImageObject", "url": "https://alicelabs.ai/images/alice-logo.png" } }, "image": { "@type": "ImageObject", "@id": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#hero-image", "url": "https://alicelabs.ai/images/og/og-home.jpg", "contentUrl": "https://alicelabs.ai/images/og/og-home.jpg", "width": 1600, "height": 900, "caption": "FAQ Schema for AI Search: A Practical 2026 Playbook", "creator": { "@id": "https://alicelabs.ai/#organization" }, "representativeOfPage": true, "license": "https://alicelabs.ai/terms" }, "mainEntityOfPage": { "@type": "WebPage", "@id": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search" }, "inLanguage": "en", "articleSection": "ai-search", "keywords": "faq schema ai search, faqpage schema, faq markup ai, structured faq for llms, faq schema 2026, faq schema chatgpt, faq schema perplexity", "about": [ { "@type": "Thing", "name": "Why FAQ Schema Still Matters in 2026 (Despite Google Narrowing Rich Results)", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#why-faq-schema-still-matters-2026" }, { "@type": "Thing", "name": "The 5 Use Cases for FAQ Schema in 2026", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#five-use-cases-for-faq-schema" }, { "@type": "Thing", "name": "JSON-LD FAQPage Format (with Real, Validator-Tested Code)", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#json-ld-faqpage-with-real-code" }, { "@type": "Thing", "name": "Sourcing Real FAQs (PAA, GSC, Support Tickets, Sales Objections)", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#sourcing-real-faqs" }, { "@type": "Thing", "name": "Validation, Deployment, and Monitoring After Launch", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#validation-deployment-monitoring" } ], "mentions": [ { "@type": "Organization", "name": "Alice Labs", "url": "https://alicelabs.ai" }, { "@type": "Organization", "name": "Google", "url": "https://google.com" }, { "@type": "Product", "name": "ChatGPT", "url": "https://chatgpt.com" }, { "@type": "Product", "name": "Claude", "url": "https://claude.ai" }, { "@type": "Product", "name": "Google Gemini", "url": "https://gemini.google.com" }, { "@type": "Person", "name": "Eric Lundberg", "url": "https://linkedin.com/in/eric-lundberg-3530451bb" }, { "@type": "Organization", "name": "Linus Ingemarsson" }, { "@type": "Organization", "name": "Inventory current FAQs across your pages" }, { "@type": "Organization", "name": "Write self-contained answers" }, { "@type": "Organization", "name": "Monitor LLM citations of your FAQ content" } ], "hasPart": [ { "@type": "WebPageElement", "isAccessibleForFree": true, "name": "Why FAQ Schema Still Matters in 2026 (Despite Google Narrowing Rich Results)", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#why-faq-schema-still-matters-2026", "description": "FAQ Rich Results in Google SERPs were narrowed in August 2023 to well-known authoritative government and health websites. But FAQPage schema is still parsed by ChatGPT, Claude, Perplexity, Gemini, and AI Overviews as citable Q-A units — and it powers voice search and site UX. The schema is alive; only the SERP enhancement narrowed." }, { "@type": "WebPageElement", "isAccessibleForFree": true, "name": "The 5 Use Cases for FAQ Schema in 2026", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#five-use-cases-for-faq-schema", "description": "FAQPage schema serves five distinct use cases beyond traditional Google Rich Results: Google AI Overviews citation, ChatGPT/Claude/Perplexity retrieval, voice search assistants, on-site UX (collapsible accordions), and internal site structure for knowledge bases or help centres. Each use case justifies the markup independently." }, { "@type": "WebPageElement", "isAccessibleForFree": true, "name": "JSON-LD FAQPage Format (with Real, Validator-Tested Code)", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#json-ld-faqpage-with-real-code", "description": "A valid FAQPage JSON-LD block uses Schema.org's FAQPage type, a mainEntity array of Question entities, and each Question must include name (the question text) and acceptedAnswer (an Answer entity with a text field). Use JSON-LD because Google explicitly recommends it over Microdata and RDFa." }, { "@type": "WebPageElement", "isAccessibleForFree": true, "name": "Sourcing Real FAQs (PAA, GSC, Support Tickets, Sales Objections)", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#sourcing-real-faqs", "description": "Real FAQs sourced from search and customer data outperform invented ones in both LLM citation rates and on-page engagement. The four reliable sources are Google's People Also Ask, Search Console queries report, customer support tickets and chat logs, and sales objection notes from your CRM." }, { "@type": "WebPageElement", "isAccessibleForFree": true, "name": "Validation, Deployment, and Monitoring After Launch", "url": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#validation-deployment-monitoring", "description": "Validate every FAQPage block with Google's Rich Results Test and validator.schema.org before deployment. Deploy via JSON-LD in either or before . After launch, monitor coverage in Search Console and run prompt audits in ChatGPT, Claude, Perplexity, and AI Overviews to track LLM citation lifts." } ], "speakable": { "@type": "SpeakableSpecification", "cssSelector": [ "[data-speakable='true']", "[data-snippet='true']", "[data-section-answer='true']", ".quick-answer", "h1" ] } }, { "@type": "BreadcrumbList", "@id": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://alicelabs.ai/en" }, { "@type": "ListItem", "position": 2, "name": "Insights", "item": "https://alicelabs.ai/en/insights" }, { "@type": "ListItem", "position": 3, "name": "ai-search", "item": "https://alicelabs.ai/en/insights/ai-search" }, { "@type": "ListItem", "position": 4, "name": "FAQ Schema for AI Search: A Practical 2026 Playbook", "item": "https://alicelabs.ai/en/insights/faq-schema-for-ai-search" } ] }, { "@type": "Person", "@id": "https://alicelabs.ai/#eric", "name": "Eric Lundberg", "jobTitle": "Co-Founder", "worksFor": { "@id": "https://alicelabs.ai/#organization" }, "knowsAbout": [ { "@type": "DefinedTerm", "name": "AI automation", "url": "https://www.wikidata.org/wiki/Q1322483" }, { "@type": "DefinedTerm", "name": "Workflow automation", "url": "https://www.wikidata.org/wiki/Q120427660" }, { "@type": "DefinedTerm", "name": "Retrieval-Augmented Generation", "url": "https://www.wikidata.org/wiki/Q117761563" }, { "@type": "DefinedTerm", "name": "Enterprise AI implementation" } ], "sameAs": [ "https://www.linkedin.com/in/eric-lundberg-3530451bb/", "https://www.wikidata.org/wiki/Q140369978" ] }, { "@type": "Person", "@id": "https://alicelabs.ai/#linus", "name": "Linus Ingemarsson", "jobTitle": "Co-Founder", "worksFor": { "@id": "https://alicelabs.ai/#organization" }, "knowsAbout": [ { "@type": "DefinedTerm", "name": "AI agent orchestration", "url": "https://www.wikidata.org/wiki/Q98678395" }, { "@type": "DefinedTerm", "name": "AI strategy" }, { "@type": "DefinedTerm", "name": "AI search optimization (LLMO)" }, { "@type": "DefinedTerm", "name": "Enterprise AI strategy" } ], "sameAs": [ "https://www.linkedin.com/in/linus-ingemarsson/", "https://www.wikidata.org/wiki/Q140369914" ] }, { "@type": "Person", "@id": "https://alicelabs.ai/#alice", "name": "Alice Holmgren", "jobTitle": "CEO", "worksFor": { "@id": "https://alicelabs.ai/#organization" }, "knowsAbout": [ { "@type": "DefinedTerm", "name": "Nordic AI consulting market" }, { "@type": "DefinedTerm", "name": "AI strategy leadership" }, { "@type": "DefinedTerm", "name": "Enterprise transformation" } ] }, { "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Does FAQ schema still work in 2026?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Google narrowed FAQ Rich Results in August 2023 to well-known authoritative government and health websites, but FAQPage schema itself is still parsed by ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews. The schema vocabulary is alive at schema.org/FAQPage; only the SERP enhancement narrowed." } }, { "@type": "Question", "name": "Why did Google narrow FAQ Rich Results in 2023?", "acceptedAnswer": { "@type": "Answer", "text": "Per Google Search Central, FAQ Rich Results were narrowed in August 2023 to reduce SERP clutter and prioritise authoritative sources. They now appear primarily for well-known, authoritative government and health websites. The change affected the visual SERP feature, not the underlying FAQPage schema vocabulary." } }, { "@type": "Question", "name": "How many FAQs should I include per page?", "acceptedAnswer": { "@type": "Answer", "text": "Five to ten FAQs per page is the typical sweet spot. Fewer and the schema lacks coverage; more and answer quality often degrades. Each answer should be 50-80 words, self-contained, and based on a real user question sourced from PAA, GSC queries, or support tickets — not invented to fill space." } }, { "@type": "Question", "name": "Where should I place FAQPage JSON-LD on the page?", "acceptedAnswer": { "@type": "Answer", "text": "Place the JSON-LD inside a ``` ### Required fields - **@context.** Always`https://schema.org`. - **@type.** Must be FAQPage at the root. - **mainEntity.** An array of Question entities. At least one is required; in practice, ship 5-10. - **Question.name.** The question text. Phrase it as a real user would. - **Question.acceptedAnswer.** An Answer entity with a text property. Without this, the Question is invalid. ### Optional but useful - **inLanguage.** Add an inLanguage property at the FAQPage level for multilingual sites. - **about.** Reference the entity the FAQ is about (Person, Organization, Product) to enrich the knowledge graph. - **dateModified.** Helpful when FAQs change. Most sites attach this to the parent Article schema instead. Place the entire script tag in the page `` or just before ``. Both work. Server-side rendering is preferred so parsers see the markup on first byte. Avoid HTML inside answer text — keep it plain Schema.org's Answer.text accepts limited inline HTML, but plain text is safest. Strip out spans, divs, and inline styles before serialising. Some validators warn on
and

tags inside the text field. Plain prose extracts cleanly to LLMs and avoids markup brittleness. ![Linus Ingemarsson](/images/linus-ingemarsson.png)![Eric Lundberg](/images/eric-lundberg.png)![Alice Holmgren](/images/alice-holmgren.png) Alice Labs practitioner team ## Need help deploying FAQ schema across your site? We source real FAQs from your GSC, support tickets, and PAA data, write LLM-ready answers, validate the JSON-LD with Rich Results Test, and ship through your CMS — typically in one to two weeks. Benchmarked against the Alice Labs LLMO Citation Benchmark across 100 SaaS brands. [Request a FAQ schema audit](#contact) 04 / 05 Step ## Sourcing Real FAQs (PAA, GSC, Support Tickets, Sales Objections) In short Real FAQs sourced from search and customer data outperform invented ones in both LLM citation rates and on-page engagement. The four reliable sources are Google's People Also Ask, Search Console queries report, customer support tickets and chat logs, and sales objection notes from your CRM. The biggest mistake we see in FAQ schema deployments is invented questions. Marketers brainstorm what readers might ask, and the result is generic, low-search-volume FAQs no real user actually queries. Source from data instead. Four channels, all reliable: ### 1\. Google's People Also Ask (PAA) For every target query, Google surfaces a PAA box with related questions actual users ask. Click each one to see the next layer of related questions. Three to five rounds of expansion gives you 20-40 real, search-validated questions per query. Tools like AlsoAsked or AnswerThePublic automate this. Manual extraction from SERPs is also fine for small batches. ### 2\. Google Search Console queries report Filter your GSC Performance report for queries containing question words: what, how, why, when, where, can, does, is, should. These are real queries that already brought users to your site. Marking up answers to your existing GSC questions is one of the highest-ROI SEO moves available. ### 3\. Customer support tickets and chat logs Your support team knows the real questions. Pull the top 50 tickets from the past quarter. Cluster them by intent. The clusters become your highest-value FAQ candidates — questions real customers ask, paid support agents currently answer, and which absolutely deserve structured Q-A on your site. ### 4\. Sales objection notes Your sales team has a different-but-overlapping set of recurring questions. Pricing, integrations, security, comparison vs competitors. These are MOFU and BOFU FAQ candidates. Marked-up answers to common objections feed both your sales motion and the LLMs your prospects will increasingly ask. Combine all four sources into a single backlog. Deduplicate. Rank by search volume + ticket volume. Ship the top 5-10 per page. Don't duplicate FAQ content across pages Each FAQ should live on one canonical page. Copying the same Q-A across multiple pages dilutes the signal and triggers content-duplication concerns. If multiple pages need the same answer, link to the canonical FAQ page instead of repeating the schema. Match the user's language, not your brand voice Use the exact phrasing from PAA, GSC, and support tickets. If users ask 'how much does it cost?' do not rewrite that as 'what is your pricing?'. Match the source phrasing — that is what LLMs match against when retrieving for similar queries. 05 / 05 Step ## Validation, Deployment, and Monitoring After Launch In short Validate every FAQPage block with Google's Rich Results Test and validator.schema.org before deployment. Deploy via JSON-LD in either or before . After launch, monitor coverage in Search Console and run prompt audits in ChatGPT, Claude, Perplexity, and AI Overviews to track LLM citation lifts. Three steps after you have written the JSON-LD: validate, deploy, monitor. Skipping any of them is how schema silently breaks. ### Validate with two tools 1. **Google Rich Results Test.** At search.google.com/test/rich-results. Paste the URL or the raw JSON-LD. The tool reports Google-eligibility plus errors and warnings. Fix everything before deploying. 2. **validator.schema.org.** The official Schema.org validator. Stricter on pure vocabulary compliance. Useful for catching unrecognised properties or wrong @type values. Common failures we see in audits: - **Question without acceptedAnswer.** The most common failure. Every Question needs a complete Answer entity. - **Smart quotes inside JSON.** Curly quotes ("smart quotes") break JSON parsers. Use straight ASCII quotes only. - **Trailing commas.** Valid in JavaScript objects but not in JSON. Fails parsing silently. - **HTML entities in text.** Unescaped ampersands and angle brackets in answer text break the JSON. Use plain text or escape properly. ### Deploy via JSON-LD script tag Place the script tag in either the `` or just before ``. Both work. WordPress users can use Yoast or Rank Math; Next.js sites can use Next SEO or inline scripts; Webflow sites can use Custom Code. Server-side rendering is preferred so parsers see the markup on the first byte. ### Monitor coverage and citations Two monitoring streams: - **Search Console Enhancements.** Reports structured data coverage and errors. Check weekly. Fix errors immediately — they propagate fast. - **LLM citation tracking.** Run prompt audits — ask each engine the questions your FAQs answer, log whether your domain appears as a source. Tools like Otterly.ai or Profound automate this. A 30-90 day baseline is enough to see whether the schema is correlating with citation lifts. Quarterly, refresh questions, prune dead FAQs, and rewrite answers that lost citations. The schema is a living asset, not a one-time deploy. Aggarwal et al. 2024 (GEO paper) Up to 40% visibility lift in generative engines from citation-rich, structured content. The lift applies broadly to citation tactics — inline statistics, named sources, structured markup. FAQ schema is one tactic in the broader citation-richness category, not a standalone driver of the 40%. arxiv.org/abs/2311.09735 ## About the Authors & Reviewers Published May 6, 2026 · Updated May 13, 2026 Written by ![Linus Ingemarsson - Co-Founder, Alice Labs at Alice Labs](/images/linus-ingemarsson.png) [Linus Ingemarsson](https://www.linkedin.com/in/linus-ingemarsson/) Co-Founder, Alice Labs Co-Founder at Alice Labs. Author of 7 research reports on AI adoption, governance and labor markets cited across EU, OECD and US benchmarks. - 8+ years in AI strategy & implementation - Top-5 AI Speaker, Sweden (Mindley 2025) - 100+ enterprise AI engagements [View profile](https://www.linkedin.com/in/linus-ingemarsson/) [](https://www.linkedin.com/in/linus-ingemarsson/)[](mailto:linus@alicelabs.ai) Reviewed by May 13, 2026 ![Eric Lundberg - Co-Founder, Alice Labs at Alice Labs](/images/eric-lundberg.png) [Eric Lundberg](https://www.linkedin.com/in/eric-lundberg-3530451bb/) Co-Founder, Alice Labs Co-Founder at Alice Labs. Builds AI automation, agent workflows and integration systems that hold up in real business operations. - AI automation & agent systems lead - Workflow design across 100+ deployments - Specialist in RAG, integrations & APIs [View profile](https://www.linkedin.com/in/eric-lundberg-3530451bb/) [](https://www.linkedin.com/in/eric-lundberg-3530451bb/)[](mailto:eric@alicelabs.ai) Published May 6, 2026 · Updated May 13, 2026 Reviewed for technical accuracy, methodology and source integrity. · All claims trace to public sources cited in-line. ## Frequently Asked Questions ### Does FAQ schema still work in 2026? ▾ Yes. Google narrowed FAQ Rich Results in August 2023 to well-known authoritative government and health websites, but FAQPage schema itself is still parsed by ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews. The schema vocabulary is alive at schema.org/FAQPage; only the SERP enhancement narrowed. ### Why did Google narrow FAQ Rich Results in 2023? ▾ Per Google Search Central, FAQ Rich Results were narrowed in August 2023 to reduce SERP clutter and prioritise authoritative sources. They now appear primarily for well-known, authoritative government and health websites. The change affected the visual SERP feature, not the underlying FAQPage schema vocabulary. ### How many FAQs should I include per page? ▾ Five to ten FAQs per page is the typical sweet spot. Fewer and the schema lacks coverage; more and answer quality often degrades. Each answer should be 50-80 words, self-contained, and based on a real user question sourced from PAA, GSC queries, or support tickets — not invented to fill space. ### Where should I place FAQPage JSON-LD on the page? ▾ Place the JSON-LD inside a