Connect your WordPress site

Chatgpt Grow publishes to WordPress through the REST API, authenticated with an application password: a separate, per-user credential you can revoke at any time. Your main account password is never used or stored.

Last updated: 2026-09-15

Before you start

  • WordPress 5.6 or newer. Application passwords were added in 5.6.
  • Your site served over HTTPS. WordPress only offers application passwords on secure connections.
  • A user account that can publish posts — an Author, Editor, or Administrator.
  • The REST API reachable (we try /wp-json/ and ?rest_route=, so plain permalinks are fine). Some hosts and security plugins block it.

Get your credentials

WordPress
  • Dashboard
  • Posts
  • Media
  • Pages
  • Users
  • Tools
  • Settings

Profile

  • Name
  • Display name
  • Email
  • Role
  • Application Passwords
Illustration — WordPress’s own screens may look different.
  1. 1

    Open your profile

    Sign in to your WordPress dashboard and open your own user profile.

    Menu pathwp-adminUsersProfile
  2. 2

    Find the Application Passwords section

    It sits near the bottom of the profile page, below the password fields. If the whole section is missing, see Troubleshooting.

    Menu pathProfileApplication Passwords
  3. 3

    Create the password

    Type a name that tells you what it is for — "Chatgpt Grow" — then click Add New Application Password. WordPress generates the password and shows it once.

  4. 4

    Copy the password

    It is displayed in groups of four characters. Copy the whole thing and keep it somewhere safe — it is never shown again.

    abcd EFGH 1234 ijkl mnop qrst
    • The spaces are cosmetic: WordPress strips them before checking, so either form works.
    • You can revoke this single password later from the same screen without touching your login password.

Official WordPress documentation

Connect it in Chatgpt Grow

Three credential fields, plus an optional name for the connection. The site URL is the only value that is not a secret.

Chatgpt Grow
ConnectWordPress
Site URL
https://example.com

Your site root, including https:// and any subdirectory WordPress is installed in.

Username
admin

The login name you type at /wp-admin — not your display name and not your email address.

Application passwordStep 4
abcd EFGH 1234 ijkl mnop qrst

The password from step 4. Spaces are fine.

Label (optional)
e.g. Main blog

Optional. A name for this connection so you can tell it apart later.

The connect dialog in Chatgpt Grow, with sample values. Only the credential fields are shown.

What happens after you connect

  • Chatgpt Grow creates a post with the article title, slug, and body, and sets it to Published — it goes live on your site right away.
  • The body is converted from Markdown to HTML and sent through the standard WordPress REST API, so it arrives as ordinary post content you can edit in wp-admin.
  • WordPress does not receive a featured image yet. The article body and its inline images are published as-is.
  • Only one platform can be connected at a time. To publish somewhere else, disconnect WordPress first.

Troubleshooting

  • The Application Passwords section is missing entirely

    WordPress is older than 5.6, the site is not detected as HTTPS, or a security plugin, must-use plugin, or custom code has disabled the feature. Ask your host before assuming it is something you configured.

  • Connection failed with status 401

    The username or the application password is wrong, or the password was revoked. The username is the login name, not the display name. Create a fresh password and reconnect.

  • Connection failed with status 403

    A security plugin, a firewall, or the host is blocking the REST API or application passwords.

  • Connection failed: the user cannot publish posts

    The account is missing the publish_posts capability — Subscriber and Contributor roles do not have it. Connect as an Author, Editor, or Administrator.

  • Connection failed with status 404

    The site URL does not point at your WordPress install, or the REST API is blocked. Check that https://your-site.com/wp-json/ or https://your-site.com/?rest_route=/ returns JSON rather than a 404 page or a plain HTML page.