New\ncontent is created as a draft by default<\/strong> so you can review it before it goes\nlive; publishing immediately is opt-in per site from your VybeFind workspace.\nIf a page already exists at the target slug the plugin uses that page instead\nof creating a second one, so a retry can never produce duplicate pages.<\/li>\n<\/ul>\n\nEvery applied change is recorded locally with a hash of the value it wrote, so\nthe plugin can detect drift<\/strong> (something later changed the value out from\nunder it) and offer one-click rollback<\/strong> to the previous value.<\/p>\n\nHow pairing works<\/h3>\n\n\n- In VybeFind, open Execution<\/strong> and click Generate pairing code<\/strong> for your\nsite.<\/li>\n
- In WordPress, go to Settings \u2192 Vybe Eye Connector<\/strong>, paste the one-time code,\nand click Pair site<\/strong>. That is the only field to fill in \u2014 the plugin\nconnects to VybeFind at https:\/\/vybefind.com by default. (Agency or\nself-hosted workspaces can point at a different host under Advanced<\/strong>.) The\nplugin generates a local keypair, exchanges the code for a per-site bearer\ntoken, and stores it privately (never shown again).<\/li>\n
- The plugin polls VybeFind every 15 minutes (WP-Cron). Each poll pulls pending\nchanges as an HMAC-signed envelope, verifies the signature, applies each\nchange, and reports the outcome back.<\/li>\n<\/ol>\n\n
External services<\/h3>\n\n
This plugin connects to the VybeFind platform (https:\/\/vybefind.com), the SaaS\nservice it is the WordPress client for. An active VybeFind account is required;\nthe plugin performs no external communication until you pair it with a workspace.<\/p>\n\n
When and why it connects:<\/p>\n\n
\n- At pairing (once, when you click \"Pair site\").<\/strong> The plugin sends your\none-time pairing code, a locally generated public key, and your WordPress\nversion to
https:\/\/<your-platform-host>\/api\/wp\/pair<\/code> in exchange for a\nper-site bearer token. The platform host is the URL you paste at pairing\n(VybeFind-hosted by default); all later requests are pinned to that host.<\/li>\n- Every 15 minutes (WP-Cron poll).<\/strong> The plugin requests pending approved\nchanges from
\/api\/wp\/changes<\/code> using the bearer token. No site content is\nuploaded on this request \u2014 it only pulls the change instructions your team\napproved in VybeFind. Since 1.1.0 those instructions may include the full body\ntext of a new page or post to create (see below).<\/li>\n- After applying each change.<\/strong> The plugin reports the outcome\n(applied \/ drifted \/ rolled_back \/ failed) and a hash of the value it wrote\nto
\/api\/wp\/changes\/<id>\/status<\/code>. When it creates a page it also reports the\nresulting post ID and its permalink, so the platform can update that same page\nlater instead of creating a duplicate. It does not transmit your existing page\ncontent, visitor data, or personal data.<\/li>\n<\/ul>\n\nData sent: pairing code, generated public key, WordPress version, connector\nversion, change IDs, per-change outcome hashes, and \u2014 for created pages only \u2014\nthe new post ID and its public permalink. Data received: the change instructions\nyou approved in your VybeFind workspace (titles, meta descriptions, JSON-LD, alt\ntext, internal links, redirects, and since 1.1.0 the title, slug and body content\nof new pages to create).<\/p>\n\n
Your use of the VybeFind service is governed by its terms and privacy policy:<\/p>\n\n
\n- Terms of Service: https:\/\/vybefind.com\/legal\/terms<\/li>\n
- Privacy Policy: https:\/\/vybefind.com\/legal\/privacy<\/li>\n<\/ul>\n\n
Security<\/h3>\n\n\n- The per-site bearer token and the signing keypair are stored as non-autoloaded\noptions and never printed back into the admin UI.<\/li>\n
- Every changes envelope from the platform is HMAC-verified before anything is\napplied \u2014 unsigned or tampered payloads are refused (fail-closed).<\/li>\n
- All admin actions are capability- (manage_options) and nonce-guarded.<\/li>\n
- Outbound requests only ever go to the platform URL saved at pairing.<\/li>\n<\/ul>\n\n\n
1.1.0<\/h4>\n\n\n- New: the connector can create a page or post from content approved in your\nVybeFind workspace. Previously it could only edit pages that already existed,\nso approved articles had to be published by hand.<\/li>\n
- Safe by default: created content is a draft<\/strong> unless you explicitly enable\nautomatic publishing for that site. An unrecognised status is treated as draft,\nso nothing goes live on your site unless you asked for it.<\/li>\n
- No duplicates: if a page already exists at the target slug, the plugin adopts\nthat page and reports its ID rather than creating a competing second page.<\/li>\n
- Post body content is passed through wp_kses_post() before insertion, so only\nmarkup WordPress already permits in post content can be written.<\/li>\n
- The connector now reports its own version at pairing, so the platform can tell\nwhich features a site supports and withholds anything this build cannot apply\ninstead of sending changes that would fail.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Security\/hardening: JSON-LD schema is now escaped late on output via\nwp_json_encode() with JSON_HEX_TAG\/HEX_AMP\/HEX_APOS\/HEX_QUOT so it can never\nbreak out of the tag, and only well-formed JSON objects are stored\n(malformed input is rejected on write). Addresses the plugin-review escaping note.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release: pairing handshake, 15-minute pull-apply loop, Yoast\/RankMath\/\nAIOSEO adapters + native fallback, JSON-LD injection, alt text, internal links,\nredirects, local change log, drift detection, and one-click rollback.<\/li>\n<\/ul>","raw_excerpt":"Securely applies VybeFind-approved SEO changes to this WordPress site \u2014 with a full change log, drift detection, and one-click rollback.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/338628","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=338628"}],"author":[{"embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/vybefind"}],"wp:attachment":[{"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=338628"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=338628"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=338628"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=338628"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=338628"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=338628"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}