Why Your Ghost Pages Aren't Getting Indexed (and How to Fix It)

Ghost is one of the more SEO-friendly platforms you can publish on. It server-renders clean HTML, auto-generates a sitemap, and handles canonicals and structured data for you. So when Ghost pages will not index, the cause is rarely technical capability. It is almost always a visibility setting or thin auto-generated content. Here is how to find which.

Why isn't my Ghost site getting indexed?

A Ghost site usually fails to index because it is still in private mode, not because Google cannot read it. Ghost has a "Make this site private" setting with password protection, and when it is on, the entire site sits behind a shared-password gate and search features are switched off. Sites are often set to private during initial setup and then launched without anyone turning it back off, which makes this the single most common accidental cause. After ruling that out, the usual suspects are members-only content that hides the body from crawlers, and large numbers of thin, auto-generated tag and author pages that Google crawls but decides not to index. Because Ghost gets the technical fundamentals right, fixing indexing is mostly about removing whatever is telling crawlers to stay out and making sure the pages you care about have real, unique content. Each of these is quick to check.

Does Ghost's private mode block search engines?

Yes, private mode blocks search engines completely, and it does so by design. Ghost's own changelog states that when you enable password protection, "all social and search engine optimisation features are disabled, and visitors must enter the password to be able to view your content." The setting, "Make this site private" with its "Enable password protection" toggle, lives in your Ghost admin settings. While it is on, every visitor (and every crawler) hits a password form instead of your content, so nothing can be crawled or indexed. This feature exists for staging sites and genuinely restricted blogs, which is exactly why it is so easy to leave on by accident after building a site privately. If your whole Ghost site is missing from Google, check this first. Turning it off restores the SEO and social features Ghost disabled and lets crawlers reach your pages again. Note that this is a simple shared-password gate, not robust security, so do not rely on it to protect sensitive content.

Are members-only and paid Ghost posts indexed?

The gated portion of members-only and paid posts is not indexed, because the content is restricted server-side. Ghost lets you set each post's access to Public, Members only, Paid-members only, or Specific tiers. When a post is gated, the full body is delivered only to authorized members, so a crawler requesting the page sees just the gated or preview portion, not the complete text. That is correct behavior for paywalled content, but it means the article's depth is invisible to Google, which can leave it looking thin. Ghost's recommended pattern is the Public preview feature: you add a divider so the opening of the post is freely readable by both visitors and Googlebot, while the main body stays behind the membership wall. That gives Google real, indexable content to work with from an otherwise gated post. If important articles are gated and not ranking, adding a substantial public preview is the fix.

Why does Ghost render well for search engines and AI crawlers?

Ghost renders well because it serves server-rendered HTML, so your content is in the page source rather than built by JavaScript. Ghost themes use Handlebars on Node.js and deliver fully rendered static HTML to the browser, which avoids the SEO pitfalls of JavaScript single-page apps where content only appears after scripts run. This matters more than ever in 2026, because the AI crawlers behind ChatGPT, Claude, and Perplexity do not execute JavaScript; they read the raw HTML and move on. Since Ghost puts your headings, body text, and metadata directly in the initial HTML response, both classic search engines and these non-rendering AI crawlers can read your content. In other words, Ghost does not have the client-side-rendering problem that makes platforms like raw Notion sites hard to index. For more on that distinction, see does Google index JavaScript. The upshot for Ghost: if a public, server-rendered page still is not indexed, the cause is content value or linking, not rendering.

Why does Search Console say "Crawled – currently not indexed" for Ghost pages?

This status means Google fetched the page and chose not to index it, which on Ghost usually points at thin or duplicative auto-generated pages. Ghost automatically creates tag and author archive pages and lists them in its sitemap, and it does not block them in robots.txt. On a small or new site, those archive pages often have little unique content, so Google crawls them and decides they do not merit indexing. The same goes for short posts and near-duplicate pages. The fixes are the standard content-quality moves: deepen thin posts, be deliberate about which tags you actually use rather than tagging every post a dozen ways, and strengthen internal links to the pages that matter. New Ghost sites also simply get crawled less until they build authority, so some patience is warranted. Our explainer on Discovered, currently not indexed covers how to tell these statuses apart and fix each.

How do I get a Ghost page indexed in Google Search Console?

Make the site public, then verify it in Search Console and request indexing. Ghost auto-generates an XML sitemap at /sitemap.xml, structured as an index pointing to separate sitemaps for pages, posts, authors, and tags, and it updates automatically when you publish. The fix loop:

1. Confirm private mode is off so crawlers can reach the site at all.
2. Submit /sitemap.xml in the Search Console Sitemaps report.
3. Run URL Inspection on the page to see how Google views it.
4. Click Request Indexing for priority pages, and avoid re-requesting unchanged ones, since Google recrawls automatically.

What Search Console will not do is alert you when an already-indexed Ghost post quietly drops out after a theme change, a re-publish, or an accidental return to private mode. SearchOptimo re-checks the index status of every URL on a schedule and alerts you the moment a page falls out, so a problem shows up in a dashboard instead of in your traffic.

If you publish at any real volume on Ghost, see whether SearchOptimo is worth it for your case, or start free and watch your own URLs.