GEOforge has published directly to WordPress since day one. Now every structured signal it generates actually lands where it needs to.
We've just released GEOforge Schema, the official companion WordPress plugin — and it closes a critical technical gap for any WordPress site in a GEOforge publishing workflow: ensuring that the schema markup and meta descriptions ContentForge generates are delivered into your CMS correctly, every time.
Install GEOforge Schema on WordPress.org →
When ContentForge generates an article, it doesn't just produce words. It produces a complete structured content object: body copy, a tuned meta description, and JSON-LD schema markup — the machine-readable layer that tells AI systems, Google, and LLMs what a piece of content is about and why it should be cited.
The problem? WordPress gets in the way.
WordPress's KSES sanitization strips inline script tags from post bodies — meaning any schema markup injected into the content itself gets silently removed. And underscore-prefixed meta fields (like _geoforge_jsonld) are hidden from the REST API by default, so external publishing tools can't write to them without elevated permissions.
The result: ContentForge published beautifully formatted posts, but all the GEO-critical metadata — the schema, the optimized meta descriptions, the structured signals that make content visible to AI systems — never made it into the page.
GEOforge Schema fixes that.
GEOforge Schema is a lightweight companion plugin that acts as the bridge between GEOforge's ContentForge module and your WordPress site. Once installed and activated, it does three things:
1. Registers the _geoforge_jsonld post-meta key for REST API write access
ContentForge can now write schema markup to your WordPress posts and pages directly over the API — no workarounds, no manual copy-paste.
2. Emits schema in the page head — exactly where it needs to be
GEOforge Schema renders the stored JSON-LD inside a proper script tag in the page head on single posts and pages. This is the format Google, Bing, and LLM crawlers read. It doesn't touch the post body, and it plays nicely with whatever your theme is already doing.
3. Syncs meta descriptions to your active SEO plugin
GEOforge Schema registers the post-meta keys used by Yoast SEO and Rank Math for REST write access. When ContentForge publishes an article, the optimized meta description is automatically handed to whichever SEO plugin you're running — capped at 320 characters, sanitized, and scoped to users with edit access.
No admin UI. No configuration screen. Install it, activate it, and your WordPress site becomes a first-class ContentForge publish target.
Most content teams think about publishing as the finish line. In GEO, publishing is where the technical work begins.
An article that's live on WordPress but missing its JSON-LD schema is invisible to AI systems in the ways that matter most. LLMs and AI search engines don't just read prose — they read structured signals. Schema markup is how you declare the entity type, authorship, topic focus, and structured facts that make a piece of content citable rather than just indexable.
With GEOforge Schema installed, every ContentForge article arrives in WordPress with:
This is what "GEO-friendly publishing" actually means in practice: not just well-written content, but content that arrives in your CMS pre-equipped with the structural signals that make it legible to AI systems.
A few practical notes worth knowing:
Multiple JSON-LD blocks per page are valid Schema.org and supported by Google — search engines merge the data. If your SEO plugin is already emitting its own schema, GEOforge Schema adds to it, it doesn't replace it.
The meta key registrations are idempotent — if Yoast or Rank Math has already exposed the key via the REST API, GEOforge Schema's registration is a no-op. No conflicts.
GEOforge Schema is open source software, available on WordPress.org, and free to install.
If you're already a GEOforge customer, this is a required companion for any WordPress site in your publishing workflow. If you're evaluating GEOforge, this is a concrete example of what native CMS integration looks like at the infrastructure level.
GEOforge Schema is one piece of a larger architecture. ContentForge handles content generation, optimization, and publishing. BaseForge grounds that content in proprietary knowledge. SignalForge measures whether it's working. CiteForge finds the citation opportunities worth pursuing.
WordPress is where a significant portion of the web lives. GEOforge Schema ensures that when GEOforge publishes to it, nothing gets lost in translation.
I lead the PPC and Analytics teams. My professional goals are to make clients and colleagues happy. I also love numbers, charts, and data-driven decisions.
