Title: Vybe Eye Connector
Author: vybefind
Published: <strong>13 Luglio 2026</strong>
Last modified: 4 Agosto 2026

---

Ricerca i plugin

![](https://ps.w.org/vybe-eye-connector/assets/banner-772x250.png?rev=3606736)

![](https://ps.w.org/vybe-eye-connector/assets/icon-256x256.png?rev=3606736)

# Vybe Eye Connector

 Di [vybefind](https://profiles.wordpress.org/vybefind/)

[Scarica](https://downloads.wordpress.org/plugin/vybe-eye-connector.1.2.0.zip)

 * [Dettagli](https://it.wordpress.org/plugins/vybe-eye-connector/#description)
 * [Recensioni](https://it.wordpress.org/plugins/vybe-eye-connector/#reviews)
 * [Sviluppo](https://it.wordpress.org/plugins/vybe-eye-connector/#developers)

 [Supporto](https://wordpress.org/support/plugin/vybe-eye-connector/)

## Descrizione

Vybe Eye Connector is the WordPress side of the VybeFind Execution Layer. It
 requires
an active VybeFind account (https://vybefind.com) — the plugin is the site-side 
agent for that service and does nothing on its own until paired. Once paired with
your VybeFind workspace, it pulls the changes your team has approved in the Execution
console and applies them in place:

 * Title tags and meta descriptions — via Yoast, Rank Math, or All in One SEO
    when
   present, or a native fallback when no SEO plugin is installed.
 * JSON-LD structured data — injected into the page head, idempotently.
 * Image alt text.
 * Internal links — inserted into the target post content, de-duplicated.
 * 301 redirects.
 * New pages or posts, created from content you approved in VybeFind. **New
    content
   is created as a draft by default
    so you can review it before it goes
    live; 
   publishing immediately is opt-in per site from your VybeFind workspace. If a 
   page already exists at the target slug the plugin uses that page instead of creating
   a second one, so a retry can never produce duplicate pages.

Every applied change is recorded locally with a hash of the value it wrote, so
 
the plugin can detect **drift** (something later changed the value out from under
it) and offer **one-click rollback** to the previous value.

### How pairing works

 1. In VybeFind, open **Execution** and click **Generate pairing code** for your
     site.
 2. In WordPress, go to **Settings  Vybe Eye Connector**, paste the one-time code,
    
    and click **Pair site**. That is the only field to fill in — the plugin connects
    to VybeFind at https://vybefind.com by default. (Agency or self-hosted workspaces
    can point at a different host under **Advanced**.) The plugin generates a local
    keypair, exchanges the code for a per-site bearer token, and stores it privately(
    never shown again).
 3. The plugin polls VybeFind every 15 minutes (WP-Cron). Each poll pulls pending
     
    changes as an HMAC-signed envelope, verifies the signature, applies each change,
    and reports the outcome back.

### External services

This plugin connects to the VybeFind platform (https://vybefind.com), the SaaS
 
service it is the WordPress client for. An active VybeFind account is required; 
the plugin performs no external communication until you pair it with a workspace.

When and why it connects:

 * **At pairing (once, when you click “Pair site”).** The plugin sends your
    one-
   time pairing code, a locally generated public key, and your WordPress version
   to `https://<your-platform-host>/api/wp/pair` in exchange for a per-site bearer
   token. The platform host is the URL you paste at pairing (VybeFind-hosted by 
   default); all later requests are pinned to that host.
 * **Every 15 minutes (WP-Cron poll).** The plugin requests pending approved
    changes
   from `/api/wp/changes` using the bearer token. No site content is uploaded on
   this request — it only pulls the change instructions your team approved in VybeFind.
   Since 1.1.0 those instructions may include the full body text of a new page or
   post to create (see below).
 * **After applying each change.** The plugin reports the outcome
    (applied / drifted/
   rolled_back / failed) and a hash of the value it wrote to `/api/wp/changes/<id
   >/status`. When it creates a page it also reports the resulting post ID, its 
   permalink, its publication status (draft/published/…) and whether a page already
   existed at that slug, so the platform can update that same page later instead
   of creating a duplicate and can tell you honestly whether the page is actually
   public. It does not transmit your existing page content, visitor data, or personal
   data.

Data sent: pairing code, generated public key, WordPress version, connector
 version,
change IDs, per-change outcome hashes, and — for created or adopted pages only —
the post ID, its public permalink, its publication status, and whether the page 
already existed. Data received: the change instructions you approved in your VybeFind
workspace (titles, meta descriptions, JSON-LD, alt text, internal links, redirects,
and since 1.1.0 the title, slug and body content of new pages to create).

Your use of the VybeFind service is governed by its terms and privacy policy:

 * Terms of Service: https://vybefind.com/legal/terms
 * Privacy Policy: https://vybefind.com/legal/privacy

### Security

 * The per-site bearer token and the signing keypair are stored as non-autoloaded
   
   options and never printed back into the admin UI.
 * Every changes envelope from the platform is HMAC-verified before anything is
   
   applied — unsigned or tampered payloads are refused (fail-closed).
 * All admin actions are capability- (manage_options) and nonce-guarded.
 * Outbound requests only ever go to the platform URL saved at pairing.

## Screenshot

[⌊The Vybe Eye Connector settings screen — connection status plus the live change
log, with drift detection and one-click rollback on every applied change.⌉⌊The Vybe
Eye Connector settings screen — connection status plus the live change log, with
drift detection and one-click rollback on every applied change.⌉[

The Vybe Eye Connector settings screen — connection status plus the live change 
log, with drift detection and one-click rollback on every applied change.

## Recensioni

Non ci sono recensioni per questo plugin.

## Contributi e sviluppo

“Vybe Eye Connector” è un software open source. Le persone che hanno contribuito
allo sviluppo di questo plugin sono indicate di seguito.

Collaboratori

 *   [ vybefind ](https://profiles.wordpress.org/vybefind/)

[Traduci “Vybe Eye Connector” nella tua lingua.](https://translate.wordpress.org/projects/wp-plugins/vybe-eye-connector)

### Ti interessa lo sviluppo?

[Esplora il codice](https://plugins.trac.wordpress.org/browser/vybe-eye-connector/)
segui il [repository SVN](https://plugins.svn.wordpress.org/vybe-eye-connector/),
segui il [log delle modifiche](https://plugins.trac.wordpress.org/log/vybe-eye-connector/)
tramite [RSS](https://plugins.trac.wordpress.org/log/vybe-eye-connector/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.2.0

 * New: you can now undo an applied change from your VybeFind workspace, not only
   
   from this settings screen. The connector has always known how to reverse every
   change it makes — restoring the previous title or description, removing a schema
   block, deleting a redirect — but VybeFind had no way to ask it to. Its rollback
   button did nothing on WordPress. It works now.
 * New: a page the connector created can be un-published. It moves back to Draft,
   
   never Trash: if someone has edited the page since, destroying that work to undo
   our change would be the larger action. This was the one change the connector 
   could make and not take back.
 * Fixed: a rollback that FAILED used to be recorded as a success. Every reversal
   
   discarded its result and then wrote “rolled back” regardless, so a page the plugin
   could not find, or a redirect store that would not save, still showed as undone
   here and in VybeFind while the change stayed live on the site. Only a reversal
   that actually happened is recorded as one.
 * No new permissions, no new network endpoints: the undo arrives on the same
    authenticated
   poll as every other change.

#### 1.1.1

 * Fixed: when the plugin adopts a page that already exists at the target slug
    (
   instead of creating a duplicate), it now reports that page’s REAL status back
   to VybeFind. Previously VybeFind could only see that the change succeeded, so
   an existing unpublished draft was shown in your workspace as “Live” — with a 
   link to a page no visitor could open. The connector now also reports the real
   status of pages it creates itself, so an editorial-workflow plugin that holds
   new posts for moderation is reflected accurately rather than assumed published.
 * No change to what the plugin writes to your site: it still never alters the
    
   status of a page it did not create.

#### 1.1.0

 * New: the connector can create a page or post from content approved in your
    VybeFind
   workspace. Previously it could only edit pages that already existed, so approved
   articles had to be published by hand.
 * Safe by default: created content is a **draft** unless you explicitly enable
   
   automatic publishing for that site. An unrecognised status is treated as draft,
   so nothing goes live on your site unless you asked for it.
 * No duplicates: if a page already exists at the target slug, the plugin adopts
   
   that page and reports its ID rather than creating a competing second page.
 * Post body content is passed through wp_kses_post() before insertion, so only
   
   markup WordPress already permits in post content can be written.
 * The connector now reports its own version at pairing, so the platform can tell
   
   which features a site supports and withholds anything this build cannot apply
   instead of sending changes that would fail.

#### 1.0.1

 * Security/hardening: JSON-LD schema is now escaped late on output via
    wp_json_encode()
   with JSON_HEX_TAG/HEX_AMP/HEX_APOS/HEX_QUOT so it can never break out of the 
   tag, and only well-formed JSON objects are stored (malformed input is rejected
   on write). Addresses the plugin-review escaping note.

#### 1.0.0

 * Initial release: pairing handshake, 15-minute pull-apply loop, Yoast/RankMath/
   
   AIOSEO adapters + native fallback, JSON-LD injection, alt text, internal links,
   redirects, local change log, drift detection, and one-click rollback.

## Meta

 *  Versione **1.2.0**
 *  Ultimo aggiornamento **3 giorni fa**
 *  Installazioni attive **Meno di 10**
 *  Versione WordPress ** 6.0 o superiore **
 *  Testato fino alla versione **7.0.3**
 *  Versione PHP ** 7.4 o superiore **
 *  Lingua
 * [English (US)](https://wordpress.org/plugins/vybe-eye-connector/)
 * Tag
 * [automation](https://it.wordpress.org/plugins/tags/automation/)[redirects](https://it.wordpress.org/plugins/tags/redirects/)
   [schema](https://it.wordpress.org/plugins/tags/schema/)[seo](https://it.wordpress.org/plugins/tags/seo/)
 *  [Visualizzazione avanzata](https://it.wordpress.org/plugins/vybe-eye-connector/advanced/)

## Valutazioni

Non sono state ancora inviate recensioni.

[Your review](https://wordpress.org/support/plugin/vybe-eye-connector/reviews/#new-post)

[Vedi tutte le recensioni](https://wordpress.org/support/plugin/vybe-eye-connector/reviews/)

## Collaboratori

 *   [ vybefind ](https://profiles.wordpress.org/vybefind/)

## Supporto

Hai qualcosa da dire? Ti serve aiuto?

 [Chiedi nel forum di supporto](https://wordpress.org/support/plugin/vybe-eye-connector/)