GEOforge

GEOforge generates JSON-LD schema markup and meta descriptions for the articles it publishes. WordPress strips inline <code><script></code> tags from post bodies (KSES sanitization) and hides underscore-prefixed meta from the REST API by default, so neither can be set by an external publishing tool without a companion plugin.
This plugin solves that by:
<ol>
<li>Registering a <code>_geoforge_jsonld</code> post-meta key, exposed via the REST API for every public REST-enabled post type, that GEOforge writes to when publishing or updating an article.</li>
<li>Printing the stored JSON-LD inside a proper <code><script type="application/ld+json"></code> tag in the page <code><head></code> on any singular view — posts, pages, and custom post types.</li>
<li>Registering the SEO post-meta keys used by Yoast SEO (<code>_yoast_wpseo_metadesc</code>), Rank Math (<code>rank_math_description</code>), and The SEO Framework (<code>_genesis_title</code> / <code>_genesis_description</code>) for REST API write access, so GEOforge can sync SEO titles and meta descriptions on publish. Each registration uses an <code>edit_post</code> auth check and <code>sanitize_text_field</code>-based sanitization capped at 320 characters. Registration is idempotent — if the SEO plugin already exposes the key for REST, our registration is a no-op.</li>
</ol>
No configuration required. Install, activate, and any GEOforge-published article will get its schema markup rendered correctly and its meta description handed to whichever SEO plugin is active.

GEOforge Schema

Renders GEOforge-generated JSON-LD schema in the page head and opens Yoast SEO / Rank Math / The SEO Framework SEO meta for REST writes.

Fabio Biocchetti

SchemaSense automatically scans your WordPress posts and pages to identify question and answer pairs, then generates proper FAQ schema markup (FAQPage JSON-LD). This structured data helps AI systems and Large Language Models (LLMs) better understand and surface your content in AI-generated responses, while also improving search engine visibility (SEO) with rich snippets in search results.
The plugin also optionally formats existing FAQ blocks as minimalistic accordions (collapsible/expandable), providing an improved user experience for visitors browsing your Q&A content.
<h3>Key Features</h3>
<ul>
<li>GEO, AIO & SEO Ready – Structured data optimized for AI systems, LLMs and traditional SEO</li>
<li>Automatic Detection – Intelligently identifies Q&A patterns in your content</li>
<li>Universal Compatibility – Works with Classic Editor, Gutenberg, and all page builders (Elementor, Beaver Builder, Divi, WPBakery, etc.)</li>
<li>Multiple Formats – Supports headings, paragraphs (including bold), HTML5 details/summary accordions, and Q:/A: format</li>
<li>Multilingual Support – Works with 15+ languages (Latin-based question marks)</li>
<li>Smart Exclusions – Won’t interfere with Yoast or other FAQ plugins that add their own schema</li>
<li>Automatic for Posts – Posts auto-process on save; pages require manual scanning</li>
<li>Separate Batch Processing – Individual scan buttons for posts and pages</li>
<li>Optional Collapsible UI – Enhance Q&A with expand/collapse functionality</li>
<li>Performance Optimized – Schema cached in post meta, not regenerated on every load</li>
</ul>
<h3>How It Works</h3>
The plugin uses multiple detection strategies:
1. FAQ Section Detection (standard HTML – works with all editors/builders) 
* Looks for headings containing FAQ keywords (e.g., “FAQ”, “Frequently Asked Questions”, “Common Questions”) 
* Scans headings and paragraphs within that section for Q&A pairs 
* Works with Classic Editor, Gutenberg, and all page builders
2. HTML5 Details/Summary Detection (modern page builders) 
* Detects accordion widgets using <code><details></code> and <code><summary></code> elements 
* Commonly used by Elementor, Beaver Builder, and other modern page builders
3. Gutenberg Block Detection 
* Native support for WordPress blocks 
* Parses block structure directly for optimal accuracy
<h3>What schema types does the plugin support?</h3>
Currently, the plugin supports FAQ (FAQPage) schema only. It generates JSON-LD structured data with the <code>@type: "FAQPage"</code> format, which includes <code>Question</code> and <code>Answer</code> entities. Support for additional schema types (HowTo, Recipe, Product, etc.) may be added in future versions.
<h3>Does this work with Gutenberg?</h3>
Yes! The plugin supports both Classic Editor and Gutenberg (Block Editor). It can parse both Gutenberg blocks and HTML content.
<h3>How does the plugin detect questions and answers?</h3>
The plugin uses intelligent pattern detection with strict scoping to avoid false positives:
FAQ Section Detection: 
* Looks for headings containing FAQ keywords (e.g., “FAQ”, “FAQs”, “Frequently Asked Questions”, “Common Questions”) 
* Supports 15+ languages with multilingual FAQ heading recognition 
* Once an FAQ section is detected, the plugin scans content within that section only
Question Detection (within FAQ sections only): 
* Heading-based questions: Sub-headings at deeper levels than the FAQ heading (e.g., h3/h4 under an h2 FAQ heading) are treated as questions 
 – No punctuation required 
 – Minimum 5 characters 
* Paragraph-based questions: Paragraphs ending with “?” 
 – Must be between 5-250 characters 
 – Automatically handles bold (<code></code>), italic (<code></code>), or plain text formatting 
 – Example: <code>What is this?</code>
Answer Detection: 
* Any paragraph following a detected question is treated as the answer 
* Multiple consecutive paragraphs are combined into a single answer
Section Boundaries: 
* FAQ section ends when a heading at the same level or higher than the FAQ heading is encountered 
* This prevents false detection of questions in subsequent sections 
* Example: If FAQ section starts with <code><h2></code>, any other <code><h2></code> or <code><h1></code> ends the FAQ section
Additional Format: 
* Q:/A: Format: Explicit “Q:” and “A:” patterns are supported anywhere in content (not limited to FAQ sections)
<h3>Which languages are supported?</h3>
The plugin supports 15+ languages including English, Spanish, French, German, Italian, Portuguese, Dutch, Polish, Russian, Swedish, Danish, Norwegian, Finnish, Czech, and Turkish. All supported languages use the standard Latin question mark (?) for question detection.
<h3>Will it conflict with Yoast SEO or other FAQ plugins?</h3>
No. The plugin automatically detects and skips content managed by Yoast FAQ blocks, Elementor FAQ widgets, and other popular FAQ plugins to prevent duplicate schema markup.
<h3>Can I customize the styling?</h3>
Yes. Override the <code>.ssd-*</code> CSS classes in your theme to customize the collapsible FAQ appearance.
<h3>Which languages are supported for FAQ detection?</h3>
The plugin supports 15+ languages (all use standard Latin question mark <code>?</code> for paragraph-based questions):
<ul>
<li>English</li>
<li>Spanish (Español)</li>
<li>French (Français)</li>
<li>German (Deutsch)</li>
<li>Italian (Italiano)</li>
<li>Portuguese (Português)</li>
<li>Dutch (Nederlands)</li>
<li>Polish (Polski)</li>
<li>Russian (Русский)</li>
<li>Swedish (Svenska)</li>
<li>Danish (Dansk)</li>
<li>Norwegian (Norsk)</li>
<li>Finnish (Suomi)</li>
<li>Czech (Čeština)</li>
<li>Turkish (Türkçe)</li>
</ul>
Note: Languages using non-Latin question marks (Arabic, Greek, Hebrew, CJK languages) are not currently supported for paragraph-based question detection.

SchemaSense – Smart Structured Data

Auto-detects FAQ content and generates valid JSON-LD schema for LLMs, GEO (Generative Engine Optimization), and SEO.

GEOforge Schema vs SchemaSense – Smart Structured Data