Install GoBuildWP Free and Pro: Order, Licence and Checks

Install GoBuildWP from the ZIP, click by click

Both plugins are distributed as ZIP files rather than through the WordPress.org directory, so the install starts from the upload form. In wp-admin go to Plugins, then Add New Plugin, then Upload Plugin. Choose the GoBuildWP Free ZIP, select Install Now, and on the result screen select Activate Plugin. A GoBuildWP menu appears in the admin sidebar. Repeat with the Pro ZIP if you bought Pro.

Read the upload error before choosing a remedy. PHP upload limits and filesystem permissions are possible causes, as are an invalid archive and incompatible WordPress or PHP requirements. Uploading a retained release ZIP over an installed copy offers replacement, but rolling files back does not reverse database migrations; review recovery before downgrading.

Updates after that arrive the normal way. Each plugin declares an update address on the GoBuildWP website, and GoBuildWP checks it and feeds the result into WordPress's own update system, so a new release appears on Dashboard, Updates and on the Plugins list like any other plugin. Because the address is declared in the plugin header, a plugin of the same name on WordPress.org cannot be offered as an update in its place.

What Pro looks like before and after its licence

Pro features load only while the Freemius SDK permits premium code, including any eligible trial or cached state. When that gate fails, feature modules and screens are unavailable while activation and licensing controls remain accessible. Persisted approval policies can still refuse covered writes after a lapse; inspect the actual gate and saved policy before diagnosing missing abilities.

Select Enter licence key, paste the key from your purchase, and submit. Activate from wp-admin rather than from a WP-CLI command, so the licence activation runs in the screen built for it. Afterwards GoBuildWP, Licence shows the plan, the sites used and left on the licence, the expiry date (or that a lifetime licence never expires) and the key itself masked, never in full. The Approvals and Memory screens appear in the GoBuildWP menu, and the Pro abilities for any companion plugin present start registering.

Pro also checks its partner. It needs GoBuildWP Free 1.18.1 or newer to be active, and it stands down rather than half-loading when Free is missing or older. After restoring a backup or migrating a site, check the Free version first: an older Free is a quieter failure than a missing licence.

• Activate GoBuildWP Pro screen replaced by a Licence screen
• Licence shows a plan, a seat count and an expiry, with the key masked
• GoBuildWP Free 1.18.1 or newer active
• Approvals and Memory listed in the GoBuildWP menu

Checking which integrations actually loaded

A Pro module registers only when its companion plugin or theme is present, at or above the version floor GoBuildWP supports, and the licence gate has passed. When one of those fails, the module's abilities are simply absent, and from inside an AI client an absent ability looks exactly like one that never existed. The way to tell them apart is wppilot/integration-health, a Pro read-only ability that lists every integration with two separate facts: whether its category is active, and whether its loader is eligible to run.

Active but not eligible means the plugin is there and something gated it, typically a version below the floor or the licence. A recorded failure means the module threw while loading and was contained so the rest of Pro could keep working; the entry shows when, and a later clean load is kept as resolved history. Ask your agent to run it once after installation and again whenever an integration you expected is missing, before reinstalling anything.

Then run the module's own setup check, such as wppilot/beaver-builder-check-setup or wppilot/acf-check-setup, which reports what that integration found on this site: versions, editions and counts. Health tells you whether the module loaded; check-setup tells you whether it is ready for the work you are about to ask for.

Deactivating, deleting and reinstalling

Deactivating either plugin stops it and keeps everything it stored, so reactivating later picks up where it left off. Deleting the free plugin from the Plugins screen is different: WordPress runs GoBuildWP's uninstall routine, which drops its own tables and options, including the change ledger, the list of connections, access tokens, Chat sessions and every OAuth client and token. Connected clients lose access, and the history of what agents changed is gone.

Two kinds of content are deliberately kept. PHP written through the sandbox stays in wp-content/wppilot-sandbox, because it is the site owner's own code and deleting source cannot be undone. Designs and skills are kept as well, unless the site has opted in to removing them through the wppilot_delete_content_on_uninstall setting. Nothing outside GoBuildWP's own prefixes is touched.

So before a delete, download the change history from Changes as CSV or JSON if you might need it, and note which clients will need reconnecting. To repair a broken install without losing anything, upload the release ZIP over the installed copy instead of deleting it first.

• Deactivate: everything kept
• Delete: ledger, connections, tokens, Chat sessions and OAuth data removed
• Kept after delete: sandbox PHP files, and designs and skills unless opted in
• Repair: upload the ZIP over the existing copy