Publishing to Ghost

Nolorem publishes blog posts directly to your Ghost site using the Ghost Admin API. No plugin is required, because Ghost has a native API that handles authentication, publishing, and media uploads.

Connect your Ghost site

1. Go to Settings then Publishing.
2. Select Ghost as your CMS platform.
3. Enter your Ghost Site URL (for example https://yourblog.ghost.io). Do not include a trailing slash or any path such as /ghost/.
4. Enter your Admin API Key. Find it in your Ghost Admin panel under Settings then Integrations then Add custom integration. The key format is {id}:{secret}.
5. Click Test connection to verify.

Use the Admin API Key, not the Content API Key. The Content API Key is read-only and cannot publish posts.

Push a post

1. Open a blog post in the editor.
2. Click Push to CMS in the post actions.
3. Nolorem formats the content as a Lexical HTML card (Ghost's native format), uploads images, and creates the post via the Ghost Admin API.
4. On success, a link to the live Ghost post appears in the editor.

Nolorem wraps your content in Ghost's Lexical HTML card format, so headings, blockquotes, images, links, and styling all render correctly without conversion issues.

Update an existing post

If you edit a post that was already pushed, clicking Push to CMS updates the existing Ghost post. Ghost uses optimistic concurrency control, so Nolorem always reads the current post state before updating.

Status sync

Ghost supports three statuses: draft, published, and scheduled.

• Setting the status to Publish creates or updates the post as published.
• Setting a future date creates a scheduled post.
• Unpublishing in Nolorem sets the Ghost post back to draft.

Ghost webhooks notify Nolorem when posts change status on the Ghost side. SEO fields (meta title, meta description, OG title, OG description) are sent directly as native Ghost properties, so no SEO plugin is needed.

Connection is failing

If Test connection fails:

• Check the site URL. Use the root URL only, with no /ghost/ path and no trailing slash.
• Confirm you used the Admin API Key, not the read-only Content API Key. The Admin key is the longer value containing a colon separator ({id}:{secret}).
• Make sure you run Ghost v5.0 or later. Older versions may use different API endpoints.
• If Ghost sits behind a reverse proxy or firewall, ensure the Admin API at /ghost/api/admin/ is reachable over HTTPS.

Publishing is failing

If a push fails, the editor shows the error returned by Ghost. Common causes:

• Site unreachable: verify the site is online and the URL is correct. Nolorem applies a 30 second timeout to Ghost calls.
• Invalid or deleted key: if you removed the custom integration in Ghost, create a new one and update the Admin API Key in Settings then Publishing.
• Concurrency conflict: if someone edited the post directly in Ghost, re-push it. Nolorem reads the latest state before each update.
• Image upload failed: Ghost enforces a file size limit. An HTTP 413 error means an image is too large. Use JPG, PNG, GIF, or WebP.
• Scheduling: the scheduled date must be in the future, otherwise Ghost publishes immediately.