Publishing
Stop pasting posts in, and see which ones loaded
Stop copying articles into each client's CMS. Connect their site once, approve the drafts, and see which pages are really live.
Try it. This is searchblueprint.io's own data.
1Five clients, five CMSs
Connect each client's site with a key from its own admin.
You've kept a login for every client's CMS and pasted each post in by hand, images and all. Enter the site and we check what it runs on, then you connect it once. You'll stop copying articles across.
- WordPress, Shopify, Webflow, Wix, Ghost and more
- Marked Detected only when we could reach it
- Setup steps you can email to their web person
Connect Shopify
- Store name
- Client ID
- Client secret
2Before anything reaches the client
Nothing goes live until you switch it on.
You've worried a tool would post to a client's site before anyone read it. Every new connection sends posts as drafts, into the client's own admin. You'll switch a site to live when you trust it, one site at a time.
- Drafts by default on every new connection
- Live for one site, drafts for the rest
- One switch stops auto-publishing for a site
Next post
SEO Automation Guide: What to Automate (and What Not To)
Saved as a draft
3The client on WordPress
WordPress without their admin password.
You've been asked for a client's admin login just to post a blog. Our plugin takes one key instead, and it only adds and updates the posts it created. You'll never have to ask for a password, and a password change breaks nothing.
- One key, no username or password
- Other posts left alone unless you allow SEO fixes
- Regenerate the key and access stops at once
Integration Key
sbi_4f9c...a21e
- SEO Automation Guide: What to Automate (and What Not To)Created by the pluginCan update
- 7 SEO Retainer Alternatives That Beat Monthly ContractsCreated by the pluginCan update
- About usNot created by the pluginCan't touch
- Our servicesNot created by the pluginCan't touch
4After you publish
See which posts really loaded.
You've seen saved on screen and a 404 on the site. After each publish we open the public page, and it says Live only once the page loads. You'll stop clicking through every post to check.
- Checked at the address readers use
- A fresh page gets a few minutes' grace
- A 500 from your host is retried, not called missing
SEO Automation Guide: What to Automate (and What Not To)
- We couldn't publish this31 Jul, 16:26 UTC
Published, but the page is not live yet: https://leotansingapore.github.io/sb-publish-test/content/blog/seo-automation-guide-what-to-automate-and-what-not-to.html returned HTTP 404. The site may still be deploying - this is re-checked automatically and never published twice.
5The post that didn't appear
Hear a connection broke before a post fails.
You've found out a client's connection died when the post didn't show up. Every connection is tested each night, and a broken one says Action needed, what went wrong, and offers Reconnect. You'll fix it before the next post is due.
- Tested nightly, nothing published
- What broke, in plain words
- Auto-publish skips it until it's fixed
leotansingapore/sb-publish-test
Delivered
1 article
The platform rejected the saved credentials. Reconnect with a fresh key or password.
6The custom-built site
Custom-built sites get each article by webhook.
You've got a client on a custom build, with no CMS to connect. A webhook sends each article to their developer's address in HTML and markdown, signed if you set a secret. You'll hand over articles without a copy and paste.
- Each article as JSON, in HTML and markdown
- Every retry carries the same article id
- Three lookups in Claude Code today, no key
{
"id": "3e6714a4-f912-4a62-bc03-c049de3e45cf",
"event": "content.published",
"title": "SEO Automation Guide: What to Automate (and What Not To)",
"slug": "seo-automation-guide-what-to-automate-and-what-not-to",
"metaTitle": "SEO Automation Guide: What to Automate & What Not To",
"contentMarkdown": "# SEO Automation Guide: What to Automate (and What Not To) ..."
}- Nothing sent yet
And the small stuff, handled
Email the steps. Send the setup steps to whoever runs the site, with no password in them.
Posts stay put. Disconnect a site and everything already published stays where it is.
Free to publish. Publishing and the live check after it cost no credits.
RSS for the rest. A private feed for site builders we don't connect to.
Check again. Fixed a page that didn't load? Press Check again and it's fetched within five minutes.
Private sites count. A password-protected page reads Published, behind a login, not missing.
Connections that tell you what happened
Before
Publishing plugin today
- Signs in with
- Your admin username and password
- Change password
- Publishing breaks
After, with SearchBlueprint
Our WordPress plugin
- Signs in with
- One key, no password
- Change password
- Nothing breaks
- Can touch
- Only posts it created, unless you allow SEO fixes
You connect once without handing over your login, and a password change never stops your posts.
Sample businesses. Yours is built from your own pages.
Try it free, right here
The tool below runs here, on this page, without an account.
More free tools, no signup
Lessons in the Academy
- Publishing to a client's CMS5 min · IntermediateWordPress, Shopify, Webflow and the rest: get access right, publish cleanly, and confirm the page is actually live.
- The content production pipeline5 min · IntermediateBrief, draft, review, publish and verify: the stages, who owns each, and what passes between them.
- Quality gates before publishing5 min · IntermediateThe checks every article passes before a client sees it: facts, structure, links, intent match.
Questions people ask
What can I connect today?
Publishing connections, the WordPress plugin, the webhook and API keys open in October. Today, Claude Code, Cursor or any MCP client can add our server with no key and look up a page's tags or whether Google's AI answers cite a site. The Claude connector is rolling out soon, and connecting Google Analytics and Search Console opens shortly.
Which platforms can I connect?
WordPress (with our plugin or an application password), WordPress.com, Shopify, BigCommerce, Webflow, Wix, Ghost, GoHighLevel, Snapps, Duda (in beta) and GitHub, plus a webhook and a private RSS feed for everything else.
Does connecting a site change anything on it?
Not by itself. A new connection sends posts as drafts into the site's own admin, and nothing goes live until you switch that site to live.
Does publishing cost credits?
No. Credits pay for writing an article. Publishing and the live check after it are free.
What if the page doesn't load after publishing?
A new page gets a few minutes first, because some hosts are slow to put it up. If it still answers not found, it reads Not live (404), and the cause is usually on the site: the post is still a draft or the blog page is hidden. Fix it and press Check again. Posts sent to a GitHub repository are the one exception: your own build confirms those.
What happens to my posts if I disconnect?
They stay where they are. Disconnecting stops new posts and removes nothing that's already live.
Where this fits
Get posts onto every client's site, and see them load.
Enter your site. Your first plan is free, no card. Publishing opens in October.
- Free first plan
- No credit card
- Keep your plan