AI FAQ Schema - AEO & GEO for AI Search

No — not for everything. The "I Have FAQ" (paste mode) and "Manual Input" modes work without any API key. You only need a key for the "Auto Generate" mode and the AI keyword detection feature. You can get an API key at platform.openai.com/api-keys.

It gives AI engines — Google AI Overviews, ChatGPT, Perplexity, Claude — clean, structured, citation-ready Q&A content, plus valid FAQPage schema. Studies show well-structured FAQ content is cited significantly more often in AI answers than plain prose. It won't directly change your Google keyword rankings; its job is to make your answers the ones AI assistants quote. Note: Google retired FAQ rich results from Search in 2026, so this plugin is built for AI citation (AEO/GEO) and page understanding, not a Google visual snippet.

llms.txt (llmstxt.org convention) is a plain-text index of your site - your pages and latest posts with one-line summaries - served at yoursite.com/llms.txt. AI crawlers such as ChatGPT, Claude, and Perplexity read it to quickly understand what your site covers. This plugin generates and serves it automatically, keeps it updated as you publish, and needs no API key. If you already have a physical llms.txt file, the plugin never overrides it.

Yes. Settings - AI FAQ Schema lists 13 known AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Bytespider, meta-externalagent, Amazonbot and more) with a Block checkbox each. Checking one adds a Disallow rule for that bot to your site's robots.txt. Each row explains the trade-off - for example, blocking OAI-SearchBot removes you from ChatGPT Search results. Blocking Google-Extended does NOT affect your normal Google Search ranking.

They are different bots for different jobs. Blocking a TRAINING crawler (GPTBot, CCBot, Bytespider) stops your content being used to train future models, while SEARCH crawlers (OAI-SearchBot, PerplexityBot) are what get you cited in live AI answers. The table separates them so you can, say, block training bots but stay visible in AI search. By default everything is allowed.

Very little for typical use. With gpt-5.6-luna, generating 5 FAQs from a blog post costs a fraction of a cent. Even a high-traffic content site generating hundreds of FAQs per month would spend just a few dollars. You only pay when you click "Generate" — never in the background.

Yes. The plugin outputs standard schema.org FAQPage JSON-LD that validates on the Schema.org validator and is consumed by Bing and the AI assistants built on its index. Note: Google retired FAQ rich results from Search (and removed FAQPage from its Rich Results Test) in 2026, so the markup no longer produces a Google visual snippet — today its value is page understanding and AI-search citation (AEO/GEO), not a Google rich result.

Yes. This plugin is fully compatible with Yoast SEO, RankMath, and other SEO plugins. It injects its own FAQPage JSON-LD schema independently. Just make sure you're not also generating FAQ schema from your SEO plugin for the same page — otherwise you may end up with duplicate structured data. If you're only using Yoast or RankMath for general SEO (title tags, meta descriptions, sitemaps), there's no conflict at all.

No — this plugin requires the WordPress Block Editor (Gutenberg). It is a native Gutenberg block and does not work with the Classic Editor plugin. If your site uses the Classic Editor, you would need to switch to the block editor to use this plugin.

Your FAQ content is always preserved in your posts — it never disappears. On deactivation, schema injection and the visual display simply pause until you reactivate, and all settings are kept. On deletion, plugin settings (API key, model, prompt, style preferences) are removed from the database per WordPress best practices, but the FAQ text in your posts stays.

Not always — AI output quality depends on your content and prompt. That's why the built-in FAQ Quality Analyzer exists. Run it before you publish and follow the recommendations to improve your score. You can also edit any generated FAQ manually.

No. Content is only sent to OpenAI when you click "Generate FAQ" or "AI Detect." Nothing is sent automatically in the background.

The SEO score (out of 100) checks 12 traditional ranking factors: question format, answer length, direct first sentence, keyword placement, sentence length, duplicate detection, and so on. It tells you how well-structured your FAQ is for search engines and featured-snippet-style extraction. The GEO score (out of 100) checks 8 AI-citation factors that matter when ChatGPT, Perplexity, Google AI Overview, or Claude decides whether to quote you. These include: filler-word detection, citation-window length (8-60 words is the sweet spot AI assistants prefer), self-contained answers (no "as mentioned above"), specificity and E-E-A-T signals, pronoun ambiguity, and structured multi-sentence formatting. Both scores display side by side, and clicking either one shows a detailed per-FAQ breakdown.

No. Schema generation runs once per post when you save, then the JSON-LD is cached as post metadata. On every page view, the plugin reads the cache directly instead of re-parsing your block content. The frontend overhead is a single small <script type="application/ld+json"> tag in the page head — the standard schema.org format. The CSS for display styles is also enqueued only on pages that actually contain a FAQ block.

Yes. The schema markup is language-agnostic — Google reads FAQPage schema correctly in any language. The AI generation also works in any language OpenAI supports (60+ languages); if your post content is in Korean, Japanese, Spanish, French, German, etc., the generated FAQs will be in the same language. The "I Have FAQ" paste mode also accepts FAQs in any language.