What it does
Connects a project to a WordPress site through our official plugin. Articles arrive as normal WordPress posts: categories resolved (created when missing), the hero image sideloaded into YOUR media library rather than hotlinked, and Article/FAQ structured data preserved on the page.
Compared to the application-password connection: no WordPress username or password is involved at all, the connection survives password rotations, and the key only authorizes the plugin's own endpoints — it cannot read or edit posts the plugin did not create.
Connect it
- Download the plugin: searchblueprint.io/downloads/searchblueprint-integration.zip
- In WordPress admin, go to Plugins -> Add New -> Upload Plugin, choose the zip and click Install Now, then Activate.
- Open Settings -> SearchBlueprint and copy the Integration Key
(starts with
sbi_). - In SearchBlueprint, open Publishing -> WordPress Plugin, enter your site URL, paste the key, and click Connect.
Plugin settings
On the WordPress side (Settings -> SearchBlueprint) you choose:
- How articles are published — publish immediately, or save as draft for review. SearchBlueprint's own per-article draft/live choice still applies; this is the default when it does not say.
- Default category — used when an article arrives without categories.
- Default author — which WordPress user the posts belong to.
Revoking access
Click Regenerate key on the plugin's settings page. The old key stops working immediately; paste the new one into SearchBlueprint to reconnect. Deactivating or deleting the plugin also severs the connection.
Troubleshooting
- "The SearchBlueprint plugin is not active on this site" — the plugin is installed but not activated, or the site in the URL is not the one you installed it on.
- "The Integration Key was not accepted" — the key was regenerated after you copied it, or it was pasted with a character missing. Copy it again from Settings -> SearchBlueprint.
- A firewall or security plugin blocks publishing — allow requests to
/wp-json/searchblueprint/v1/. Wordfence, iThemes Security and some Cloudflare rules block unknown REST namespaces by default.