Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Decisions first
Create a dedicated Ghost integration, keep its Admin API key server-side, select Posts versus Pages, send an approved draft with the tested content format, retain the Ghost ID and updated_at value, verify the preview and metadata, then publish and inspect the public theme-rendered URL.
- Admin API keys never belong in browser code.
- Posts and Pages have different editorial and navigation jobs.
- Newsletter delivery and web publication are separate consequential actions.
Choose Post, Page, author, and distribution
Before writing, decide whether the content belongs in the chronological publication, as a static page, in a newsletter, behind membership controls, or in more than one of those surfaces.
Ghost's stable Admin API exposes posts and pages, plus tags, images, newsletters, members, and related resources. That breadth makes explicit scoping important. An SEO guide normally needs post or page write access and image upload, not member management.
Record the author policy, canonical URL, slug, feature image, excerpt, tags, template, access tier, email-only or web status, and intended publish time. Do not infer newsletter distribution from the fact that a post was approved for the site.
| Decision | Safe default | Escalate when |
|---|---|---|
| Resource | Post for editorial; Page for durable standalone | Navigation or template changes |
| Status | Unpublished draft | Direct publish requested |
| Distribution | Web only | Newsletter send or paid access |
| Author | Mapped editorial identity | New staff identity required |
Secure the Admin API and content format
Ghost says Admin API keys are suitable only for secure server-side use. Test the site's expected Lexical or HTML import path rather than converting content during a production write.
Use a named integration with a revocation owner and keep key material out of logs and analytics. Confirm the Ghost URL and API version. The Admin API returns post objects and supports stable browse, read, edit, add, copy, and delete operations for posts and pages.
Ghost's post representation centers on Lexical. If the workflow sends HTML, use the documented format behavior and compare the resulting stored and rendered content. Complex embeds, cards, images, and internal links need fixture tests.
- Server-side token handling
- Versioned API request
- Stable Ghost resource ID
- Tested Lexical or HTML conversion
- Image upload and alt-text policy
- Slug-conflict and retry behavior
Create the draft and inspect the theme
Read-back proves Ghost stored the fields; preview proves the active theme and cards render an acceptable page.
Compare title, slug, excerpt, body, feature image, tags, author, template, access, canonical metadata, status, and update timestamp. Store the Ghost ID immediately so retries update the same resource.
Inspect the preview on desktop and mobile. Themes control headings, metadata, related navigation, image treatment, and subscription calls to action. Resolve theme failures before publication.
Separate publish from newsletter send
Publishing a web page and sending an email have different audiences and reversibility. Require distinct authorization and verification for each.
For web publication, verify the public status, canonical, robots, title, description, H1, image, links, access behavior, and content fingerprint. For any email distribution, show the newsletter, audience, subject, and send state to a separate authorized reviewer.
Measure the canonical page's search job and qualified subscription or product action. Ghost engagement counts can add context, but the original opportunity and search evidence remain attached to the job.
Continue the workflow
Test one draft Post and Page, including content-format conversion, images, theme preview, timeout retry, web publish, and a blocked newsletter action.
- Ghost integration guide: review connection, fields, states, and known issues
- automated content publishing: apply idempotency and public verification
- human-in-the-loop SEO: separate publication and distribution permissions
Questions teams ask
- Should a Ghost Admin API key be used in the browser?
No. Ghost's documentation says the Admin API key is secret and token authentication is suitable only for secure server-side environments.
- Does Ghost use HTML for post content?
Ghost centers post content on a standardized Lexical JSON representation. The API can support format behavior, but the integration should test conversion and rendered cards rather than assume arbitrary HTML is lossless.
- Is publishing a Ghost post the same as sending a newsletter?
No. Web publication and email distribution have different consequences and should use separate, explicit authorization.
Primary sources
The SearchHandled Editorial Team prefers first-party documentation and names the limits of each source. Links were checked on the access date.
- Ghost Developer Docs: Admin API overview and authenticationAccessed August 29, 2026 · Admin API keys belong only in secure server-side environments.
- Ghost Developer Docs: Admin API posts overviewAccessed August 29, 2026
- Google Search Central: Creating helpful, reliable, people-first contentAccessed August 29, 2026 · Quality principles, not a promise that any page will rank.
- Google Search Central: Guidance about AI-generated contentAccessed August 29, 2026
