Wigoh Connect FAQ

Should I connect my live site or a staging copy? Either works. Wigoh never edits the connected site directly. Connecting a staging copy is recommended; the plugin warns before connecting a site that does not look like staging.

What does a release overwrite? Content tables, options (merged, keeping site-specific values), the theme and plugin folders the release contains, and uploads added in the preview. Users, user meta, comments and plugin runtime tables are never replaced.

How long can I roll back? For 7 days after a release goes live, from Wigoh → Releases in WordPress or from the release page in Wigoh.

What happens if the health check fails after a release? The plugin rolls back automatically and reports the failure. The site is back to its pre-release state within seconds.

Does the plugin store a Wigoh password or API key? No. The site holds only its own private key, encrypted with your site's salts. Wigoh holds only the public key.

What happens when I disconnect? Wigoh revokes the site's key; the plugin deletes the local key and generates a new one. Reconnecting creates a new identity.

Why does it say my site looks like a live site? The plugin checks the environment type, hostname, search-engine visibility and HTTP authentication. If none indicate staging, it asks you to confirm.

Does it work on multisite? No.

Do I pay for a plan for a connected site? A connected site publishes back to your own WordPress, so there is no hosting plan to buy for it. AI edits in the editor are paid the way they are for any site. See Credits in the editor.