How to Connect WordPress to an AI Content Engine for Auto Publishing · BloGoose

Blog · Content Automation · November 20, 2026

How to Connect WordPress to an AI Content Engine for Auto Publishing

Authors

Roktim Saha · Senior software engineer

Roktim Saha builds BloGoose. He is a senior software engineer in India, and Verthilix is the name he uses for that software. roktimsaha.com

Verthilix · Software

Verthilix is the name Roktim Saha uses for the software he builds, including BloGoose. It is not a company. verthilix.com

How to Connect WordPress to an AI Content Engine for Auto Publishing

A finished draft is sitting in an open chat window, and the publish button is still six steps away.

Copy. Paste into the editor. Rebuild the formatting. Find a featured image. Retype the meta description. Fix the slug. Anyone who has tried to connect WordPress to an AI content engine knows that gap — the writing is done, but the post isn't live, and the manual loop quietly eats an afternoon per article.

Closing it is less work than the vendor docs imply. A working connection needs exactly four things:

That's the whole finish line. No plugin is required on most installs, and no paid tier unlocks it.

Below, you'll get the setup sequence in order, the four reasons the Application Passwords panel sometimes never appears, and how to stop a retry from publishing the same article twice. One of those failure states is triggered by a setting your host may have changed without mentioning it — and it looks nothing like a permissions problem until you know where to look.

From there, the rest of the automated SEO content workflow is scheduling and voice, not plumbing.

Here is the exact order of operations.

How Do You Connect WordPress to an AI Content Engine Step by Step?

Connecting takes six steps and about 15 minutes: create an application password, prove it with a single curl call, then paste the bare domain and owning username into the engine. Run the credential test before you configure anything — a pass means every later failure belongs to the tool, a fail means it belongs to the site.

Prerequisites: admin access to WordPress on HTTPS, plus a terminal or API client. Most sites need no plugin at all.

  1. Create the application password (1 minute). An application password is a separate, revocable credential WordPress issues for one app, so you never hand over your login password. Open Users, then Profile, scroll to Application Passwords, name it "content engine", and click Add New Application Password. Copy the key immediately — it is shown exactly once.
  2. Prove the credential with curl (2 minutes). Run curl --user "user:xxxx xxxx xxxx xxxx xxxx xxxx" https://yoursite.com/wp-json/wp/v2/users/me. You should see your user object as JSON, which confirms both the credential and REST routing. The spaces between character groups are cosmetic; the key works pasted with or without them.
  3. Open the engine's connection settings and type the site URL. Enter the bare domain — no /wp-json suffix, no trailing slash. Add either and the tool appends a second path, and every call lands on a 404.
  4. Enter the username that owns the key. Not the site's display name, not the admin email — the login of the account you created the password on.
  5. Paste the password and click Connect. You should see a green connected state within seconds.
  6. Publish one draft, then delete it. This proves write access to /wp-json/wp/v2/posts end to end before real content is at stake.

What if the Application Passwords panel never appears?

Usually the panel is hidden, not removed. WordPress suppresses it when the site is not served over HTTPS, when WP_ENVIRONMENT_TYPE is set to local or staging, when DISABLE_WP_APPLICATION_PASSWORDS is defined, or when a security or host-tools plugin disables it — check those four in that order. If a host policy is the cause and you cannot change it, a small mu-plugin that re-enables the feature through a filter brings the panel back without touching the host's settings.

Worked example: a publisher on a managed host finished the connection in three minutes. The curl call returned their user JSON on the first attempt, so when the engine still reported a failed connection, the credential was ruled out — the URL was the problem, pasted with the /wp-json path included. Switching to the bare domain and reconnecting succeeded on the next try.

If you would rather not run these checks by hand, the BloGoose connect flow walks the same sequence against your site and tells you which side failed.

Once the pipe works, what actually lands is decided by the role and the fields you send with each request.

Which WordPress Role and Which Fields Decide What Actually Lands?

Which WordPress Role and Which Fields Decide What Actually Lands?

Give the connector an Editor account when SEO meta has to land, an Author account when body copy alone is enough, and never a Contributor. Contributor can create drafts but cannot publish, so an autopilot push dies on its first live attempt.

Role decision matrix

RoleCan publishManages categoriesBest for
ContributorNoNoNobody automating publishing
AuthorYesNoSolo operators who set categories and meta by hand
EditorYesYesContent leads running multi-author clusters
AdministratorYesYesAgencies that must install the SEO meta bridge snippet

What we'd choose: Editor. Editor both publishes and manages taxonomy terms, which is the combination a content cluster actually needs — Author publishes but cannot assign the category structure. Contributor is the trap: it writes drafts it can never ship. Administrator is not a default upgrade; it is only required when the SEO meta bridge snippet has to be installed on the site. Connector docs are honest that most sites connect through Application Passwords with no plugin at all — they simply never lead with the role, which is why this bites on launch day.

The payload contract: seven fields, two silent failures

An engine sends seven fields: title, slug, HTML content, excerpt, featured media (which ties into featured image SEO), category and tag ID arrays, and SEO meta. Two of those values are accepted without complaint and then render wrong.

Value sentHTTP responseWhat renders
Category names as strings200 OKPost falls into the default category
Tag names as strings200 OKTags silently dropped
Yoast or Rank Math metaIgnoredEmpty meta description

WordPress expects categories and tags as integer IDs, not names. A name payload returns 200 and the post quietly lands in the default category.

A publisher maps a week of briefs to a custom API connection using an Editor account. The first live push succeeds and every article shows up in the wrong place: default category, empty meta description. The fix is two changes — send category and tag IDs instead of names, and install the bridge snippet that opens the Yoast fields over REST. The next push lands in the right cluster with descriptions intact.

BloGoose handles that payload contract as part of its publishing path, so articles leave the engine already carrying the fields WordPress will accept rather than being hand-assembled in a spreadsheet.

The next question is what to do when a push returns something other than 200.

How to Check It Worked and What Each Error Code Means

How to Check It Worked and What Each Error Code Means

It worked if a GET request to /wp-json/wp/v2/posts returns the post with its slug, category IDs and featured image intact. If it didn't, the status code usually names the cause, and the cause is rarely the password.

  1. 401 Unauthorized: stripped header. On Apache CGI, the Authorization header is often dropped before it reaches WordPress, so a correct Application Password still fails. Add SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1 to .htaccess before you regenerate anything.
  2. 403 Forbidden: role too low. The login succeeded, but the user isn't allowed to perform the request. Compare the role against the table in the previous section.
  3. 404 Not Found: route blocked. This is almost never a credential problem. Switch off plain permalinks, then check for a firewall rule blocking /wp-json/.
  4. Missing panel: feature disabled. The panel disappears when the site has no HTTPS, when WP_ENVIRONMENT_TYPE is set to local or staging, when DISABLE_WP_APPLICATION_PASSWORDS is defined, or when a security or host-tools plugin turns it off. Fix the cause, or re-enable the panel with a filter in an mu-plugin.
  5. 500 Server Error: misplaced filter. A 500 right after a setup change usually means a filter landed in wp-config.php. Move it into an mu-plugin.
  6. Duplicate posts: retry after timeout. WordPress committed the post, the request timed out, and the engine sent it again. Engines should match on slug or a stored post ID.

Worked example: A publish request times out, so the engine retries. WordPress had already saved the first copy, and the retry collides on the slug. Because the engine matches on slug, the second copy lands as a draft and the live post stays untouched. Delete the draft, then ask Google to crawl new posts.

A few questions usually come up once publishing runs cleanly.

Common Questions About Auto Publishing to WordPress

Common Questions About Auto Publishing to WordPress

No plugin is required on most sites, and access is revoked in two places, not one.

Does Jasper publish directly to WordPress?

Check Jasper's own integrations documentation before assuming yes. Direct publishing only exists where the vendor lists application-password support, sitemap import, and post-status control; anything less is export and manual upload. Confirm those three features there, not on a comparison page.

Do I need a plugin to connect?

No. Most sites connect through Application Passwords and the REST API without one. The connector is a fallback for hosts and security plugins that hide the approval screen or disable application passwords outright. Install it only when the profile panel refuses to appear.

How do I revoke an AI content engine's access to WordPress?

Two separate switches exist, and only one revokes immediately. Do both.

Why did the same article publish twice?

Duplicates come from retries. A timed-out publish request gets resent, and WordPress creates a second draft with the same title. Check the posts list before retrying manually, and prefer a tool that stores the post ID it created.

Next up: publishing your first draft this week without opening wp-admin, with AEO optimization running behind it.

Publish Your First Draft This Week Without Opening wp-admin

Three moves, in this order: run the curl test today, connect your domain so the crawl and the publish share one credential, then ship a single draft end to end before you turn on a calendar.

That sequence is the payoff. The first publish is where taxonomy IDs and SEO meta surface — and where a role picked for convenience, rather than for whether meta must land, turns into rework. If the test returned JSON, nothing left here is troubleshooting.

Run it, then check BloGoose pricing when you're ready to run the calendar.

The connection is a credential problem, not a content problem — solve it once and every article after it publishes itself.