SEO by platform
SEO for Ghost
Articles arrive in your Ghost site through Ghost's Admin API, with content, images and metadata ready to review in Ghost's editor. New connections publish as drafts, so nothing goes live until someone presses publish in Ghost.
How publishing works on Ghost
The connection publishes through Ghost's Admin API, authenticated by the credential a custom integration issues. New connections publish as drafts by default, and you flip that per connection once you trust the pipeline. Published articles appear in the project's content views with their publish state and, once live, their public URL, which the verifier fetches: a write Ghost accepted but that never became a reachable page shows as not live instead of success.
Drafts by default, live when you say so
New connections publish as drafts, so nothing goes live on your site until someone presses publish in Ghost. Flip that per connection once you trust the pipeline.
Help centre: GhostPublished means the public URL answered
After every publish we fetch the public URL and record what came back. 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.
Articles come off a planned calendar
Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.
Internal links point at pages that exist
With a website selected and an audit completed, the writer links to real crawled URLs from your site, never paths it invents. The 1-to-6 slider is enforced after generation as a hard rule, so the count you set is the count you get.
The connection is probed daily
A daily authentication probe runs against every connection. A failure marks it unhealthy with the cause named, authentication, permissions, or unreachable target, so you find out before the next article tries to publish into a dead connection.
What this connection will not do
Stated up front, because finding out after the first publish costs more. Each line is a fact about what we send Ghost, not a guess about the platform.
Ghost themes control the final rendering, so the connection delivers the content and the theme decides how it looks on the page. Documented: Ghost
Very large images can exceed Ghost's upload limits. When that happens the article still publishes with the image slot noted, and you re-add the oversized image in Ghost. Documented: Ghost
The connection targets one Ghost site, and a second site is a second connection. Documented: Ghost
Connect it in three steps
The same fields the connect wizard asks for, in the order it asks.
Create a custom integration in Ghost
In Ghost Admin, go to Settings, then Integrations, and add a custom integration. Copy the Admin API key and the API URL. You want the full id:secret pair, the shorter Content API credential will not work.
Paste both into the project
In the project's Publishing tab, choose Ghost and paste the site URL and the pair you copied. The optional read-back credential can be added later or never.
Send a test publish
Check that the post appears in Ghost as a draft. Once the first posts reach Published, the chain is proven.
Questions people ask
The ones that decide whether this fits, answered with the verdict first.
- Why does authentication fail immediately?
- Almost always the credential. It must be the full id:secret pair from a custom integration. The Content API value, shorter and without a colon, will not work, and neither will a staff access token.
- The connection works but posts 404. Why?
- The Ghost site is behind a proxy, or the API URL does not match. It must be the admin domain exactly as Ghost's integration screen shows it.
- What happens if I rotate the Admin API key?
- The connection breaks until you paste the new one. Treat the credential like a password, and rotating it in Ghost is exactly how you revoke our access.
Other platforms
Same pipeline, different door. Every platform page states what its connector sends and what it will not.
WordPress
Two connectors, one pipeline. Publish with an application password, or install the plugin and paste one Integration Key. Either way the article arrives with its images uploaded into your own media library, and the publish is confirmed by fetching the public URL.
Webflow
Articles land as items in the CMS collection you point the connection at, your Webflow templates render them like any other item, and new connections create draft items that wait in Webflow for your publish action.
GitHub
Articles commit as markdown files into the repository and path you choose, and your deploy turns each commit into a page. Built for Next.js, Astro, Hugo, Jekyll and any headless setup where a committed file becomes a page on the next build.
SEO by platform
See it on your own site
A free audit grades your site A+ to F, then the calendar, the writer and the Ghost connection do the week's work. No card required.