WordPress sites

What the integration does

Connect any number of self-hosted WordPress sites via the standard WordPress REST API and application passwords — works with any stock WordPress installation (5.6+) with no plugins required. Once connected, each site becomes a publishing destination for articles and Content autopilots, with category browsing for targeting, custom metadata for organization, screenshots for at-a-glance recognition, and connection testing on demand.

Connecting a site

Automatic connection (recommended)

1. Open Integrations → WordPress and click Connect site.
2. On the Automatic tab, enter the site URL (include https:// if the site uses SSL).
3. Approve the connection on the WordPress site when redirected. After approval, you return to WebGPT with the connection already established.

Manual connection

When automatic isn't available or manual credentials are preferred:

1. Click Connect site and switch to the Manual tab.
2. Enter the site URL.
3. Enter a WordPress username with Editor or Administrator role.
4. Paste a WordPress application password (see below for how to generate).
5. Save. The connection is verified with a live API call; a success message confirms the credentials work and the REST API is accessible.

Generating a WordPress application password

Application passwords are a built-in WordPress feature (5.6+) that allow external apps to access the REST API without the main login password.

1. Log in to WordPress admin with an Editor or Administrator account.
2. Go to Users → Profile (or Edit Profile from the top-right menu).
3. Scroll to Application Passwords.
4. Enter a name ("WebGPT" works) and click Add New Application Password.
5. Copy the generated password immediately — WordPress only displays it once.
6. Paste it into the WebGPT connection form.

Reconnecting an existing site

Sites that exist in the dashboard but aren't connected to WordPress (for example, added via Cloudflare sync, or with expired credentials) show a Connect WordPress prompt on their card. Click it to open the connection form with the URL pre-filled. Reconnecting preserves all existing site data — categories, metadata, marketplace settings — and only updates the credentials.

Adding metadata

After connecting, enrich each site record for organization at scale:

• Category — Custom grouping ("Client sites", "Personal blogs", "E-commerce").
• Hosting provider — Where the site is hosted.
• Registrar — Where the domain is registered.
• Owner — Useful when managing sites for multiple clients or team members.
• Language — The site's primary language.
• Expiration date — Domain expiration, for renewal tracking.
• Notes — Any additional context.

Site management

Each connected site has a card with per-site actions: Generate screenshot (fresh homepage capture), Test connection (verifies credentials and API access), Edit (URL, credentials, metadata), View categories (the site's WordPress post categories, used when targeting publishes), and Delete (removes from WebGPT; doesn't affect the WordPress site itself).

Image watermark

Each domain has an optional watermark configuration in the Details tab — when enabled, a text overlay is added to every image published to that domain. Configure:

• Watermark text — Defaults to the domain name; customizable per site.
• Font — Choose from 1,900+ Google Fonts (downloaded and cached on first use).
• Position, opacity, color, angle — Standard watermark controls.

Domains without per-site settings inherit account defaults. The publish page and Content autopilot tasks each have their own per-article watermark toggle.

Settings tab

Manage the dropdown values used in site metadata. Categories, Registrars, Hosting providers, and Owners each have their own list — add, rename, or delete entries, and every site edit form draws from these lists. Categories here are WebGPT organizational groupings, separate from WordPress post categories.

Using connected sites

Connected sites become publishing destinations throughout WebGPT:

• AI articles — Pick a connected site and category; content posts directly via REST API.
• Content autopilots — Each task can target a different connected site and category; the bot publishes on schedule.

WordPress categories are fetched and cached per connected site, so targeting a specific section is a dropdown selection rather than a separate lookup.

Troubleshooting

• Connection fails — The error message names the specific cause: "not a WordPress site" means the URL doesn't expose a WordPress REST API; "REST API blocked" means a security plugin (Wordfence, iThemes Security, etc.), server firewall, or .htaccess rule is restricting /wp-json/; "bad credentials" means the username or application password is wrong (spaces are part of the password — copy it exactly); connection timed out / failed means the site is unreachable from the server. Less common causes include the WordPress user lacking the Editor/Administrator role and SSL certificate issues.
• REST API check — Visit https://yoursite.com/wp-json/wp/v2/posts in a browser. If it doesn't return JSON, the REST API is being blocked server-side.
• Credentials expired — Re-test the connection after changing WordPress passwords, updating plugins, or modifying server settings. If it fails, generate a new application password and update the connection.