AEO for Ghost
Popular with publishers and bloggers market share
Ghost is a publisher-focused CMS built for professional content creators, bloggers, and media organizations. It outputs clean semantic HTML, loads fast by default, and includes built-in Article and Author structured data — making it one of the most AEO-ready platforms out of the box. Its headless API also supports custom frontends for maximum flexibility.
Default robots.txt Behavior
Ghost generates a default robots.txt that allows all crawlers and references the sitemap. The file can be customized by editing the routes.yaml configuration or by creating a custom robots.txt in the content directory. No AI bot directives are included by default, but adding them is straightforward via configuration.
Default Structured Data
Ghost includes built-in Article schema with author, datePublished, dateModified, and publisher fields on all posts. Author pages include Person schema. The default Casper theme and most Ghost themes output this schema automatically. However, FAQ, HowTo, BreadcrumbList, and Product schema are not included and require custom implementation via the Code Injection feature.
Common AEO Issues
| Issue | Impact | Fix |
|---|---|---|
| Missing FAQ and HowTo schema | While Article schema is built-in, FAQ and HowTo content lacks structured data that AI engines use to extract specific question-answer pairs | Use Ghost Code Injection (available per-post and site-wide) to add FAQPage and HowTo JSON-LD to relevant posts. Create reusable JSON-LD templates for different content types |
| No AI bot directives in robots.txt | AI crawlers are not explicitly managed, defaulting to each crawler's own crawl behavior | Customize robots.txt via Ghost routes.yaml configuration or content directory override. Add User-agent rules for GPTBot, ClaudeBot, PerplexityBot, and Amazonbot |
| Limited schema customization without Code Injection | Built-in Article schema cannot be extended or modified through the Ghost admin UI — custom schema types require code | Use Ghost Code Injection to add custom JSON-LD scripts. For headless Ghost setups, implement schema in the frontend application where you have full control |
| Theme-dependent markup quality | Custom Ghost themes may not maintain the semantic HTML quality of the default Casper theme, potentially degrading content accessibility for AI crawlers | Audit your theme output for proper heading hierarchy, semantic elements, and schema inclusion. Stick with well-maintained themes or customize Casper directly |
Recommended Plugins
- Ghost Code Injection
Built-in feature for adding custom JavaScript and JSON-LD to the site header/footer (site-wide) or individual posts. The primary mechanism for extending Ghost structured data beyond the built-in Article schema.
- Ghost API (Headless)
Ghost Content API enables headless usage with custom frontends (Next.js, Gatsby, etc.) for maximum AEO control. Source content from Ghost while implementing custom schema, robots.txt, and rendering strategies.
Step-by-Step Guide
- 1
Run an AEO audit
Use AEOprobe to scan your Ghost site. Article schema and content quality should score well out of the box. Focus on AI bot access and any missing schema types beyond Article.
- 2
Configure AI bot rules in robots.txt
Edit your Ghost routes.yaml or add a custom robots.txt in the content directory. Add User-agent rules for GPTBot, ClaudeBot, PerplexityBot, and Amazonbot with Allow or Disallow directives.
- 3
Add Organization and WebSite schema site-wide
Go to Ghost Admin > Settings > Code Injection and add JSON-LD scripts for Organization and WebSite schema in the Site Header. These complement the built-in Article schema.
- 4
Add FAQ schema to relevant posts
For posts containing Q&A content, use the per-post Code Injection to add FAQPage JSON-LD. Structure the schema to match the question-answer pairs in your content.
- 5
Optimize content for AI consumption
Ghost already produces clean semantic HTML. Focus on answer-first paragraph structures, clear heading hierarchy, and comprehensive meta descriptions. Use Ghost's built-in excerpt feature to provide concise content summaries.
- 6
Re-audit and monitor
Run AEOprobe again to verify improvements. Ghost sites typically see strong baseline scores — focus on incremental gains from FAQ schema and AI bot rules. Monitor after Ghost version updates.
Frequently Asked Questions
Does Ghost support AEO out of the box?
Ghost is one of the most AEO-ready CMS platforms by default. It includes built-in Article and Author schema, generates clean semantic HTML, loads fast, and produces well-structured content. The main gaps are FAQ/HowTo schema and AI bot directives in robots.txt, which require manual configuration.
How do I add structured data to Ghost posts?
Ghost includes Article schema automatically on all posts. For additional schema types like FAQPage or HowTo, use the Code Injection feature — available site-wide in Settings > Code Injection, or per-post in the post settings sidebar. Add JSON-LD script tags with your custom schema.
Can I use Ghost as a headless CMS for better AEO?
Yes. Ghost's Content API lets you use it as a headless CMS with a custom frontend (Next.js, Gatsby, etc.). This gives you full control over structured data, robots.txt, rendering strategy, and performance optimization while keeping Ghost's excellent content editing experience.
Is Ghost better than WordPress for AEO?
Ghost has a stronger AEO baseline — built-in Article schema, faster default performance, cleaner HTML output. WordPress has a larger plugin ecosystem for advanced schema types and more granular control. For publishers focused on blog/article content, Ghost is often the better choice. For complex sites needing diverse schema types, WordPress offers more flexibility.