Websites
Set up Ghost
Connect your Ghost publication to make every published post and page searchable as clean text with its real publish date, authors and tags — deeper than crawling the rendered site, so “what did we announce last spring” and “what does the pricing page say now” answer from the publication itself. Read-only.
Before you start
- A Content API key from a custom integration: in Ghost Admin open Settings → Integrations → Add custom integration (any name — it only labels the key) and copy its Content API key.
- The key is read-only by design: it can only ever return published content — drafts and members-only internals stay out by construction — and nothing is ever written to your publication.
- The site's own address, including https:// — self-hosted Ghost and Ghost (Pro) both work.
- Create the custom integration and copy its Content API key as above.
- Documents → Ghost, enter the Site URL (the address the publication is served on) and paste the key as Content API key.
- Choose access groups, Test, then Sync.
What comes in
- Every published post and page becomes one document headed with its author(s), tags, public URL and publish date, followed by the full text as plain prose.
- Pages rank as the site's living word; posts rank as dated announcements, so an old post never outranks the current page.
- Posts or pages restricted to members or paid subscribers are skipped entirely — the Content API exposes only a teaser for those, never the gated body — and Sync notes how many it skipped.
- Internal tags (the ones starting with #) are left out, and a post with no text in its body isn't read. Editing a post or page in Ghost brings the new version in on the next sync.
Access
Access is allow-only: every post and page this source brings in is visible to the groups you choose when setting it up — the Content API carries no reader list of its own to mirror.
Posts and pages are each capped at 2,000, read 100 at a time; Sync notes it if a publication has more, and anything already synced beyond the cap stays searchable rather than disappearing. Test confirms the key works, names the publication it reached and reports how many published posts are visible right now; on failure it says why — a rejected key reports that Ghost rejected the credentials, a wrong address that Ghost could not be reached. To cut access, revoke the key where it was created, under Settings → Integrations in Ghost Admin.
Last updated 20 Sep 2026