Ghost CMS SEO: Settings, Structured Data and Speed

Ghost already handles much of the technical SEO for you: it creates an XML sitemap, adds canonical tags, outputs structured data on posts and pages, and falls back to sensible metadata when you leave fields blank. Your work is in writing unique metadata, choosing a lean theme, controlling paywalled content and keeping redirects tidy.

The 2024 Web Almanac structured data chapter reported JSON-LD on 41% of pages, up from 34% in 2022, which means a Ghost site’s built-in markup puts it in line with a growing norm rather than ahead of it.

What Ghost does automatically

Ghost is a publishing platform built around blogs, newsletters and memberships, and its technical SEO defaults reflect that. Ghost’s own SEO help page lists the features it provides out of the box:

• Every post and page has its own metadata, and if you leave the fields blank Ghost falls back to the data it already has.
• Twitter Card and Open Graph tags are built in for social previews.
• An XML sitemap is created and updated automatically.
• Canonical tags are added across the site.
• Structured data is included automatically in posts and pages.

This is a stronger default than many CMS installations that depend on a plugin stack. It also creates a trap: because the basics are present, people assume the job is finished. A site can have flawless canonical tags and still publish thin posts with identical meta descriptions and no internal links. Treat the defaults as a foundation to verify, not a result.

Metadata: use the fallback as a safety net, not a strategy

Ghost’s fallback behaviour is helpful, but the fallback comes from your title and the beginning of your excerpt or content. That can produce titles that are too long and descriptions that stop mid-thought. For every post worth ranking, I fill in the metadata fields by hand.

A practical routine for each post:

1. Write the post title for the reader and the search query, keeping the main phrase near the front.
2. Set a separate meta title only if the headline is too long or too clever for a search result.
3. Write a meta description that states what the reader gets, in one or two sentences.
4. Set an Open Graph image and description if the post will be shared on social networks.
5. Check the URL slug. Short, descriptive and free of stop words is the target.

Search engines may still rewrite what they show. That is normal. Good metadata raises the odds that what appears is accurate and persuasive.

Structured data: what is automatic and what you can add

Ghost adds structured data to posts and pages by default. In my audits, I check three things. First, that the markup describes the page honestly: author, headline, dates and images should match what a visitor sees. Second, that nothing in the theme or in injected code duplicates or contradicts it. Third, that the markup type is right for the content. An article is not a product, and an author archive is not a person profile unless the page really is one.

If you need markup that Ghost does not output, such as FAQ-style data, organisation details or product schema for a book or course, you can add JSON-LD through code injection or in a theme template. Keep additions specific to the page they describe, and test them with Google’s Rich Results Test and the Schema Markup Validator. A blanket block of markup injected across every page is how sites end up marking up content that does not exist on the page.

If you run Ghost beside a more configurable system such as the one in my Drupal SEO guide, apply the same markup discipline to both. Remember that structured data helps search engines understand a page. It does not guarantee a rich result and it does not replace content quality.

Memberships, paywalls and indexing

Memberships are where Ghost sites most often create an SEO conflict. If a post is visible only to paying members, Google needs a way to understand that this is a legitimate paywall and not cloaking. Google’s paywalled content documentation says to use JSON-LD with isAccessibleForFree set to false and a hasPart element that identifies the gated section by CSS selector. It explains that this helps Google tell paywalled content apart from cloaking, which violates its spam policies, and it warns that content must actually be served to Googlebot.

My decision rules for a membership site:

Check how your theme and settings serve gated posts to a crawler, and confirm what the preview looks like in search. I would rather lose a few indexable gated posts than leave Google with an inconsistent picture of the site. Whatever you choose, make the choice per content type rather than by accident.

Themes and speed

Ghost’s documentation highlights its modern technology stack and clean semantic markup, and a fast base helps. But speed is a property of the finished site, not of the platform. The theme, images, fonts, embeds and tracking scripts decide what visitors experience.

My checks on a Ghost site:

• Theme markup. Headings should reflect structure. Some themes style a post title as a large heading yet render it as a different element, so inspect the output.
• Images. Upload at a sensible size, add alt text, and avoid very large hero images for posts that do not need them.
• Embeds and scripts. Social embeds, comment widgets and analytics each add weight. Remove any you do not use.
• Core Web Vitals. Check LCP, INP and CLS with field data where available, not just a lab test on a fast connection.

If you are comparing a publishing platform with a design-led builder, the differences in editing control are covered in my Squarespace SEO setup guide.

Content structure: tags, archives and internal links

Ghost organises content with tags and, depending on your theme, tag and author archive pages. These can help readers browse, and they can also become thin pages that compete with your real content. I decide for each tag archive whether it is a useful landing page with a description and a curated set of posts, or a low-value listing that does not need to be indexed.

The same thinking applies to internal links. Ghost makes publishing frequent posts easy, and older posts quietly fall out of sight. Every few months, review which posts bring in search traffic and add links to them from newer, related posts. Planning topics so posts support each other, rather than publishing isolated articles, is the approach I describe in my HubSpot CMS guide on topic clusters, and the principle is platform-independent.

A Ghost blog also tends to be a business’s content engine rather than the whole website. If your marketing site and blog live on different platforms or subdomains, make sure the connection between them is intentional. The trade-offs of that structure are discussed in my headless CMS SEO guide.

Author pages and trust signals

Because Ghost is built for publishers, bylines and author pages are central. Use them properly. Give each author a real name, a short biography that states relevant experience and links to genuine profiles elsewhere. Readers and search quality systems both look for evidence that a real, knowledgeable person stands behind the content. An author page with a photo, a clear subject focus and links to their best work does more for credibility than a generic “Staff” byline.

Keep the markup consistent with what is visible. If the page shows an author name, the structured data should name the same person, and the dates shown should match the dates in the markup. When you update a post substantially, change the visible date honestly rather than republishing old content with a new date.

Redirects and migrations

Moving to Ghost from WordPress or another platform is common, and it is where rankings are most at risk. Before switching, export your URL list, decide the new URL pattern and map each old URL to its replacement. After launch, test a sample of old URLs and confirm each reaches the correct new page in one step. Check Ghost’s current documentation for how redirects are configured on your version and hosting, because the mechanism has varied.

My website migration SEO checklist walks through the entire process, including how to monitor Search Console afterwards. If you are weighing platforms before deciding, the best CMS for SEO comparison sets out where a publishing-focused CMS suits and where it does not.

Questions people ask about Ghost SEO

Next steps

Ghost gives publishers an excellent head start, and the remaining gains come from metadata, structure and speed. If you want help auditing a Ghost site or planning a move to it, my SEO web design and development service covers it, and you can request a free audit through my contact page.

More in this series (SEO by website platform): start with Best CMS for SEO: WordPress vs Shopify vs Webflow vs Custom, then explore:

• Wix SEO: What You Can Control and How to Set It Up
• Squarespace SEO: Setup Guide and Known Limits
• Webflow SEO: Setup, CMS Collections and Best Practices
• BigCommerce SEO: Store Setup Checklist
• Next.js SEO: Rendering, Metadata and Sitemaps
• Magento SEO: Adobe Commerce Technical Setup Guide
• Framer SEO: How to Optimise a Framer Website