WordPress REST clients need registered, REST-visible post meta to write SEO fields. A successful post request alone does not prove that your SEO plugin uses those values in its rendered output.
Odiseo SEO Bridge registers those keys — only the ones for the SEO plugin you already have active — so they can be written through the standard WordPress REST API.
What it does, and what it does NOT do:
- Registers SEO post meta for Yoast, Rank Math or SEOPress. Available fields depend on the active plugin.
- Retains legacy All in One SEO post-meta fields for compatibility. Modern AIOSEO stores data in its own tables; these legacy fields do not constitute verified support for its rendered SEO. Use its documented API and verify the result.
- Does NOT change your SEO configuration or your existing content.
- Adds an Odiseo information and connection-guide page in the WordPress admin. When explicitly enabled, it also serves a public IndexNow ownership key as plain text.
- Only users who can already edit a post can write its SEO fields.
- Prepares a native editorial author when an authorized publishing client requests a byline. The identity has no role, email or login access; personal accounts are never renamed. The first setup requires create_users and edit_others_posts; reuse requires edit_others_posts.
- SEO metadata support requires a compatible SEO plugin; editorial signatures work independently.
It is open source (GPL) and makes no external calls: it exposes authenticated metadata and editorial-author operations. It is a useful building block for any headless or automated publishing setup.
Installing the plugin does not connect your website to Odiseo or start publishing. Connect your domain separately in the Odiseo dashboard. Content generation, images, approvals, reporting and Odiseo MCP are services of the platform, not features executed by this plugin. No Odiseo account is required to use the bridge with another authenticated REST client.