SEO by platform
SEO for WordPress
Two connectors, one pipeline. Publish with an application password, or install the plugin and paste one Integration Key. Either way the article arrives with its images uploaded into your own media library, and the publish is confirmed by fetching the public URL.
How publishing works on WordPress
Articles publish straight into WordPress as ordinary posts. Categories are matched by name and created when missing, images are re-hosted into your media library rather than hotlinked from us, and on each publish you pick draft or published, with draft the safer default while you get a feel for the output. Re-publishing an edited article updates the same post: the slug never changes, and a live post is never demoted back to draft.
An application password, never your login
The direct connection accepts only a WordPress application password. It can be revoked on its own without touching your login, and your real account password is never accepted in the first place.
Help centre: WordpressThe plugin needs no password at all
Install the official plugin and paste one Integration Key. No WordPress username or password is involved, the connection survives password rotations, and the key authorizes only the plugin's own endpoints, never posts the plugin did not create.
Structured data survives, through the plugin
Articles published through the plugin keep their Article and FAQ structured data on the page, printed from wp_head, which is where a script tag survives on WordPress.
Published means the public URL answered
After every publish we fetch the public URL and record what came back. Published shows only when the page was found, a fresh 404 waits out a grace window, and a server error never concludes the page is missing.
Articles come off a planned calendar
Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.
The connection is probed daily
A daily authentication probe runs against every connection. A failure marks it unhealthy with the cause named, authentication, permissions, or unreachable target, so you find out before the next article tries to publish into a dead connection.
What this connection will not do
Stated up front, because finding out after the first publish costs more. Each line is a fact about what we send WordPress, not a guess about the platform.
The direct REST connection cannot carry JSON-LD: WordPress strips script tags out of post content, so sending it would publish the schema as visible text. Connect with the plugin instead and it is printed from wp_head.
The direct REST connection cannot set a separate SEO title: WordPress core's REST API exposes no SEO title field, it lives in Yoast, Rank Math or AIOSEO postmeta, which only a plugin can write. Through our plugin the SEO title lands in whichever of those you run.
The site must be reachable from the internet. Local or IP-restricted installs cannot be published to. Documented: Wordpress
Connect it in three steps
The same fields the connect wizard asks for, in the order it asks.
Create an application password
In WordPress admin, open Users, then your profile, scroll to Application Passwords, name it SearchBlueprint and press Add. Copy the password: WordPress will not show it again. Prefer no passwords at all? Install the plugin and copy its Integration Key instead.
Connect it in SearchBlueprint
Open the project's Publishing tab and choose WordPress. Enter your site URL, your WordPress username and the application password. Pasting the password with its spaces is fine, they are stripped.
Test, then publish
Test the connection before saving, then publish an article as a draft and open it in WordPress. Once the first few posts reach Published, the whole chain is proven.
Questions people ask
The ones that decide whether this fits, answered with the verdict first.
- 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 are ordinary posts in your WordPress and stay exactly as they are. Disconnecting deletes our stored credentials and cancels queued sends, and reconnecting the same site later still updates the original posts instead of duplicating them.
- My site is on wordpress.com, does this apply?
- Use the WordPress.com connection instead. On wordpress.com-hosted sites the /wp-json/ API this connector uses is not reachable, and plans below Business cannot install plugins, so there is a separate connector for them.
Other platforms
Same pipeline, different door. Every platform page states what its connector sends and what it will not.
WordPress.com
Sites hosted on wordpress.com cannot use the self-hosted WordPress connectors: /wp-json/ is not reachable there, and plans below Business cannot install plugins. This connection exists for exactly those sites, and you connect it with your WordPress.com account rather than a pasted credential.
Ghost
Articles arrive in your Ghost site through Ghost's Admin API, with content, images and metadata ready to review in Ghost's editor. New connections publish as drafts, so nothing goes live until someone presses publish in Ghost.
Webflow
Articles land as items in the CMS collection you point the connection at, your Webflow templates render them like any other item, and new connections create draft items that wait in Webflow for your publish action.
SEO by platform
See it on your own site
A free audit grades your site A+ to F, then the calendar, the writer and the WordPress connection do the week's work. No card required.