[WordPress] 外掛分享： Franixo – AI Visibility & GEO Connector

外掛標籤

開發者團隊

原文外掛簡介

The Franixo Connector links one WordPress site to one Franixo brand with a site-scoped key. It is an MCP client of Franixo: Franixo never writes to your site. Every change is made by this plugin, on your site, after an administrator approved it.

Content Drafts – browse drafts Franixo wrote for your brand, read the evidence they are based on, see every unresolved [VERIFY: …] placeholder and verification note, and import a draft as an unpublished WordPress draft. Nothing is ever published automatically. Page update drafts are treated as editorial instructions: they are imported as a separate instruction draft, or applied to an existing page through a working copy, a before/after comparison and an explicit confirmation.
Technical Fixes – see findings of Franixo’s Technical GEO Audit for your pages. For the few deterministic fixes (self-referencing canonical, removing named robots meta directives, allowing AI search crawlers in the virtual robots.txt, Organization JSON-LD on the home page) the plugin reads the live page, asks Franixo for a preview, shows the real before/after and preconditions, and applies the change only after you approve it. It then reads the page again, undoes the change if it is not visible, and keeps it reversible.
Reports – imports and fix results are reported back to Franixo with idempotency keys and automatic retries. Franixo verifies applied fixes later with its own audit.
Activity – an audit log of who did what, the report queue, and verification status.

Manual fixes (titles, meta descriptions, headings, internal links, redirects, page-specific schema, llms.txt, server or firewall issues) are shown as information only.
This plugin requires a Franixo account and relies on the external Franixo MCP service. See “External Services” below for what is sent, when, and the applicable terms and privacy policy.
External Services
This plugin connects to an external service: the Franixo MCP service at https://api.franixo.com/mcp, operated by SCOPEONAI LLC, the operator of Franixo (https://franixo.com/). The address is fixed in the plugin and cannot be changed. The plugin does not work without it: all drafts, technical audit findings and previews shown by the plugin come from this service.
What the service is used for

Site connection authentication: checking the site key and which Franixo brand and website it belongs to.
Brand and connection information: brand name and domain, the website address bound to the key, granted permissions.
AI-generated content drafts: listing drafts and reading a single draft with its evidence and review notes.
Technical GEO audit findings: listing technical fixes and reading a single fix.
Technical improvement previews: Franixo compares a proposed fix with the current state of your page.
Synchronization reporting: telling Franixo that a draft was imported or updated in WordPress, or that its post status changed.
Technical fix execution reporting: telling Franixo that a fix was applied, failed, skipped, rolled back or changed by hand.

What data is sent
With every request:

your Franixo site key, in the Authorization HTTP header;
a User-Agent header with the plugin version and the WordPress version (for example FranixoConnector/1.0.0 (WordPress/6.8));
as with any HTTP request, the IP address of your web server is visible to the service.

Depending on the operation:

Connection setup: the plugin name and version and the supported MCP protocol version. No site data is sent; Franixo answers with the brand and website bound to the key, and the plugin compares that address with your site locally.
Reading drafts and fixes: list filters (draft status or task status), the page size, pagination cursors, and the Franixo brand, draft or fix identifier being opened.
Previewing a technical fix: the Franixo fix identifier and version, and a snapshot of the current state of the affected resource read from your own site: its type, WordPress ID and URL, its last modification time, and, depending on the fix, the canonical URL printed on the page, its robots meta directives, the robots.txt content your site serves (up to 100 KB), or the list of structured data (JSON-LD) types on your home page.
Draft import reports: the Franixo draft identifier and version, whether the post was created or updated, the result, the WordPress post ID, post URL and post status, or, if the import failed, an error code and a short error message. Later post status changes (for example publishing) are reported the same way.
Fix reports: the Franixo fix identifier and version, the result (applied, failed, skipped or reverted), the affected resource type, WordPress ID and URL, the time of the change, a short change summary (including any note an administrator types when recording a manual change), a fingerprint (hash) of the previewed page state, and, on failure, an error code and a short error message.
Every report contains a unique idempotency key generated by the plugin so that retries are not recorded twice.

The plugin does not send post content, WordPress user names, email addresses, passwords, or any data about your site’s visitors.
When data is sent

When an administrator saves a site key or runs “Test connection”.
When an administrator uses the plugin screens: refreshing or loading more drafts or fixes, opening a draft or fix, previewing a fix, importing or updating a draft, applying or rolling back a fix, recording a manual change, or retrying a report.
When an imported post changes status in WordPress (for example when you publish it), a status report is queued and sent shortly afterwards by WP-Cron.
By scheduled background synchronization (WP-Cron): the connection, the first page of ready drafts and the list of fixes are refreshed at the interval chosen in Franixo → Settings (default every 30 minutes; it can be turned off).
By the background retry queue (WP-Cron, checked every 5 minutes): reports that could not be delivered are re-sent with the same idempotency key, with increasing delays, for up to 24 hours.

Nothing is sent before a site key has been entered, and nothing is sent after you disconnect.
While previewing and verifying a technical fix, the plugin also requests the affected page or robots.txt from your own website (a loopback request to your own domain). That request stays on your site and is not sent to Franixo; only the snapshot described above is.
Terms and privacy

Franixo Terms of Service: https://franixo.com/terms
Franixo Privacy Policy: https://franixo.com/privacy