SiteLift LogoSiteLiftDocs

GhostGhost

Publish SiteLift articles as Ghost posts, and comparison pages as Ghost pages, through the Admin API.

How it works

SiteLift talks to the Ghost Admin API with a key from a custom integration. Each article becomes a published post with its feature image, meta title, meta description and tags; the structured data goes into the post’s code injection. Posts are matched by slug, so republishing an edited article updates the same post instead of creating a second one.

Setup Guide

  1. 1

    Create a custom integration in Ghost

    In Ghost Admin open Settings → Advanced → Integrations, click Add custom integration, name it SiteLift and save.

    Copy the Admin API Key. It has the form id:secret; keep both halves. The Content API key next to it is read-only and cannot create posts.

    Prefer posts to show a specific author? Use that person’s staff access token instead (Settings → Staff → the user → Staff access token). It works the same way, is limited to that user’s role, and every post is attributed to them. An Author role can publish articles; comparison pages need an Editor or Administrator.

  2. 2

    Connect in SiteLift

    Open Settings → Integrations, choose Ghost and enter your site URL (the one you open Ghost Admin on) and the Admin API Key.

    SiteLift checks the key against your site before saving it. Keys are encrypted at rest.

  3. 3

    Publish

    Articles publish on your content calendar schedule, or right away from an article page. The first post appears in Ghost within a minute.

Tip

Once connected you never log into Ghost to publish. Articles go live on your SiteLift schedule, and edits made in SiteLift are pushed again when you republish.

What gets published

  • Title and feature image. Ghost themes render both, so the H1 and the hero image are removed from the body and sent as title and feature_image (with alt text).
  • SEO fields. The meta title, meta description and a custom excerpt are filled from the article’s SEO data.
  • Structured data. The Ghost editor strips scripts from the body, so the JSON-LD is added to the post’s code injection (head) instead and renders on the live page.
  • Tags. The target keyword and secondary keywords become Ghost tags, created on first use.
  • FAQ and inline images. Stay in the body exactly as written.

Competitor comparison pages

Supported. Comparison pages publish as Ghost pages. Ghost pages are flat, so a page lives at /your-brand-vs-competitor/ at the site root, and the hub is a page at your compare path (for example /compare/). Unpublishing sets the page back to draft.

Troubleshooting

  • 401 Unknown Admin API Key. The key was pasted incompletely or the integration was deleted. Create a new custom integration and reconnect.
  • Could not reach the site. The site URL must be the public Ghost address over HTTPS. Staging sites behind a password or a private network cannot be reached.
  • Post looks unstyled. Ghost converts HTML into its editor format, which is lossy for unusual markup. Headings, lists, tables, quotes and images come through; custom embeds may not.

Still stuck? Use Test Connection on the Integrations page; the message comes straight from Ghost. Or write to support.

Previous

Shopify

Next

HubSpot