Ghost integration use cases
Use cases
Three patterns:
Content recommender. After bot answers a customer's question, suggest a related Ghost blog post for deeper learning. About 15 to 25% engagement lift.
Knowledge expansion. Blog posts often cover product details, comparisons, and troubleshooting. Index them; bot answers from them alongside core docs.
Marketing-page enrichment. Visitor browses your blog; bot answers questions citing the same blog content.
Setup
30 minutes:
- Connect Ghost via API. See Ghost integration setup (same flow as WordPress).
- Pick what to index: all published posts, specific tags, or a date range.
- Configure webhook on Ghost side to notify AskVault on publish/edit.
- Trigger initial sync. 500 posts indexes in about 10 minutes.
Sync behavior
- On-publish. Webhook fires within 30 seconds.
- Scheduled. Every 6 hours as backup.
- Manual. Trigger any time.
Content recommendations
When the content_recommender skill runs:
- Customer asks about a topic.
- Bot answers the question.
- Skill searches indexed Ghost posts for related content.
- Surfaces top 1 to 3 posts with title and excerpt.
About 20 to 30% of customers click through.
Audience tags
By default public. Override for member-only Ghost posts:
paid_usersfor paid-member-only posts.internalfor staff-only.
Limits
- Posts indexed. Up to 5,000 per source.
- Sync latency. Within 30 seconds of publish.
- Webhook reliability. Built-in retry.
Common pitfalls
Posts missing. Webhook not configured. Verify under Ghost > Integrations > Webhooks.
Outdated content cited. Sync delay. Trigger manual.
Member-only posts leak to anonymous visitors. Audience tag not applied. Set under source settings.
FAQ
Does this work with Ghost Pro and self-hosted?
Both. Pro uses cloud-API; self-hosted uses Content API with API key.
Can I exclude specific posts?
Yes via tag-based exclusion or audience tagging.
Will old posts be deindexed when deleted?
Yes via webhook event or next scheduled sync.