{"id":313494,"date":"2026-05-20T07:24:19","date_gmt":"2026-05-20T07:24:19","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/geoforge-schema\/"},"modified":"2026-05-20T07:24:06","modified_gmt":"2026-05-20T07:24:06","slug":"geoforge-schema","status":"publish","type":"plugin","link":"https:\/\/ru.wordpress.org\/plugins\/geoforge-schema\/","author":23498805,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_crdt_document":"","version":"1.2.0","stable_tag":"1.2.0","tested":"6.9.4","requires":"5.6","requires_php":"7.4","requires_plugins":null,"header_name":"GEOforge Schema","header_author":"Hop AI","header_description":"Emits JSON-LD schema markup generated by GEOforge into the <head> of single posts and pages, and opens up the SEO post-meta keys used by Yoast SEO and Rank Math so GEOforge can write meta descriptions on publish. Required for schema and meta-description delivery on GEOforge-published content \u2014 WordPress strips inline <script> tags from post bodies and underscore-prefixed meta is hidden from REST by default. Also ships a small scoped stylesheet that constrains GEOforge-published content to a readable column width on themes that don't apply a content container.","assets_banners_color":"","last_updated":"2026-05-20 07:24:06","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/getgeoforge.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":28,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.2.0":{"tag":"1.2.0","author":"delchostanimirov","date":"2026-05-20 07:24:06"}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3538484,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3538484,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[2591,2516,1117,186],"plugin_category":[49,55],"plugin_contributors":[263624],"plugin_business_model":[],"class_list":["post-313494","plugin","type-plugin","status-publish","hentry","plugin_tags-geo","plugin_tags-json-ld","plugin_tags-schema","plugin_tags-seo","plugin_category-maps-and-location","plugin_category-seo-and-marketing","plugin_contributors-delchostanimirov","plugin_committers-delchostanimirov"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/geoforge-schema\/assets\/icon-128x128.png?rev=3538484","icon_2x":"https:\/\/ps.w.org\/geoforge-schema\/assets\/icon-256x256.png?rev=3538484","generated":false},"screenshots":[],"raw_content":"\n

GEOforge generates JSON-LD schema markup and meta descriptions for the articles it publishes. WordPress strips inline <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>\n\n

This plugin solves that by:<\/p>\n\n

    \n
  1. Registering a _geoforge_jsonld<\/code> post-meta key, exposed via the REST API, that GEOforge writes to when publishing or updating an article.<\/li>\n
  2. Printing the stored JSON-LD inside a proper <script type=\"application\/ld+json\"><\/code> tag in the page <head><\/code> for single posts and pages.<\/li>\n
  3. Registering the SEO post-meta keys used by Yoast SEO (_yoast_wpseo_metadesc<\/code>) and Rank Math (rank_math_description<\/code>) for REST API write access, so GEOforge can sync meta descriptions on publish. Each registration uses an edit_post<\/code> auth check and sanitize_text_field<\/code>-based sanitization capped at 320 characters. Registration is idempotent \u2014 if the SEO plugin already exposes the key for REST, our registration is a no-op.<\/li>\n<\/ol>\n\n

    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>\n\n\n

      \n
    1. Upload the plugin zip via Plugins \u2192 Add New \u2192 Upload Plugin.<\/li>\n
    2. Activate.<\/li>\n
    3. Publish from GEOforge as normal \u2014 schema will appear in <head><\/code> on each article.<\/li>\n<\/ol>\n\n\n
      \n

      Do I need GEOforge to use this plugin?<\/h3><\/dt>\n

      The plugin is designed to render JSON-LD that GEOforge writes during publish. It will work with any tool that writes a JSON-encoded string to the _geoforge_jsonld<\/code> post-meta key via the REST API, but on its own it does nothing \u2014 there is no admin UI for entering schema by hand.<\/p><\/dd>\n

      Will this conflict with Yoast SEO, Rank Math, or All in One SEO?<\/h3><\/dt>\n

      No. Multiple <script type=\"application\/ld+json\"><\/code> blocks per page are valid Schema.org and supported by Google \u2014 search engines merge the data. If both your SEO plugin and GEOforge emit schema, both will appear in the page head.<\/p>\n\n

      For meta descriptions, the plugin registers Yoast and Rank Math meta keys for REST. The registration calls are idempotent \u2014 if the SEO plugin has already registered the key itself, our call is a no-op. The auth callback restricts writes to users with edit_post<\/code> capability on the target post.<\/p><\/dd>\n

      Why is the meta key prefixed with an underscore?<\/h3><\/dt>\n

      WordPress treats underscore-prefixed meta as \"protected\" \u2014 hidden from the default Custom Fields UI in the post editor. This prevents accidental editing of the JSON blob while still allowing the REST API (and this plugin) to read and write it.<\/p><\/dd>\n

      What happens if I deactivate the plugin?<\/h3><\/dt>\n

      The stored schema data is preserved in post meta. Re-activating restores schema rendering on the front end. Uninstalling the plugin does not remove the meta.<\/p><\/dd>\n\n<\/dl>\n\n\n

      1.2.0<\/h4>\n\n
        \n
      • JSON-LD output: decode the stored value and re-encode via wp_json_encode<\/code> with JSON_HEX_TAG | JSON_HEX_AMP | JSON_HEX_APOS | JSON_HEX_QUOT<\/code> (plus JSON_UNESCAPED_UNICODE | JSON_UNESCAPED_SLASHES<\/code>) before emitting. Every HTML-sensitive character is emitted as a \\uXXXX<\/code> escape, replacing the prior str_replace('<\/', '<\\\/', $json)<\/code> approach.<\/li>\n
      • Register _yoast_wpseo_metadesc<\/code> (Yoast SEO) and rank_math_description<\/code> (Rank Math) post-meta keys for REST write access. Both use show_in_rest<\/code>, an edit_post<\/code> auth callback, and a sanitize_text_field<\/code>-based sanitizer capped at 320 characters. Idempotent \u2014 no-op when the SEO plugin already exposes the key.<\/li>\n<\/ul>\n\n

        1.1.1<\/h4>\n\n
          \n
        • Readme: rewrite the short description so the wp.org renderer doesn't strip the literal <head><\/code> tag and leave the sentence incomplete. Functionality unchanged.<\/li>\n<\/ul>\n\n

          1.1.0<\/h4>\n\n
            \n
          • Enqueue a small scoped stylesheet on single posts and pages that constrains .geoforge-content<\/code> to a 768px max-width and makes inline images responsive. Fixes edge-to-edge text on themes that don't apply a content container around the_content()<\/code>. No typography or color rules \u2014 host theme keeps full control of look-and-feel.<\/li>\n<\/ul>\n\n

            1.0.0<\/h4>\n\n
              \n
            • Initial release.<\/li>\n<\/ul>","raw_excerpt":"Emits GEOforge-generated JSON-LD schema markup into the page head of single posts and pages, and opens Yoast SEO \/ Rank Math description meta for REST …","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/313494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=313494"}],"author":[{"embeddable":true,"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/delchostanimirov"}],"wp:attachment":[{"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=313494"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=313494"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=313494"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=313494"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=313494"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ru.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=313494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}