Publishing
Publishing that checks the public URL
Connect WordPress, Shopify, BigCommerce, Webflow, Wix, Ghost, GoHighLevel, Snapps or a git repository. Every publish is verified by fetching the public URL.
Every content tool claims it publishes to your CMS.
The quiet failure is the platform accepting the write while the page 404s for every reader, because a draft flag, a theme or a build step got in the way. A write is not a publish until a reader could reach the page.
- 9platforms with a direct connection, each documented in the help centre
- 2universal paths for everything else: a signed webhook and a keyed RSS feed
- 4delivery attempts per article, all carrying one stable id to dedupe on
- 60connections tested per nightly health sweep, oldest checked first
Published means the public URL answered
After every publish the public URL is fetched, so 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.
Help centre: Publish verificationNothing publishes before you look
New connections publish as drafts until you switch them live, on every platform. Nothing reaches a client's site before someone has read the output.
WordPress connects with one key
Install the official plugin and paste one Integration Key, with no username or password, so the connection survives password rotations. The key authorizes only the plugin's own endpoints, never posts the plugin didn't create.
Connections are probed daily
A daily authentication probe runs on every connection, and a failure marks it unhealthy with the cause named: authentication, permissions, or unreachable target. A failed publish marks it at once.
Your endpoint receives signed JSON
Your endpoint receives each article as JSON with HTML, markdown and JSON-LD, signed with an HMAC. Failed deliveries retry up to 4 times against a stable article id, so one article never becomes two posts.
GitHub commits for git-built sites
Articles commit as markdown with front matter into the repo path you set, and your deploy turns each into a page. Git publishes are never marked live: a repo URL proves nothing about the site.
How it works
The sequence, start to finish. Read it in order: each step assumes the one above it has already run.
Connect the platform
Open the project's Integrations tab, choose the platform, paste the credential it issues (application password, API token or key), and send a test publish.
Publish or schedule
Publish generated articles by hand or let planned calendar items flow through, with each connection's draft or live setting deciding whether posts wait.
Read the states
Published, Checking, Not live (404) and Unreachable each name your next move, and the first few posts on a new connection prove the chain.
The other ways people do this
What each approach does, and what happens here instead. Mechanism only, never an outcome claim.
| Approach | How it works | Here |
|---|---|---|
| Copying the draft into the CMS | How it worksYou paste the article, fix the formatting, upload the images and set the meta. It is reliable, and it is the step that stops the calendar in a busy week. | HereThe article goes across with body, images and meta mapped, and the connection's draft setting decides whether it waits for you. |
| A publish integration that trusts the API | How it worksThe platform returns success and the tool records the article as published. A draft flag, an unpublished blog page or a pending build leaves the reader on a 404. | HereThe public URL is fetched after the write. Published means that fetch found the page, and a fresh 404 waits out a grace window first. |
| A plugin holding your username and password | How it worksThe credential is the login itself, so a password rotation breaks publishing, and the plugin can do whatever that account can do. | HereThe WordPress plugin takes one Integration Key that authorizes its own endpoints, and it never touches posts the plugin did not create. |
| Finding out when a connection breaks | How it worksA dead token is discovered by the article that failed to publish at six in the morning, once the schedule has already missed its slot. | HereEvery connection is probed daily and marked unhealthy with the cause named: authentication, permissions, or unreachable target. |
Try the job, or learn the subject
The tool below runs here, on this page, without an account. The rest of the free tools and the lessons sit under it.
CMS detector
Detect the CMS and tech behind a site. It runs here, on this page, with no account.
More free tools, no signup
- Hosting checker
- Identify where a site is hosted.
- DNS lookup
- Look up a domain's DNS records.
Lessons in the Academy
- Publishing to a client's CMS5 min · Intermediate
- WordPress, Shopify, Webflow and the rest: get access right, publish cleanly, and confirm the page is actually live.
- The content production pipeline5 min · Intermediate
- Brief, draft, review, publish and verify: the stages, who owns each, and what passes between them.
- Quality gates before publishing5 min · Intermediate
- The checks every article passes before a client sees it: facts, structure, links, intent match.
Questions people ask
The ones that decide whether this fits, answered with the verdict first.
- Which platforms are covered?
- Nine platforms plus two universal paths. WordPress (direct or via the official plugin), Shopify, BigCommerce, Webflow, Wix, Ghost, GoHighLevel, Snapps and GitHub for git-built sites, plus a signed webhook and keyed RSS feeds.
- Does connecting a platform touch my live site?
- Only when you publish. Every new connection publishes as drafts until you switch it live, so the first posts wait in your platform's own admin for you to read.
- Does publishing cost credits?
- No. Credits pay for producing an article, one for a standard draft and two for a Skyscraper one. Publishing and the verification fetch that follows it are free.
- Do I need a developer?
- Only for the webhook. Every platform connection takes a credential you copy from your own admin, and the WordPress plugin takes a single key.
- What happens if the page 404s after publishing?
- It stays on Checking through a grace window, then shows Not live (404), because hosts deploy asynchronously. The cause is usually on the platform: a draft post, an unpublished blog page, or a missing publish step.
- Can my developer receive articles instead of a CMS?
- Yes. The webhook delivers each article as JSON with HTML, markdown and the JSON-LD as its own field, HMAC-signed with the timestamp inside the signed string. Your endpoint can return the final URL, so verification checks the real page.
- My platform isn't listed. Is there a path?
- Usually, through RSS. Every project can expose a keyed RSS feed of published articles, and site builders without a write API often have an RSS import. The key is the credential, so share it only with what consumes it.
- What happens to my posts if I disconnect?
- They stay where they were published. Articles live on your platform under your account, and disconnecting stops future publishes rather than removing anything already live.
Where this fits
The jobs either side of this one, and the two pages that read it from your side of the desk.
Autoblog
Plan a month of posts. Auto-write drafts each at midnight on its calendar date through the same researched pipeline you run by hand, and every publish is checked at the public URL.
AI article writer
Give it a keyword. It researches, drafts with internal links and images, then scores the result on the same 36 checks that grade audited pages.
White-label reports
Branded PDF reports, branded share pages, and client logins scoped to one project. For agencies that sell SEO under their own name.
Publishing
See it on your own site
A free audit grades your site A+ to F, then shows where this feature pays first. No card required.