| 开发者 | erinkwon1 |
|---|---|
| 更新时间 | 2026年5月9日 04:04 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<head>. No coding. No guesswork. No plugin conflicts. Then run the dual SEO + GEO analyzer to see exactly how AI-citation-ready your FAQs are before you publish.
Why FAQs Matter for SEO
Google's FAQ rich results can double your click-through rate by showing Q&A snippets directly in search results. But to qualify, your page needs properly formatted structured data — the kind that typically requires a developer to set up manually.
This plugin makes that automatic.
What Makes This Plugin Different
Most FAQ plugins just display pretty accordions. This one goes further:
<head> — exactly the format Google requires for rich results. You don't touch any code.
Multiple OpenAI Models
Choose the model that fits your needs and budget:
gpt-4o-mini — Fastest, lowest cost. Great for most blogs.gpt-4o — Multimodal flagship, balanced quality and cost.gpt-4.1-mini — Upgraded mini with a larger context window.gpt-4.1 — Flagship model. Best quality for competitive niches.o3-mini — Reasoning model. Good for complex topics.o3 — Most capable reasoning model.o4-mini — Latest lightweight reasoning model.{count} as a placeholder for the number of FAQs. The plugin always enforces JSON formatting automatically.
Target Keyword Optimization
Set a target keyword per block (or let AI detect it from your content). The quality analyzer then checks whether your FAQs are properly optimized around that keyword.
Who Is This For?
mkjb-ai-seo-faq-schema folder to /wp-content/plugins/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 your pages the structured data they need to qualify for Google's FAQ rich results — expanded Q&A snippets that appear directly in search. These can significantly increase click-through rates. That said, Google decides whether to show rich results based on their own criteria; the plugin ensures your schema is valid and properly formatted.
Very little for typical use. With gpt-4o-mini, 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 markup that passes Google's Rich Results Test. You can verify any page at search.google.com/test/rich-results.
Absolutely. The generated FAQs are fully editable directly in the block editor. Change any question or answer, reorder them, or delete individual entries anytime.
Yes. The plugin uses a native Gutenberg block with server-side rendering, so it works with any WordPress theme. No shortcodes, no theme customizations required.
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 preserved in your posts — it won't disappear. However, the schema injection and visual display will stop working until you reactivate. Your settings (API key, model, etc.) are also saved and restored on reactivation.
Your FAQ content inside posts is preserved. Plugin settings (API key, model, prompt, style preferences) are removed from the database on deletion, as per WordPress best practices.
Yes. The plugin is standard GPL software with no license key or site limit. Install it on as many WordPress sites as you want.
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.
The analyzer runs 12 checks across three categories:
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 Google ranking factors: question format, answer length, direct first sentence, keyword placement, sentence length, duplicate detection, and so on. It tells you if your FAQ qualifies for Google's FAQ rich results. 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, which is exactly what Google's Rich Results Test expects. 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.
registerBlockType and the PHP register_block_type calls). WordPress 7.0 enforces full iframe isolation for the block editor and deprecates apiVersion 1 and 2; this release pre-emptively switches the FAQ block to apiVersion 3 so it keeps working when 7.0 lands. No user-visible behaviour change — the block already used useBlockProps and only wp.* globals (no document.querySelector etc.), so iframe isolation has no impact.the_content filter at priority 100 that scans for the FAQ block class and injects the inline stylesheet when needed. End result: FAQ styling now reaches the browser whether the block is dynamic, static HTML, translated, or pasted from another post.