FAQ schema was deprecated by Google for most content types in 2023-2024 and specifically ignored by AI engines in 2024-2026, which means the specific markup that many brands invested in heavily is now producing specifically zero AEO value. The specific replacement that captures the same Q&A pattern AI engines prefer is semantic HTML question-format headings paired with specific direct-answer body content — the same pattern described throughout this content without the specific JSON-LD markup wrapper. AI engines parse the specific HTML structure directly and extract the specific Q&A pairs from the specific headings and body content, which makes the specific schema layer unnecessary and sometimes counterproductive.
FAQ schema deprecated by Google in 2023-2024, ignored by AI engines. Replacement: semantic HTML question headings + direct-answer body. AI engines parse HTML structure directly. Specific brands still maintaining FAQ schema should prune and restructure.
Why specifically did Google deprecate FAQ schema for most content types?
Google specifically deprecated FAQ schema for most content types in 2023-2024 because the specific markup was being abused to produce artificially-prominent SERP rich results that did not match genuine user intent. Pages were adding FAQ schema with questions that were not real FAQ content, simply to capture the specific additional SERP real estate. Google's specific response was to restrict FAQ rich results to only specific authoritative source types (government and health authorities), which specifically removed the primary incentive for most brands to maintain the specific markup. The specific deprecation was not about the specific markup being technically broken; it was about Google specifically removing the specific SERP benefit that drove the specific implementation.
Why do AI engines specifically ignore FAQ schema even when it is implemented?
AI engines specifically ignore FAQ schema because the specific information the schema encodes — question-answer pairs — is already present in the specific HTML structure and body content, and the specific engines can extract the Q&A pattern directly without needing the specific JSON-LD wrapper. The specific schema is redundant with the semantic HTML signal. AI engines specifically prefer parsing the specific HTML directly because it produces the specific authentic reading of the content, while the specific schema is sometimes decoupled from the specific body (schema says one thing, body says another), which creates specific uncertainty about which specific version to trust. The specific engines resolve the ambiguity by relying on the specific HTML as the specific primary signal and treating the specific schema as supplementary.
What specifically is the HTML replacement that captures the Q&A pattern?
The HTML replacement is specifically to structure Q&A content as question-format H2 or H3 headings followed by direct-answer body paragraphs — the same specific chunk structure that applies to broader AEO content. 'What is a good DTC conversion rate?' as an H2 heading, followed by '[Direct answer]...' as the opening paragraph. The specific pattern provides AI engines with the specific question signal (heading) and the specific answer signal (first body sentence) in the specific HTML structure the engines parse directly. The specific pattern works for both dedicated FAQ sections (bottom-of-page Q&A clusters) and inline Q&A content (specific question-answer pairs embedded within broader article content). The specific structure is specifically simpler than FAQ schema implementation and specifically produces better extraction because the signal is the primary content rather than a secondary layer.
What should brands specifically do with their existing FAQ schema implementations?
1) Audit which specific pages currently have FAQ schema implemented. 2) For specific pages where the FAQ schema matches current body content (specific question-answer pairs in both schema and HTML), the specific schema is harmless but adds no value — removing it simplifies the specific page without reducing AEO. 3) For specific pages where the FAQ schema is decoupled from the body content (schema has questions that are not in the HTML, or body has questions that are not in the schema), the specific decoupling can confuse engines — remove the specific schema and ensure the specific body content has semantic HTML Q&A structure. 4) For specific pages where the FAQ schema was implemented primarily for SERP rich results (now deprecated), the specific schema can be removed entirely without affecting specific SEO or AEO. 5) Reinvest the specific operational attention from maintaining FAQ schema into specific question-format heading discipline across the content, which is where the specific AEO value sits.
What specifically are the two schema types that still help AEO for Q&A content?
Two specific schema types still help for Q&A content specifically where they apply. First, Article schema with specific entity references (the Article's about field pointing to specific topic entities, specific keywords, specific authors) specifically helps AI engines identify what the specific article discusses and attribute citations correctly. Second, HowTo schema specifically helps for sequential how-to content with specific numbered steps — this is specifically distinct from FAQ-style Q&A and specifically produces specific extraction for how-to queries. Beyond these two specific schema types, Q&A content in 2026 relies specifically on the semantic HTML structure (question-format headings, direct-answer bodies) rather than on specific schema markup. The specific lean approach to structured data is one of the specific operational simplifications that AEO specifically rewards.
What is the common mistake brands make when transitioning away from FAQ schema?
The common mistake is removing the specific FAQ schema without specifically restructuring the specific underlying content with question-format headings and direct answers, which produces pages that lose both the specific schema signal (now deprecated anyway) and specifically fail to add the specific HTML signal replacement. The specific result is pages that were AEO-neutral under the specific schema implementation becoming AEO-weak after the specific removal because no specific replacement structure is added. The right discipline is to specifically pair the specific schema removal with specific HTML restructuring in the same operational pass — remove the specific schema, add specific question-format headings, verify specific direct answers open each specific section, deploy together. The specific pairing produces specific net improvement rather than specific net regression.
Conclusion
FAQ schema deprecation is one of the specific technical shifts that most brands have not yet caught up with because the specific SEO advice from 2022-2023 recommended extensive FAQ schema implementation. The practical next step for any team currently maintaining extensive FAQ schema is to audit which specific pages use it, remove the specific schema from pages where it no longer applies, and restructure the specific underlying content with specific question-format headings and specific direct answers that capture the specific AEO value the schema no longer provides. In Advize's experience, the specific restructuring often produces specifically improved AI citations because the semantic HTML signal is specifically clearer than the specific schema wrapper was.