If you've updated Ghost recently and noticed a new "Social" option in your admin sidebar, you've run into one of the more ambitious things Ghost has shipped in years. It's called the Social Web, and underneath it is a protocol called ActivityPub, the same open standard that powers Mastodon and a growing list of other federated platforms.
The short version: people on other platforms can now follow your Ghost publication, like your posts, and reply to them, without ever creating an account on your site or even visiting it directly. Here's what that actually means, how it works, and whether it's worth turning on.
What Problem Is This Actually Solving?
For most of the last decade, getting your writing in front of new people meant posting links to closed social networks and hoping the algorithm cooperated. You don't own your audience on those platforms, the platform does, and a single algorithm change can tank your reach overnight.
ActivityPub flips that relationship. It's an open, decentralized protocol, standardized by the W3C, that lets independent platforms talk to each other directly. Ghost's own framing for this is genuinely useful: think of it like email. You can have a Gmail account and someone else can have an address through a completely different provider, and you can still email each other seamlessly. ActivityPub aims to do the same thing for social interactions, follows, likes, replies, reposts, across totally different platforms and companies.
So when Ghost integrated ActivityPub, the practical result is that someone using Mastodon, WordPress (which has its own ActivityPub support), or several other federated platforms can follow your Ghost site directly from their own app, the same way they'd follow anyone else there, and see your new posts show up in their feed.
How It Actually Works
When you publish a new post on a Ghost site with Social Web enabled, Ghost generates an ActivityPub "Create" activity for that content and sends it out to your followers' inboxes on whatever federated platform they're using. Their app then displays it like any other post in their feed, with the ability to like, reply, or repost it, and those interactions get federated right back to your Ghost site.
A few specifics worth knowing:
- You get a fediverse handle automatically, in the format
@index@yourdomain.com, representing your site's homepage. Ghost has also been rolling out the ability to customize the "index" part of that handle, so it doesn't have to stay generic. - A custom domain is required. If your Ghost site is running on a subdirectory path rather than its own full domain, Social Web won't be available to you. This is a structural requirement of how ActivityPub identities work, not an arbitrary Ghost limitation.
- Interactions flow both ways. Someone on Mastodon liking your post shows up as a like on your Ghost site too, and replies from federated platforms appear as comments-equivalent interactions tied to your content.
Notes: A New, Smaller Way to Publish
Alongside ActivityPub support, Ghost introduced a new content type called Notes. Notes are short-form posts, closer to a tweet or a Mastodon post than a full blog entry, and importantly, they only publish to the social web rather than appearing as posts on your actual site.
This matters because it gives Ghost publishers a place for the kind of quick, in-the-moment thoughts that don't really belong in a full newsletter or blog post, without needing a separate Twitter or Mastodon account just for that purpose. You can share a quick reaction, a link, or a short observation as a Note, and it shows up in the fediverse exactly like a native post from any other federated platform.
Two Ways to Read: Inbox and Feed
Ghost didn't just build the ability to be followed, it also built tools for following others, organized into two distinct views:
- Feed shows a chronological stream of long-form and short-form content from accounts you follow across the fediverse, similar to browsing a traditional social timeline.
- Inbox is more focused on direct interactions and replies, the conversational side of the social web rather than the broadcast side.
Together, these mean you can actually use Ghost as a genuine fediverse client, discovering and following other writers and publications, not just broadcasting your own content outward.
What About Bluesky?
Bluesky runs on a different underlying protocol, the AT Protocol, rather than ActivityPub, so it doesn't connect to Ghost natively the way Mastodon does. Ghost reaches Bluesky through a bridging service called Bridgy Fed, which translates between ActivityPub and the AT Protocol so your posts can show up there too. It's worth knowing this is a bridge rather than a direct integration, since it means Bluesky compatibility depends on a third-party translation layer rather than Ghost talking to Bluesky directly.
Turning It On
For Ghost(Pro) users, Social Web is available directly in your admin settings, no extra infrastructure required. You enable it, optionally customize your handle, and your publication becomes followable from any ActivityPub-compatible app almost immediately.
Self-hosted Ghost sites need a bit more setup. Beyond running a recent enough version of Ghost, the analytics and social features introduced in Ghost 6.0 rely on connecting an additional service called Tinybird, run as a separate piece of infrastructure alongside Ghost itself, with its own access tokens to secure. This fits the broader architectural direction Ghost has been taking with newer features: rather than bundling everything into one increasingly complex core application, things like ActivityPub and analytics run as their own services that Ghost coordinates with, which self-hosters now need to account for in their setup.
Before flipping the switch on an existing site, it's worth running Ghost's theme-linting tool, gscan, to check your theme is compatible with the current version, and removing any legacy AMP templates if your theme still has them, since these aren't part of the supported path going forward.
Should You Actually Turn It On?
For most publishers, yes, with very little downside. A few reasons it's worth enabling:
- It's a genuinely new distribution channel that costs you nothing extra to use. You're already publishing your posts. Social Web just makes them discoverable to an additional audience that's actively looking for exactly this kind of independent, non-algorithmic content.
- It fits the kind of person drawn to Ghost in the first place. If you chose Ghost because you wanted to own your audience and content rather than depend on a platform's algorithm, the fediverse's whole premise lines up with that same instinct.
- The audience is still growing, but it's a real one. The fediverse isn't yet the size of the major closed social networks, but it's grown consistently, and it skews toward exactly the kind of engaged, intentional readers who tend to become genuine subscribers rather than passive scrollers.
The honest caveat: if your audience and growth strategy are entirely built around closed platforms you're already active on, Social Web is a nice-to-have rather than a strategic necessity right now. But since enabling it doesn't cost anything or require you to change how you already write, there's little reason not to turn it on and let it run quietly in the background while you keep doing what you were already doing.
A Step Toward the Open Web Ghost Has Always Wanted
Ghost's own framing for this feature leans into something bigger than a feature checklist: a belief that the earliest, more open era of the internet, where independent sites linked to and interacted with each other directly rather than through a handful of closed platforms, is worth rebuilding. Whether or not that vision fully plays out, the practical upshot for you as a publisher is simple. You get a new, free way for people to discover, follow, and engage with your writing, on a protocol nobody owns and nobody can take away from you by changing a policy overnight.
