Connect WordPress
SEObox publishes to WordPress through the built-in WordPress REST API, using an Application Password. There’s no plugin to install.
Requirements: WordPress 5.6 or later with the REST API reachable at
https://your-site.com/wp-json/, and a user with the Author role or higher.
Create an Application Password
In WordPress admin, go to Users → Profile (or edit the user SEObox should publish as),
scroll to Application Passwords, enter a name such as SEObox, and click Add New
Application Password. Copy the password it shows — it looks like abcd efgh ijkl mnop qrst uvwx.
If you don’t see the Application Passwords section, a security plugin may have disabled it, or the site may not be served over HTTPS. Re-enable it in the plugin, or ask your host.
Add the connection in SEObox
On your site’s page in SEObox, open Content Management System, choose WordPress, and fill in:
| Field | Value |
|---|---|
| Site URL | Your site’s root URL, e.g. https://example.com (no /wp-admin) |
| Username | The WordPress username (not the email) |
| Application password | The password from step 1 — spaces are fine |
Click Connect.
Publish a test article
Approve an article and click Publish. It should appear under Posts in WordPress within a few seconds.
What SEObox sends
SEObox calls POST {Site URL}/wp-json/wp/v2/posts with HTTP Basic authentication and this data:
| WordPress field | Comes from |
|---|---|
title | Article title |
content | Article body as HTML. If the article has FAQs, a “Frequently Asked Questions” section is added at the end. |
excerpt | Article meta description |
slug | Article slug |
status | publish |
The post ID and permalink WordPress returns are saved on the article in SEObox.
Not sent: featured image, categories, tags, and SEO-plugin fields such as Yoast or Rank Math titles. Add them in WordPress after publishing if you need them.
Troubleshooting
| Error | Fix |
|---|---|
401 / rest_cannot_create | Wrong username or Application Password, or the user can’t publish posts. Use the username, not the email, and a role of Author or higher. |
404 on /wp-json/ | The REST API is blocked. Check security plugins, firewall rules, and that permalinks aren’t set to “Plain”. |
| 403 from a firewall or CDN | Allow-list requests to /wp-json/wp/v2/posts (Cloudflare WAF, Wordfence, etc.). |