Publish to WordPress

The WordPress connection publishes generated articles directly to your site: post body, categories, and images re-hosted into your own media library rather than hotlinked from us.

Create an application password in WordPress

Use an application password, never your real account password. It can be revoked on its own without touching your login, and it's the only credential we accept.

To create one:

Sign in to WordPress admin as an Editor or Administrator. Authors can publish posts but not pages.
Open your profile and scroll to Application Passwords.
Enter a name (SearchBlueprint) and click Add Application Password. Older WordPress versions call it Add New Application Password.
Copy the password it shows — WordPress won't show it again.

WordPress hides the Application Passwords section on a site without HTTPS, and some security plugins hide it too.

Connect it in SearchBlueprint

To connect the site:

Open the project, then Integrations.
Choose WordPress.
Enter your site URL, your WordPress username, and the application password.
Test the connection before saving.

Note that WordPress displays application passwords in space-separated groups. Pasting it with the spaces is fine — they're stripped.

Publish an article

From a generated article, choose Publish and pick draft or published. Draft is the safer default while you're getting a feel for the output.

What happens after you publish

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'll see one of:

Published: The page was fetched and is live.
Checking...: Published recently, not yet confirmed. Hosts deploy asynchronously, so a fresh 404 isn't treated as a failure.
Not live (404): It was written but the public URL doesn't resolve. The post exists in WordPress — the permalink or template is the thing to look at.

Limits and usage

The site must be reachable from the internet. Local or IP-restricted installs can't be published to.
Categories are matched by name and created if missing.
Publishing itself doesn't consume a usage credit — generating the article did.

If something isn't working

Authentication failed. Three usual causes: the application password was regenerated, the username is wrong (it's 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 doesn't return JSON, the block is on the WordPress side.

Images don't appear. Media upload requires the same credential to have upload permission. An author-level account often can't 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.

Is my WordPress password stored somewhere?

Only the application password, and only encrypted. It's never included in anything sent back to a browser, and it's never allowed to travel a redirect to another host. Your real account password is never accepted in the first place.

Does re-publishing an edited article create a second post?

No. We keep the WordPress post id from the first publish and update that post in place. An update never changes the post's slug and never demotes a live post back to draft.

What happens to published posts if I disconnect?

Nothing. They're ordinary posts in your WordPress and stay exactly as they are. Disconnecting deletes our stored credentials and cancels queued sends — the delivery history is kept, so reconnecting the same site later still updates the original posts instead of duplicating them.

Can I connect two WordPress sites to one project?

No. A project holds one WordPress connection — saving the form again replaces it, which is how you rotate a credential. A second site needs its own project; the plugin connection is a separate slot and can coexist.