Publish to WordPress with the plugin

Our official plugin connects a project to a WordPress site. Articles arrive as normal WordPress posts: categories resolved (created when missing), the hero image sideloaded into your own 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 can't edit posts the plugin didn't create unless you opt in to On-page SEO fixes in the plugin's settings (off by default), which allows named SEO fields only.

Connect it

Install the plugin first:

1. Download the plugin: searchblueprint.io/downloads/searchblueprint-integration.zip
2. In WordPress admin, go to Plugins → Add New → Upload Plugin, choose the zip, and click Install Now, then Activate.

Then connect it, either way:

In one click (recommended). In SearchBlueprint, open Publishing → WordPress Plugin, enter your site URL and click Open WordPress and connect. The plugin's settings page opens on your site in a new tab; press Confirm and connect there. WordPress sends its own key to SearchBlueprint, and the wizard step you left completes on its own — nothing to copy. The link it opens works for 30 minutes and once.

By hand. Open SearchBlueprint → Settings on your site and copy the Integration Key — it starts with sbi_. Back in the same wizard step, paste it and click Connect.

Either way, SearchBlueprint checks the key against your site before it saves anything, so a connection that shows as connected is one that answered.

Plugin settings

On the WordPress side (SearchBlueprint → Settings; before plugin 1.14.0 it was Settings → SearchBlueprint, and that address still forwards), you choose:

• How articles are published: Publish immediately, or save as a draft for review. SearchBlueprint names draft or live on every article it sends, so this default only applies to requests that don't specify one.
• Default category: Used when an article arrives without categories.
• Default author: Which WordPress user the posts belong to.

The settings page also shows which SearchBlueprint project the site is connected to when the one-click flow made the connection.

Meta titles and descriptions on your pages

The plugin shows what SearchBlueprint set on each page the way an SEO plugin shows its own fields:

• A SearchBlueprint box on every post and page edit screen: the meta title, meta description and focus keyword SearchBlueprint set, when they last synced, and where they are live. If someone has since edited the value in Yoast SEO or Rank Math, the box says so.
• A SearchBlueprint column in the Posts and Pages lists, with the sync date and the title.

Where the values go live:

• With Yoast SEO or Rank Math active, they are written into that plugin's fields, so nothing else about your SEO setup changes.
• With no SEO plugin, the SearchBlueprint plugin prints the page's title and meta description tags itself. Your post title and excerpt are left alone.
• All in One SEO and SEOPress keep their fields where the plugin cannot write; the box says so and the value is kept for when you change plugin.

Two directions:

• Pull from SearchBlueprint on the WordPress side: a Pull from SearchBlueprint link under each page in the Pages and Posts lists, the same as a bulk action for many pages at once, and a button in the SearchBlueprint box on the edit screen. It fetches the page's values from the project's on-page mapping and applies them. A page the mapping does not know yet is reported as such, never guessed.
• The whole site at once: SearchBlueprint → Settings → Pull all pages and posts now pulls every published page and post (up to 1,000 at a time, in rounds of 200 with a reload between rounds, so a large site never hits the server's time limit), and the Keep pages in sync box there repeats it once a day on its own. The page shows when the last full pull ran and what it did.
• Edit in WordPress: the box's fields are editable. Save the page and the change is sent back to SearchBlueprint, where the mapping shows the new value as one revision with the old one kept in the page's history. If SearchBlueprint could not take the change, the box says so on the next load.

How they get there from SearchBlueprint:

1. In SearchBlueprint, open the project's On-page → Page mapping. Each page has a proposed meta title and description you can edit or comment on.
2. Press Push live on a row to apply it after reviewing the change, or switch on Sync meta titles and descriptions to WordPress when saved above the table. With that on, a value you save goes live at once and the row says Live on your site.
3. On the WordPress side, On-page SEO fixes must be on in SearchBlueprint → Settings for pages the plugin did not publish itself. It is off until you switch it on.

Only the meta title, meta description, URL slug and focus keyword are ever written. H1s, body text, internal links and structured data on an existing page are never changed, because a page built with Elementor or shortcodes would not survive a rewrite.

Your site's numbers inside WordPress

The SearchBlueprint menu entry opens an Overview page (on the direct-download build the embedded app sits under it as Workspace), and there is a Dashboard widget, both read from the project and cached for an hour, with a Refresh link:

• Site audit: the latest graded audit's score, grade and verdict, findings by severity, and the top five fixes with the page each concerns.
• On-page: pages the mapping covers, pages still to optimise, and pages on the site carrying SearchBlueprint's values.
• Deep audits: the last run of each of the Technical SEO, Schema, Mobile CRO and AI Deep-Dive audits, with its score where the audit states one, its open findings and how many are urgent, and a link to the exported report.
• Content: how many articles SearchBlueprint has published on the site, the newest one, and how many items the content plan holds.
• Rankings: the tracked keywords with position, movement since the previous check, and the ranking page.
• AI visibility: mentions per engine, measured rows only; a sample is never shown as a result.
• Google Search Console: clicks, impressions, click-through rate and average position from the last run, when the project has Search Console connected.
• Credits: the workspace's credits left this month (also shown on the admin bar's SearchBlueprint item, which links to Overview, Buy credits and Settings), the plan and when it renews, with Buy credits and Upgrade plan buttons that open the Plan & credits page in SearchBlueprint. Payment happens there, never inside WordPress. The Dashboard widget shows the same balance.

A block the project has not run yet says so and links to where it runs. The SearchBlueprint box on each post and page also shows that page's status: whether the live title and description match the plan, the recommended H1 against the current one, and the audit's open findings for the page. Page content is never rewritten; an H1 change is yours to make in the editor.

Site Health

Tools → Site Health → Status has a SearchBlueprint connection row: not connected yet, the last contact failed (with the reason the app gave), or connected to which project and when the site last reached it. It reads what the plugin already holds and sends nothing.

Revoke access

Click Regenerate key on the plugin's settings page. The old key stops working immediately — connect again from SearchBlueprint, or paste the new key there. Deactivating or deleting the plugin also severs the connection.

If something isn't working

You see "The SearchBlueprint plugin is not active on this site". The plugin is installed but not activated, or the site in the URL isn't the one you installed it on.

You see "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 SearchBlueprint → Settings.

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.

What can the Integration Key actually change on my site?

Three plugin endpoints, nothing else. Publishing can create posts and update only posts the plugin itself created. The separate on-page-fixes endpoint can edit named SEO fields of other pages only if you turn on On-page SEO fixes in the plugin's settings — off by default.

If I deactivate or delete the plugin, do published articles disappear?

No. Published articles are ordinary WordPress posts and stay on your site; uninstalling removes only the plugin's own key and settings. Publishing stops until the plugin is active again, and attempts say so rather than failing silently.

Where is the key stored, and can it leak?

It's stored encrypted on our side, is only ever sent to your site, and requests refuse to follow redirects — so the key can't be replayed to a host you didn't configure. In the one-click flow, the plugin sends the key only to searchblueprint.io — that address is fixed inside the plugin and is never taken from the link, so a tampered link cannot send your key anywhere else.

What does the one-click link give someone who has it?

Only the ability to attach a WordPress site to that one SearchBlueprint project, for 30 minutes, once — the same thing the admin who made it could do by pasting a key. It is not a sign-in to SearchBlueprint and carries no SearchBlueprint credential. If it expires before you press Confirm, click Open WordPress and connect again for a fresh one.