Skip to content
AEOprobe
Platform guide

AEO for Ghost

Ghost supplies metadata and structured data for its themed frontend. Check the active theme and post settings first. Do this before you add code or treat a post missing from the sitemap as a fault.

Updated

Default robots.txt behavior

Ghost supplies a default robots.txt. Inspect its served rules. To replace it, put robots.txt in the root of the active theme. Then upload and activate the updated theme. The documented method does not use routes.yaml or a content directory. On Ghost(Pro), your plan must allow custom theme installation.

Decide whether to permit search and user-fetch crawlers separately from training crawlers, within the controls your platform provides. See how AEOprobe distinguishes crawler roles.

Default structured data

Ghost documents automatic structured data, canonical tags and XML sitemaps. The theme’s ghost_head helper outputs page metadata including JSON-LD. Schema types and fields may differ between themes and custom frontends. Inspect the JSON-LD script your site actually publishes.

Common AEO issues

Common AEO issues, their impact and fixes
IssueImpactFix
A custom theme omits ghost_headImpactGhost’s automatic page metadata and JSON-LD are absent from that theme’s output.FixRestore the documented helper in the theme’s head. Then inspect the published page.
An intentional canonical override is mistaken for a sitemap faultImpactA post with a custom Canonical URL is excluded from Ghost’s sitemap.FixCheck the post’s Canonical URL before you change sitemap behavior. Keep the override if it is intentional.

Step-by-step guide

  1. 1

    Inspect the active theme’s metadata

    Check a public post’s canonical and JSON-LD. If a custom theme lacks the automatic metadata, check that its head includes ghost_head. For a headless frontend, inspect the frontend’s own implementation instead.

  2. 2

    Customize crawler rules through the theme

    If you need to change the policy and your plan allows custom themes, add robots.txt at the theme root. Upload and activate the updated theme. Then check the public /robots.txt. Keep the required exclusions and your sitemap reference.

  3. 3

    Review post overrides and supplementary code

    Open the post’s settings and check Canonical URL. A custom value removes the post URL from Ghost’s sitemap. For a specific schema gap, use the post’s Code Injection settings. Site-wide Settings → Advanced → Code Injection applies across the site, so do not put one post’s facts there.

Official documentation

Questions

Can routes.yaml replace robots.txt?

No. Ghost’s documented method places robots.txt at the root of the active theme. Upload and activate that theme. On Ghost(Pro), first check that your plan allows custom themes.

Does a headless Ghost site inherit all theme SEO output?

No. ghost_head belongs to the themed frontend. A custom frontend must implement and serve its own metadata, structured data and crawler files.

The free audit checks up to 3 public pages with no sign-up. Structured data checks read JSON-LD only. Microdata and RDFa are not parsed. Findings do not guarantee rankings or AI citations.

A saved-site audit costs 20 credits. It covers up to 10 pages on Free, 50 on Watch and 100 on Pro. AEOprobe plans are Free at €0/month, Watch at €7/month and Pro at €21/month. Your account shows what you can buy.

Run the free audit on your site