ClimbAI
Integrations

WordPress

Connect WordPress with an Application Password: what gets published, what is WordPress-only, and how to fix a failed connection.

Updated 2026-09-13

Climb AI connects to WordPress over the standard REST API using an Application Password — not your login password, and not a plugin. The connection needs your site URL, your WordPress username, and that Application Password.

  1. 1
    Create the Application Password
    In your WordPress admin, go to Users → Profile, scroll to Application Passwords, name it (e.g. "Climb AI") and click Add New Application Password. Copy the generated password immediately — WordPress shows it once.
  2. 2
    Confirm your user role
    Use the same username you log in with, and make sure that user has a role that can publish posts (Administrator or Editor). A Contributor or Author-without-publish role will authenticate but fail to go live.
  3. 3
    Enter the credentials in Climb AI
    In site setup, choose WordPress and enter the site URL, username, and Application Password. Climb AI checks them immediately against /wp-json/wp/v2/users/me.

What gets published

Sent to WordPressRead from WordPress
Title, body, category (created if missing)Live post URL, once published
Featured image and OG image (uploaded to Media Library)Media IDs for uploaded images
Post status: created as draft, then flipped to publish—
New posts are created as a draft first and switched to publish only after the post ID is saved. If a request is interrupted mid-publish, a retry can leave a stray draft — it will never create a second live post.

WordPress-only features

  • Alt text sync — when the Images agent rewrites an image's alt text, it pushes the update straight to that image's WordPress media item.
  • Image compression and replacement — images can be re-compressed to WebP, resized, and re-uploaded to your Media Library, replacing the original.
  • GEO fix files — the GEO Agent can push fix code (schema, FAQ blocks, etc.) directly into a post or page it matches by URL slug, editing the raw Gutenberg/shortcode source so it doesn't break block markup.
These three only work for WordPress. Other platforms get the article itself, but not automatic image optimisation, alt-text sync, or in-place fix-file application.

Common connection errors

ErrorCauseFix
"responded with non-JSON content"A security plugin (Wordfence, iThemes, etc.) is blocking or altering REST API responsesAllow-list /wp-json/wp/v2/* in the plugin, or temporarily disable it to test
"API endpoint not found" (404)Permalinks are set to "Plain" instead of "Post name"Go to Settings → Permalinks and choose "Post name", then save
"Authentication failed" (401/403)Wrong username, or the Application Password was mistyped/regeneratedRe-copy the Application Password from Users → Profile and re-enter it exactly, spaces included
Connects but never goes liveThe account has a role without publish permissionUse an Administrator or Editor account

Frequently asked questions

Yes — it is scoped to REST API access on your site and can be revoked any time from Users → Profile without changing your login password.

Related
  • Connect your site — What each onboarding step asks for, what gets auto-filled, and where to pick a publishing platform.
  • Article images — Choosing a style, how many images each article gets, what counts against your image allowance, and how alt text gets written.
  • GEO audit and fix files — What a GEO audit scores, the fix categories it generates, and how to apply them — one click on supported CMSs, copy/paste elsewhere.
Ready to try it on your own site?

5-day free trial, nothing charged until day 6, 30-day money-back after that.

Try Now For $0.00

5-day free trial · 30-day money-back · price locked for life

Still stuck? hello@climbai.io

Try Now For $0.00