Skip to content
Try Free →

Ghost integration use cases

Last updated: · 2 min read

What's actually available

There's no Ghost-specific connector in AskVault — no Content API key field, no publish webhook, and no scheduled Ghost-aware sync. What does work: a Ghost blog is a normal, crawlable website, so its published posts can be added to your knowledge base the same way any other site's pages are — by crawling the blog's URLs.

Indexing your Ghost blog

  1. Add your blog as a knowledge source using URL crawling — point it at your blog's homepage or sitemap.
  2. The crawler follows public links on the site, the same as it would for any marketing site or docs site.
  3. Re-crawl when you publish new posts, or turn on auto-resync (Growth plan and above) if you want AskVault to periodically re-check the pages on its own.

This surfaces blog content in chat answers alongside your other indexed pages — there's no separate "blog content recommender" step; it's retrieved the same way any indexed page is.

Limitations vs. a dedicated CMS integration

Worth being upfront about, since a "Ghost integration" page might otherwise imply more than this:

  • No instant on-publish sync. New posts show up after the next crawl, not within seconds of publishing.
  • No membership-gated content. Only publicly reachable pages are crawled; paid-tier and member-only posts behind a login aren't accessible.
  • No dedicated content-recommendation skill. There's no content_recommender skill that proactively suggests a related blog post after the bot answers a question — indexed blog content is retrieved the normal RAG way, alongside everything else in the knowledge base.
  • No Ghost-specific audience tagging. Access control for crawled pages uses the same audience tagging available to any knowledge source, not a Ghost-only mechanism.

FAQ

Does this work with Ghost Pro and self-hosted?

Both, in the sense that either one's public blog is just a website the crawler can reach. There's no Ghost-specific setup either way.

Can I exclude specific posts?

Yes, via the crawler's standard include/exclude path rules — the same mechanism used to restrict any crawl, not a Ghost-specific tag.

Will old posts be removed automatically when deleted from Ghost?

No. A deleted post's page will start 404ing; you'd need to remove that document from Knowledge Hub manually, or wait for the next crawl's dead-link cleanup if that's enabled for the source.

Was this page helpful?