Before you start
- You need to be an Administrator or Owner of the Ghost site — only they can add custom integrations.
Step 1 — Create a custom integration in Ghost
- In Ghost Admin, open Settings and go to Integrations (in Ghost 5 it sits under Advanced in the settings sidebar). Click Add custom integration.

Settings → Integrations → Add custom integration
- Name it SEO Sorted and click Add.

Name the integration
- Ghost opens the integration. Keep this page open — you need two values from it:
- Admin API key — 24 characters, a colon, then 64 characters.
- API URL — usually your site address, e.g.
https://yourblog.ghost.io.

The integration's keys — copy the Admin API key and the API URL
Step 2 — Connect in SEO Sorted
Project Settings → Integrations → Ghost → Connect.
The Ghost connect form
The API URL from step 1. A bare domain is fine (
https:// is added), and /ghost on the end
is stripped.Step 3 — Publish
Open an article, click Publish, then Publish now next to Ghost. The dialog confirms Article Published — “Successfully published to your Ghost site” — with a View article button for the live post.What gets published
Only the Facebook (Open Graph) card is filled. X/Twitter card fields are left empty, so Ghost
falls back to its own defaults for them.
Re-publishing, unpublishing and deleting
- Re-publish updates the same Ghost post in place — never a duplicate. If the post was deleted in Ghost, a new one is created.
- Unpublish moves the post back to Draft in Ghost.
- After an unpublish, SEO Sorted forgets the post. Publishing the article again creates a new Ghost post; the earlier draft stays in Ghost.
- Deleting the article in SEO Sorted deletes the Ghost post.
Tracking AI crawlers
Ghost(Pro) requires DNS-only records, so Cloudflare can’t run in front of it and AI crawler tracking isn’t available there. On self-hosted Ghost, use Cloudflare (any site), or send visits from your web server with Any other server (API).Common problems
“An Admin API key looks like <24 characters>:<64 characters>.”
“An Admin API key looks like <24 characters>:<64 characters>.”
The value you pasted isn’t an Admin API key — most often it’s the Content API key, which has
no colon. Copy the Admin API key from the custom integration.
“Ghost rejected that Admin API key…”
“Ghost rejected that Admin API key…”
The key was regenerated in Ghost, or the integration was deleted. Copy the Admin API key
again from Settings → Integrations → your custom integration.
“… did not answer as a Ghost site. Use the API URL shown on your custom integration.”
“… did not answer as a Ghost site. Use the API URL shown on your custom integration.”
Use the API URL shown on the integration. On a custom domain that redirects, try the
*.ghost.io address instead.“Could not reach Ghost at …”
“Could not reach Ghost at …”
We couldn’t open a connection to that address. Check the URL is correct and that the site is
reachable from the public internet — a
localhost or private-network Ghost won’t work.Tables or embeds look different in the Ghost editor
Tables or embeds look different in the Ghost editor
Ghost converts HTML into its own cards. Anything it can’t convert is kept as an HTML card,
so it still renders on the site exactly as published.

