Skip to content
Enjoy 20% off for 12 months on all plans. Use promo code: HYPERGROWTHClaim it

My article didn't publish

A publish can fail at three layers, and the fix differs by layer. Here's the diagnosis order — connection, then platform, then verification state.

Open in the appUpdated 2026-08-22

If an article didn't reach your site, the failure sits at one of three layers, and the fix differs by layer. Work through them in order and stop at the first thing that's wrong.

Check the connection

Open the project's Integrations tab. An unhealthy connection explains everything downstream, so fix it first with the connection repair order →: re-paste the credential, check the scopes, and check the target.

Check the platform's own state

The write may have succeeded into a platform that isn't showing it: a draft awaiting publish (the default for new connections), a Webflow site that needs its own publish action, a Shopify blog not linked in navigation, or a Wix site without the blog app. The platform pages in this help centre list each one's quirks.

Read the verification state

We fetched your public URL and recorded what came back — the state table → says what each value asks of you. Note that Not live (404) with a healthy connection almost always means the platform layer.

Read the publish record

The publish record on the article shows the outcome per attempt. A failed attempt names the platform's refusal — auth, scope, or limit. That text is the platform talking, and searching this help centre for it usually lands on the exact fix.

Limits and usage

  • Retrying a publish is safe. Articles publish to a stable slug, so a retry overwrites its own earlier attempt rather than duplicating the post.
  • A failed publish doesn't consume extra generation credit — the article exists; only delivery failed.
  • Verification rechecks every few minutes while the state is still open, so a quick platform-side fix flips it without republishing. Once the state settles, retry the publish — retries are safe and overwrite the same slug.

If something isn't working

Everything checks out and the post still 404s

Why this happens: caching. Some hosts cache 404s briefly.

To fix: give it the grace window — verification does.

One platform fails repeatedly across projects

Why this happens: the platform changed something, like an API version or its auth rules.

To fix: check the platform's page here for updates, and file it to support if the docs haven't caught up.

Publishes succeed but the post lands unformatted

Why this happens: that's the theme's rendering, not delivery. See the platform's page for what the connection controls versus what the theme does.


How long do I have before verification stops rechecking?

Not long — the check runs every 5 minutes, a missing page gets a 5-minute grace window, and verification gives up after at most 5 checks. A fix that lands after the state settles isn't picked up automatically; retry the publish. Retries are safe — they overwrite the same slug.

Was this page helpful?

Still stuck?

Email us and the team replies from the same address. If you're signed in, Ask anything in the app answers from these guides.