What it does
Connects a project to a WordPress site so generated articles publish directly: post body, categories, and images re-hosted into your own media library rather than hot-linked from us.
How to run it
1. Create an application password in WordPress
- In WordPress admin, go to Users, then your profile.
- Scroll to Application Passwords.
- Enter a name (SearchBlueprint) and press Add.
- Copy the password it shows. WordPress will not show it again.
Use an application password, never your real account password. It can be revoked on its own without touching your login, and it is the only credential we accept.
2. Connect it here
- Open the project, then Integrations.
- Choose WordPress.
- Enter your site URL, your WordPress username, and the application password.
- Test the connection before saving.
WordPress displays application passwords in space-separated groups. Pasting it with the spaces is fine; they are stripped.
3. Publish
From a generated article, choose Publish and pick draft or published. Draft is the safer default while you are getting a feel for the output.
Reading the results
Publishing records an event and then verifies it by fetching the public URL and recording what came back. A successful write is not a successful publish - a post can be created and still 404 for a reader if the site renders it differently than expected.
You will see one of:
- Published - the page was fetched and is live.
- Checking... - published recently, not yet confirmed. Hosts deploy asynchronously, so a fresh 404 is not treated as a failure.
- Not live (404) - it was written but the public URL does not resolve. The post exists in WordPress; the permalink or template is the thing to look at.
Limits and cost
- The site must be reachable from the internet. Local or IP-restricted installs cannot be published to.
- Categories are matched by name and created if missing.
- Publishing itself does not consume a usage credit; generating the article did.
When it goes wrong
Authentication failed. Three usual causes: the application password was regenerated, the username is wrong (it is the WordPress username, not the email in some setups), or a security plugin blocks the REST API. Test the connection after each change.
The REST API is disabled. Some hosts and security plugins block
/wp-json/. Open yoursite.com/wp-json/wp/v2/posts in a browser: if that does
not return JSON, the block is on the WordPress side.
Images do not appear. Media upload requires the same credential to have upload permission. An author-level account often cannot upload.
Redirect loops on connect. A site that redirects between www and non-www, or http and https, can strip the auth header along the way. Enter the URL in its final canonical form.