Does AskVault have a dedicated Ghost Content API integration?

Not today. There's no Ghost-specific connector, Content API key field, or publish webhook. A Ghost blog's public posts can be indexed the same way as any other website: with AskVault's URL crawler.

How do I keep a crawled Ghost blog's content up to date?

Refresh it manually from the Knowledge page: Resync re-reads posts that changed, and running the Web Crawler again adds new posts. Paid plans can set an automatic re-crawl schedule, but until automatic re-crawl is on for your account a scheduled check may not re-read a changed page, so keep using Resync to be sure. There's no Ghost-specific publish webhook.

Can AskVault index membership-gated Ghost content?

No. The URL crawler only reads publicly reachable pages. Member-only and paid-tier content behind a login isn't accessible to it.

Ghost integration use cases

Written by Joseph Russo, Principal Architect, Networks and Tech, AskVault · Reviewed by Allison Chan

Last updated: June 18, 2026 · 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

Add your blog as a knowledge source using URL crawling: point it at your blog's homepage or sitemap.
AskVault finds your posts from the blog's sitemap (Ghost publishes one at /sitemap.xml), the same as it would for any other site.
Refresh when you publish. Run the Web Crawler again to add new posts, and use Resync for edited ones. Paid plans can set an automatic re-crawl schedule, but until automatic re-crawl is on for your account a scheduled check may not re-read a changed page, so keep using Resync to be sure (details).

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 manually, or wait for the next crawl's dead-link cleanup if that's enabled for the source.

Was this page helpful?