WordPress Integration
Connect a WordPress site to SEOMind using the WordPress REST API and an Application Password. This connection does not require a SEOMind plugin. It is the direct WordPress connection; SEOMind does not currently offer a separate WordPress.com authorization flow.
Before you start
- Use a WordPress site with an available REST API and an HTTPS address. WordPress 5.6 or newer includes Application Passwords.
- Use a WordPress account allowed to create posts. Uploading images also requires media upload permission. An Editor or Administrator account normally has these permissions.
- The site must belong to the current SEOMind project’s Primary Website. SEOMind compares the website host when you connect.
1. Create an Application Password in WordPress
- Sign in to your WordPress admin dashboard and open Users → Profile (or edit the account you will use).
- Find Application Passwords, enter a recognizable name such as
SEOMind, and create the password. - Copy the generated password immediately. WordPress will not display it again. Use this Application Password, not the password you use to sign in to WordPress.
If the Application Passwords section is missing, check that the site uses HTTPS and that a security plugin or site policy has not disabled it. See the WordPress Application Passwords guide.
2. Connect the site in SEOMind
Open Publishing Integrations → Add New Integration, select WordPress, and fill in:
| Field | What to enter |
|---|---|
| WordPress Site URL | The HTTPS base URL where WordPress is installed, such as https://example.com or https://example.com/blog. Do not enter /wp-admin, /wp-login.php, or /wp-json. |
| WordPress Username | The username for the WordPress account that created the Application Password. |
| Application Password | The generated WordPress Application Password. |
Click the button to add the integration. SEOMind tests the credentials against <site URL>/wp-json/wp/v2/users/me before saving the connection. A successful test verifies sign-in; it does not create a post. The WordPress site’s host must match the project’s Primary Website.
3. Send an article
Open an article in SEOMind, choose Publish, select the verified WordPress integration, and choose one of these statuses:
- Publish Now creates a public WordPress post.
- Save as Draft creates a WordPress draft for review and later publication in WordPress.
SEOMind converts the article’s Markdown to HTML and sends the title, content, and selected status to the standard WordPress Posts API. It attempts to upload the featured image and inline Markdown images to the WordPress Media Library. An image upload failure does not stop the post from being created, so check images on the resulting post.
This direct connection currently creates standard posts. It does not send SEOMind’s SEO description, tags, or preferred slug as WordPress fields, and it does not select custom post types. Check those fields in WordPress before publishing a draft.
Troubleshooting
- Authentication failed (401): Confirm the WordPress username and use the generated Application Password, not the normal login password. Create a new Application Password if the old one was revoked.
- Forbidden or blocked (403/406): Check WordPress permissions, firewall rules, and security plugins that restrict REST API requests.
- REST API unavailable or not found: Open
<site URL>/wp-json/wp/v2/users/mein a browser to check the path. A message that authentication is required is expected without credentials; a 404 or blocked response indicates an API or URL problem. - WordPress site mismatch: Select the SEOMind project whose Primary Website has the same host as the WordPress Site URL.
- Article is not public: Check whether you selected Save as Draft. Open the WordPress dashboard to review and publish that draft.
- Images are missing: Confirm the WordPress account can upload media and that WordPress can accept the image files.
Keep each Application Password private and create a separate one for SEOMind. You can revoke it in WordPress when you disconnect the site. For details on the underlying authentication method, see the WordPress REST API authentication guide.