Integrations

Ghost CMS Publishing via the Admin API

Ghost publishers already care about the right things

Ghost attracts a particular kind of publisher: newsletters, independent media, developer blogs — people who chose a platform because it's fast, clean, and opinionated about quality. That audience has a sharper allergy to careless AI content than most, and rightly so. Publishing junk under a masthead people subscribe to burns something hard to rebuild.

Which is exactly why the SEOtopilot pipeline fits Ghost better than a bare generator would: nothing reaches your site until it has been fact-checked claim by claim and approved by you in the review queue. The floor is "verified or visibly flagged," not "sounds plausible."

Connecting: an Admin API key

Ghost doesn't do OAuth; it does Admin API keys, and does them well. In your Ghost admin, create a custom integration — Ghost generates the key — and paste it into SEOtopilot once. From then on:

  • The key is stored encrypted, cryptographically bound to your site's record, and never logged.
  • Revocation is instant and on your side: delete the integration in Ghost admin and access dies.
  • HTTPS is required; we refuse to send credentials over plain HTTP anywhere in the product.

Works identically for Ghost(Pro) and self-hosted installs — the Admin API is the same API.

What arrives in Ghost

Approved articles are rendered to clean, sanitized HTML and created as posts with title, slug, excerpt, and metadata in place. Your theme renders them like any post you wrote by hand — Ghost's typography does its thing, your members see your usual layout, nothing looks imported.

For newsletter-first Ghost sites, draft mode is the natural setting: articles land as drafts, you give them the final read in context, and you decide what goes to the web versus what also goes to inboxes. SEOtopilot deliberately stays out of your email sends — that judgement is yours.

SEO for the platform that skipped the plugins

Ghost ships fast pages and sane markup out of the box, but content strategy — what to write, in what order, against which queries — isn't a platform feature anywhere. That's the layer SEOtopilot adds, and for stacks where Ghost serves as a headless backend, the Contentful and Sanity page describes the adjacent pattern.

Getting started

In Ghost admin: Settings, Integrations, Add custom integration — copy the Admin API key and your API URL, paste both into SEOtopilot, and the connection verifies immediately. Total setup is a couple of minutes, and the first crawl builds your keyword base from what you've already published.

Frequently asked questions

How does authentication work with Ghost?

Ghost uses Admin API keys rather than OAuth — you create an integration in your Ghost admin, paste the key into SEOtopilot once, and it's stored encrypted and bound to your site. Delete the integration in Ghost to revoke access instantly.

Does this work with Ghost(Pro) and self-hosted Ghost?

Both. The Admin API is identical across Ghost's hosted and self-hosted versions, so the integration doesn't care where your Ghost lives — HTTPS required either way.

Can articles land as drafts?

Yes — per-site setting, same as every integration. Approved articles can arrive in Ghost as drafts for a final look in your theme before you hit publish there.