AI-Powered Schema Markup & FAQ Generator #
Generate complete JSON-LD schema markup and FAQ structured data for any post or page using AI — directly from the Gutenberg block editor sidebar panel.
Location #
| WordPress Admin → Posts / Pages → Gutenberg Block Editor → Click SchemaEngine AI logo (top-right toolbar) → SchemaEngine AI panel |
✨ AI-Powered Schema & FAQ Generation #
SchemaEngine AI reads the content of your post or page in real time and uses AI to generate semantically correct schema.org JSON-LD markup — without requiring you to manually fill in any schema fields. It also generates FAQ structured data and automatically populates SchemaEngine AI’s own Gutenberg FAQ block on the page.
This is a Pro feature. Before using AI Generator, you need to add Your Own AI KEY
Workflow Overview #
1. Opening the SchemaEngine AI Panel
2. Panel Controls — Schema Type & FAQ Settings
3. Choose an Action — Generation Modes
5. Review & Save the Generated Schema
1. Opening the SchemaEngine AI Panel #
The SchemaEngine AI generation panel is a sidebar that opens within the Gutenberg block editor. It does not require navigating away from the post — everything happens alongside your content.
| 1 | Open the Gutenberg block editor Edit any post or page using the WordPress block editor (Gutenberg). The panel is not available in the Classic Editor. |
| 2 | Click the SchemaEngine AI logo in the editor top bar The SchemaEngine AI icon (purple logo) appears in the top-right toolbar of the block editor alongside other editor controls. Click it to open the SchemaEngine AI sidebar panel on the right side of the screen. |
| 3 | The panel opens on the right The SchemaEngine AI panel slides open, showing the plugin branding at the top, a generation status indicator, and the configuration controls below. The panel remains open as you scroll or edit the post content. |
Figure 14.1 — SchemaEngine AI panel open in the Gutenberg editor showing Auto-detect schema type, FAQ settings, and three action options
2. Panel Controls — Schema Type & FAQ Settings #
Before generating, review the two configuration controls in the panel.
Schema Type
| Option | Description |
|---|---|
| ✨ Auto-detect (AI) | Default. The AI reads the post content and title and automatically selects the most appropriate schema.org type (e.g. BlogPosting, HowTo, Product, FAQPage, Recipe). Recommended for most posts. |
| Manual selection | Open the Schema Type dropdown to choose a specific schema type. Use this when you know the exact type needed and want to override the AI detection — for example, forcing Recipe schema on a post the AI might classify as an Article. |
FAQ Settings — Number of FAQs #
| Control | Description |
|---|---|
| Number of FAQs | A +/− stepper control to set how many FAQ question-and-answer pairs the AI should generate. Default: 8. Range: typically 1–20. Only relevant when the action includes FAQ generation (Schema + FAQs or FAQs Only). |
💡 How many FAQs to generate?
8 FAQs is a good default for most blog posts and landing pages. For short posts, reduce to 3–5. For comprehensive guides or comparison articles, increase to 10–15. Google typically shows up to 3–5 FAQ rich result dropdowns in search results, but having more in the markup increases the likelihood that relevant ones are picked.
3. Choose an Action — Generation Modes #
Three generation modes are available. Select the one that fits your needs before clicking Generate.
★ Schema + FAQs ★ Recommended #
Complete structured data and FAQ block — generates full JSON-LD schema markup AND the specified number of FAQ question-answer pairs. The FAQ data is automatically injected into SchemaEngine AI’s Gutenberg FAQ block on the page. Recommended for blog posts, guides, and product pages.
| { } Schema Only JSON-LD structured data only — generates the schema markup without any FAQ content. Use this for posts that do not benefit from FAQ schema (e.g. portfolio items, news articles without Q&A content, product listings). |
| ? FAQs Only 8 question/answer pairs only — generates only the FAQ content without regenerating the schema. Use this to add or refresh FAQs on a page that already has correct schema, or when you want to update the FAQ block independently. |
| Use case | Schema + FAQs | Schema Only | FAQs Only |
|---|---|---|---|
| New blog post or guide | ✔ Recommended | ○ Use if no FAQs needed | — |
| Product / landing page | ✔ Recommended | ○ Alternative | — |
| News article | — | ✔ Recommended | — |
| Post already has correct schema | — | — | ✔ Refresh FAQs |
| Post without FAQ content | — | ✔ Recommended | — |
| Updating FAQs only after content change | — | — | ✔ Recommended |
4. Generate — AI Processing #
Once the Schema Type and action are configured, click Generate to start the AI processing.
| 4 | Click the GENERATE → button The large purple Generate button at the bottom of the panel sends the post content to the AI for analysis. Processing time depends on post length — typically 3–10 seconds for most posts. A status indicator appears in the panel while the AI works. Status during generation: “Generated — not saved yet PENDING” label appears in amber at the top of the panel, confirming the AI has completed generation but the schema has not yet been saved to the post. |
💡 The AI reads your actual post content
SchemaEngine AI does not generate generic placeholder schema. The AI analyses the real title, headings, body text, images, and metadata of the current post to produce schema values specific to this content — including the actual headline, description, author, datePublished, image URL, and wordCount properties.
5. Review & Save the Generated Schema #
After generation completes, a JSON-LD Schema modal appears automatically displaying the generated markup. Review it before saving.
Figure 2 — Generated JSON-LD Schema modal showing 232 lines and 6 schema types with Save Schema button
| 5 | Review the generated schema in the modal The JSON-LD Schema modal opens showing the complete generated output. Check that the detected schema types are correct, property values (headline, description, image, author) are accurate, and the overall structure looks correct. The status bar shows the total line count and number of schema types generated. Available actions in this modal: Preview — read-only view of the generated JSON-LD (default) Edit — modify the generated schema before saving Copy — copy the JSON-LD to clipboard Test — open Google’s Rich Results Test with this schema |
| 6 | Click Save Schema to apply the generated schema to the post The Save Schema button (purple, bottom-right of the modal) saves the generated JSON-LD to the post. The modal closes and the SchemaEngine AI panel updates to show the Schema Health dashboard. The post still needs to be saved/updated in WordPress using the Save or Update button in the editor top bar. Important: Clicking Save Schema saves the schema data but does not publish or update the WordPress post itself. Click the WordPress Save / Update button in the editor top bar to publish the changes. |
6. Schema Health after Save #
After clicking Save Schema, the panel transitions from the generation view to the Schema Health dashboard — giving immediate feedback on the quality of the saved schema.
Figure 3 — SchemaEngine AI panel showing Schema Health dashboard after saving: AI Confidence 100%, Valid Schema 100/100 (A+), Rich Result Readiness 99/100 (A)
AI Confidence Score #
The AI Confidence score is a new indicator that appears in the panel after AI generation. It reflects how certain the AI is that the generated schema is appropriate for this post type and content.
| AI Confidence | What it means | Recommended action |
|---|---|---|
| 100% | AI is certain about the schema type and all generated property values | Save and publish — schema is optimal |
| 85–99% | AI is highly confident — minor ambiguity in a few properties | Review the schema preview, then save |
| 70–84% | AI detected some ambiguity — post content may be mixed-topic | Review carefully, edit if needed before saving |
| < 70% | AI is uncertain — post content may be too short or ambiguous | Consider switching Schema Type from Auto-detect to manual and regenerating |
Schema Health scores after AI generation #
- Valid Schema (100/100 · A+) — All schema types generated by AI pass schema.org validation
- Rich Result Readiness (99/100 · A) — Schema is optimised for Google rich result eligibility based on 6 criteria
- Detected Types — shows the schema types the AI generated (e.g. Article · FAQPage)
- Readiness Breakdown — the same 6-criteria breakdown from Step 12 (Completeness, Rich Results, Cross-References, Content Depth, Identifiers, Graph Structure)
Action buttons in the health view: #
| Button | Action |
|---|---|
| 👁 View | Opens the JSON-LD Schema modal in Preview mode to inspect the saved schema |
| ✏️ Edit | Opens the schema in Edit mode to make manual adjustments after AI generation |
| 🗑 Delete Schema | Removes the saved schema from this post — use with caution. This cannot be undone without regenerating. |
| 🔍 Test in Google Rich Results | Opens Google’s Rich Results Test for the live page URL to validate the schema in Google’s own testing tool |
7. FAQ Block Integration with FAQPage Schema Markup #
❓ Automatic FAQ Block Population #
SchemaEngine AI includes its own native Gutenberg FAQ block. When you generate Schema + FAQs or FAQs Only, the AI-generated question-and-answer pairs are automatically inserted into this block on the page — no copy-pasting required. The FAQ block handles both the visible frontend display of the FAQ accordion and the FAQPage schema.org structured data output. This means your FAQs are both readable by visitors and machine-readable by search engines from a single block.
How FAQ block population works: #
- SchemaEngine AI analyses the post content and generates the requested number of relevant question-and-answer pairs.
- The FAQs are formatted as schema.org Question and acceptedAnswer entities within the FAQPage type.
- The generated FAQs are automatically inserted into the SchemaEngine AI FAQ block on the page — if the block does not exist yet, it is added automatically.
- The FAQ block renders the questions and answers as a visible, styled accordion section for readers.
- The same FAQ data is included in the page’s JSON-LD output as FAQPage schema markup for search engines.
Gutenberg FAQ Block #
- Native Gutenberg block — works without any page builder.
- FAQ data auto-populated by AI generation.
- Renders as a visible, styled FAQ accordion on the front end.
- Outputs FAQPage schema.org markup automatically.
- Fully editable — add, remove, or reorder questions in the block editor
Elementor Accordion Widget
- Elementor default Accordion widget for sites built with the Elementor page builder
- Supports the same FAQ schema output as the Gutenberg block.
- Drag-and-drop into any Elementor layout.
- FAQ content can be manually added or synced from the generated FAQs.
- Schema markup is handled by SchemaEngine AI — no separate schema plugin needed
💡 FAQ blocks improve AEO and GEO performance
FAQ schema is one of the most valuable structured data types for Answer Engine Optimisation (AEO) and Generative Engine Optimisation (GEO). Pages with FAQPage schema are significantly more likely to be cited as sources in Google AI Overviews, ChatGPT responses, and Perplexity answers — because the Q&A structure matches exactly how AI systems retrieve and present factual answers.
