CapstonAI is an AI visibility platform that helps brands track, audit, and optimize their presence in AI-generated answers. It monitors how your brand is mentioned across ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews, then provides actionable fixes to improve your share of voice in AI search results.

How does CapstonAI track AI visibility?

CapstonAI sends structured brand queries to multiple large language models (LLMs) on a recurring basis and records whether your brand is mentioned, cited, or recommended. It aggregates these results into a GEO score, a share-of-voice metric, and a citation report.

Which AI models does CapstonAI monitor?

CapstonAI currently monitors ChatGPT (OpenAI), Claude (Anthropic), Gemini (Google), Perplexity, and Google AI Overviews. Coverage is continuously expanded as new AI search surfaces emerge.

CapstonAI offers a free WordPress plugin that provides basic AI visibility scanning for your site. For full AI visibility tracking, audit reports, automated content fixes, and multi-brand monitoring, the Core Plan is available at $99/month.

How is CapstonAI different from Semrush or Ahrefs?

Semrush and Ahrefs are built for traditional search engine optimization. CapstonAI is purpose-built for the AI search era: it tracks your brand presence inside AI-generated answers from ChatGPT, Claude, Gemini, and Perplexity.

How To Create FAQ Schema For AI Engines In 2026: Complete Implementation Guide

How to Create FAQ Schema for AI Engines in 2026: Complete Implementation Guide

FAQPage schema is the single highest-leverage structured data type for AI search visibility in 2026. CapstonAI’s Q1 2026 cohort benchmark across 86 customers shows pages with proper FAQPage schema get cited 1.9× more by ChatGPT, 2.3× more by Perplexity, and appear 3.1× more often in Google AI Overviews. Yet 78% of B2B sites and 84% of D2C sites have no FAQPage schema at all. Here’s the complete 2026 implementation guide — what to ask, how to structure, common mistakes, and copy-paste examples.

TL;DR: Create FAQ schema by: (1) identifying real questions buyers ask (not what you wish they’d ask), (2) writing direct 40-100 word answers, (3) wrapping in FAQPage JSON-LD, (4) keeping HTML + JSON-LD content identical, (5) placing on pricing/comparison/condition/product pages, (6) updating quarterly, (7) avoiding the cardinal sins (FAQ outside actual page content, robotic tone, marketing-speak).

Free CapstonAI scan → Pricing

The 7-step playbook

Step 1: Source real questions (not invented ones). Pull questions from: GSC People Also Ask data, sales team Slack on objections, support tickets, Reddit threads in your category, AnswerThePublic, ChatGPT prompts you can audit. Real questions = real citation rate.
Step 2: Write direct, scannable answers (40-100 words). First sentence = direct answer. Following sentences = supporting context. Avoid “It depends” openers — AI engines don’t cite hedged content. Cite a specific number or example whenever possible.
Step 3: Use FAQPage JSON-LD (not Microdata or RDFa). JSON-LD is preferred by Google + AI engines. Plugins (Yoast, Rank Math, CapstonAI) generate this automatically. Manual implementation:
Step 4: Render the same content in HTML (not just schema). Google’s June 2023 policy and AI engines treat hidden FAQ schema (JSON-LD only, no on-page HTML) as low-quality. Always show the FAQ on-page in

question

+

answer

format.
Step 5: Place on the right pages. Highest impact: pricing pages, comparison pages, condition/use-case pages, location pages, product pages with sales objections, technical doc pages. Lowest impact: blog posts (use HowTo schema instead).
Step 6: Avoid the 5 cardinal sins of FAQ schema. (1) FAQ content not visible on the page, (2) marketing-speak instead of direct answers, (3) only 1 question (need 3+ for citation lift), (4) duplicate FAQs across pages, (5) outdated answers (refresh quarterly).
Step 7: Test + monitor. Validate schema with Google Rich Results Test. Monitor citation lift with AI tracking tools. Iterate on the questions that don’t earn citations.

Concrete case study

Real customer pattern (anonymized) showing the impact of this playbook over one quarter:

Metric	Before FAQ schema	After FAQ schema (90 days)	Delta
ChatGPT citations on pricing/comparison pages (panel of 30)	4	17	+13
Perplexity citations	6	23	+17
Google AI Overview appearances	2	11	+9
“People Also Ask” appearances (Google)	8	28	+20
Featured snippet wins on FAQ-eligible queries	3	14	+11

Common errors when optimizing for FAQPage schema

Inventing questions instead of sourcing real ones. Made-up FAQ that nobody asks earns nothing. Source from GSC, sales, support, Reddit.
Schema-only with no visible HTML FAQ. Google penalizes since 2023. AI engines also downrank. Always show FAQ on-page.
Marketing-speak in answers. “Our innovative solution leverages…” gets skipped. Direct answer first, then context.
Single FAQ entry. FAQPage schema needs 3+ questions to be effective. Single Q&A = no citation lift.
Stale FAQs. FAQ that says “In 2023…” in 2026 = downrank. Refresh quarterly.

FAQ — FAQPage schema

Does FAQPage schema still work after Google’s 2023 changes?

Yes for AI engines (ChatGPT, Perplexity, Claude). Google itself reduced FAQ rich-result eligibility in 2023 but AI Overviews still pull from FAQPage schema heavily. Net positive.

How many questions per FAQ section?

Sweet spot: 5-8 questions per page. Less than 3 = no schema lift. More than 10 = diluted attention. Match the buyer questions for that specific page.

Should every page have FAQ schema?

No. Only pages with genuine question-shaped content. Forced FAQ on category pages without real questions = low-quality signal.

Tools and related reading

Ready to optimize for FAQPage schema?

Free CapstonAI scan →

Last updated: May 2026. Sources: CapstonAI Q1 2026 cohort (86 customers, 24 800 LLM responses analyzed), engine disclosures, Search Engine Land × CapstonAI analysis, vendor documentation.