GoBuildWP Free and Pro install order, step by step

Order of operations

The recommended GoBuildWP Free and Pro install order has four passes: install Free, inspect diagnostics and verify a client read, install Pro, then enter the licence. Pro needs a supported active Free version; either activation order can work once both dependencies and the Freemius premium-code gate are satisfied. Its Elementor abilities use the engine supplied by Free.

The builds this page was checked against are GoBuildWP Free 1.18.6 and GoBuildWP Pro 1.12.4.

What the site needs

Both plugins declare the same floor in their headers: WordPress 6.9 or newer and PHP 8.0 or newer. WordPress checks those headers after it unpacks an uploaded ZIP into its temporary upgrade folder and before it moves the plugin into place, so on an older stack the install is refused and the plugin never reaches the plugins folder.

Use an administrator account. Installing needs the plugin-install capabilities, and every GoBuildWP screen is gated on manage_options (manage_network_options on a multisite network), so an editor never sees the GoBuildWP menu at all.

Pass one: upload and activate Free

1. Download the release ZIP from gobuildwp.com/download/latest, or take the same asset from the latest GitHub release. Use that built package rather than an archive of the source code: the release bundles the MCP Adapter, and a copy without it activates normally but never registers its MCP route.

2. In wp-admin, go to Plugins > Add Plugin and press "Upload Plugin" at the top of the screen.

3. Choose the ZIP and press "Install Now". WordPress reports "Plugin installed successfully."

4. Press "Activate Plugin". A GoBuildWP item with a REST API icon appears near the top of the admin sidebar; its first page is Dashboard, followed by Connect a client and Diagnostics.

After activation, explicitly select Read Only before the first client session. On its first activation GoBuildWP switches AI Abilities on for the current domain and leaves the safety profile on Production Safe, which blocks raw code execution, server filesystem access, WP-CLI and temporary administrator access. A site that has switched AI Abilities off before keeps that decision when the plugin is reactivated.

When WordPress refuses the ZIP

Each of these starts with "The package could not be installed." and then gives the reason:

"The PHP version on your server is …, however the uploaded plugin requires 8.0." Ask your host to move the site to a newer PHP, then upload again.

"Your WordPress version is …, however the uploaded plugin requires 6.9." Update WordPress core first.

"No valid plugins were found." The archive is not an installable plugin. It is usually a source download or a ZIP that was unpacked and re-zipped with an extra folder level. Fetch the release ZIP again and upload it untouched.

Uploading over a copy that is already installed is not an error. WordPress shows a comparison of the two versions with a "Replace current with uploaded" button, which is also a valid way to update either plugin by hand.

Pass two: prove Free connects

Open GoBuildWP > Connect a client. If AI Abilities are off, the page shows only the Enable AI Abilities step: tick "Turn on AI Abilities for this site", choose the Safety profile you want, and press "Save Settings". The page confirms with "Settings saved."

Next, open GoBuildWP > Diagnostics. Pick your sign-in method under "How do you connect?" (or "Not sure (check both)") and press "Run diagnostics". A healthy site answers "All checks passed". Treat findings as server-side evidence and investigate the indicated causes. Diagnostics is not a client connection test: use the generated connection details in the actual client, record its build and negotiated transport, discover an expected read ability and run one authorised read before adding Pro.

Pass three: upload and activate Pro

1. Download the Pro ZIP from the Freemius customer portal at users.freemius.com, signing in there with the email you paid with. From your GoBuildWP account, app.gobuildwp.com > Licences > "Billing, invoices and licence keys" opens the same portal in a new tab.

2. Upload it the same way: Plugins > Add Plugin > Upload Plugin, then "Install Now".

3. Press "Activate Plugin". After a single activation WordPress takes you once to GoBuildWP > Activate Pro, a screen headed "Activate GoBuildWP Pro". If you switched on several plugins together with "Activate Selected", that redirect stands down on purpose; open Activate Pro from the GoBuildWP menu yourself.

4. Until a key is entered, every admin page carries a red notice: "GoBuildWP Pro is installed but not licensed, so none of it is running." That is the expected state at this point rather than a fault. The notice means Pro registers no abilities or screens yet; a few safety settings stored earlier, such as requiring approval for writes, still hold writes back on a site where they were switched on before. Pass four, entering the key, has its own article on activating the licence.

Pro notices that point to the order

"GoBuildWP Pro needs the free GoBuildWP plugin." Pro is active but Free is missing or inactive, so Pro has loaded nothing, not even its activation screen. The notice carries two buttons, "Download GoBuildWP (free)" and "View releases on GitHub". Install and activate Free and the notice clears. Having activated Pro first does no harm; Pro still sends you to Activate Pro once Free is present.

"GoBuildWP Pro needs GoBuildWP … or newer." followed by "This site has …. Update from the WordPress updates screen, or install the current build over it." Free is installed but older than this Pro build accepts. Update Free, or upload the current Free ZIP and choose "Replace current with uploaded".

"GoBuildWP Pro was built without its licensing identifiers, so it cannot verify a licence and is not loading." The Pro ZIP is incomplete. It is a packaging fault, not a licence problem; download Pro again and upload it over the old copy.

Updates after install

The builds this article installs come from gobuildwp.com and GitHub, not WordPress.org. Both check the GoBuildWP website for new versions, and offers appear on the normal WordPress updates screen. Update Free before Pro, so Pro never meets an older Free than the one it was built against. If an install goes wrong, the two version numbers from the Plugins screen and the Diagnostics result are the first things support will ask for.

Staging first, then production

Running all four passes on a staging copy before production lets you verify the real client on controlled content. Staging can still send email, contact providers or expose data, so use synthetic fixtures and review its external connections. Two behaviours affect how the result travels.

AI Abilities are tied to the hostname they were switched on for. When a staging database is pushed to production, or production is cloned to staging, the copy arrives on a different hostname and its abilities are switched off until someone re-enables them under GoBuildWP > Connect a client. The wp-admin notice says that the site domain changed. This is deliberate, so a forgotten copy of a site does not quietly answer an AI client.

Staging seat treatment depends on the domain Freemius recognizes and this product's licence configuration. Inspect the actual activation and seat status before cloning or activating another site. Do not assume every staging activation consumes a paid seat or is exempt. Deactivate obsolete activations and verify the resulting allowance.

Installing on a multisite network

Free can be network-activated from Network Admin > Plugins. Activation then runs for every site in the network, and runs again for each site added later, so a new subsite is set up the same way as the existing ones. A subsite that has switched AI Abilities off keeps that decision; network activation does not turn it back on.

On a network, the GoBuildWP settings need the network-level capability rather than ordinary site administration, so a subsite administrator without network rights does not see them. The Pro steps above were written for a single site. On a network, activate Pro only after Free is network-active, then open GoBuildWP > Licence on each subsite that should run Pro and confirm what it reports, rather than assuming one activation covers the whole network.

Installing from the command line

WP-CLI's standard plugin commands work for both ZIPs: install the file with wp plugin install followed by its path and --activate. Do Free first, exactly as in the browser.

Free also adds its own command, wp wppilot mcp serve, which serves the same MCP server over standard input and output for a client running on the same machine as the site, such as an editor or a CI job. It refuses to run without WP-CLI's global --user parameter, and calls made through it pass the same safety profile, confirmation and rate-limit checks as calls over HTTP.

The Pro licence is the one step that has no command-line route. Pro adds no WP-CLI command for it, and the key is entered through the Freemius dialog in wp-admin, so finish pass four in a browser even when everything else was scripted.