GEOforge

<p>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.</p>
<p>This plugin solves that by:</p>
<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>
<p>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.</p>


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.

GEOforge Schema vs Schema