How to fix “Discovered - currently not indexed” on Ghost
If Search Console shows “Discovered - currently not indexed” on your Ghost site, you are in the right place. Google knows the URL but has not crawled it yet. This page covers the causes and a step-by-step fix for Ghost. A publishing-focused blog platform. Sitemap and canonicals are automatic; posts have a metadata panel.
Contents
What does this status mean?
The URL was discovered from your sitemap or a link, but Googlebot has not visited it yet. It usually comes from crawl budget, server load or the page being treated as low priority.
Likely causes on Ghost
- The site is large and Google cannot get to every URL.
- The server is slow or throws errors and Googlebot slows down to be polite.
- Many low-value URLs (filters, parameters) fill the crawl queue.
- No internal links; an orphan page known only from the sitemap.
- Ghost note: The sitemap builds itself at /sitemap.xml with child sitemaps for posts, pages, tags and authors. Submitting the main address is enough.
Step-by-step fix on Ghost
- In your Ghost admin go to: Post settings > Meta data, Settings > Code injection and Labs > Redirects.
- The sitemap builds itself at /sitemap.xml with child sitemaps for posts, pages, tags and authors. Submitting the main address is enough.
- Ghost is fast; slowness usually comes from a heavy theme or external scripts. Remove needless scripts in code injection.
- Link to important pages directly from the home page and category pages.
- Put only canonical, 200-returning URLs you want indexed in the sitemap.
- Take filter and parameter URLs out of crawling with robots.txt or canonicals.
- Lower server response time and error rate; watch response time in Search Console crawl stats.
- Send priority URLs through an indexing panel and follow progress with URL inspection in Search Console.
Extra checks for Ghost
- noindex and visibility: Confirm the site is not marked "Make this site private" in settings; a private site is noindex and password-protected. Remove noindex added through per-post code injection.
- robots.txt: Ghost serves a default robots.txt. To customise, add a robots.txt file to your theme; a wrong rule can close post folders.
After fixing
In Search Console start "Validate fix" for this status and resubmit the page with URL inspection. First confirm the blocker is gone with the free Free indexability checker tool; for many URLs follow Bulk URL indexing: how to send thousands of pages to Google. Google makes the indexing decision itself and timing ranges from days to weeks.
More information
Frequently asked questions
What is the difference between "Discovered" and "Crawled"?
"Discovered" means Google knows the URL but has not visited; "Crawled" means it visited but did not index. The first is usually about crawl priority, the second about content quality.
Thousands of my pages have this status. What now?
First decide which ones truly need indexing and remove the rest from the sitemap and internal links. Work in priority order instead of forcing every URL at once.
Where are these settings on Ghost?
Post settings > Meta data, Settings > Code injection and Labs > Redirects.
Related pages
- Ghost: Duplicate without user-selected canonicalFixes
- Ghost: Duplicate, Google chose different canonical than userFixes
- Ghost: Alternate page with proper canonical tagFixes
- WordPress: Discovered - currently not indexedFixes
- WooCommerce: Discovered - currently not indexedFixes
- Shopify: Discovered - currently not indexedFixes