How to fix “Discovered - currently not indexed” on Blogger
If Search Console shows “Discovered - currently not indexed” on your Blogger 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 Blogger. Google's free blogging platform. Search settings sit on a single screen, but duplicate label pages from the theme are common.
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 Blogger
- 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.
- Blogger note: The sitemap is automatic at /sitemap.xml and may only list recent posts; if you have many posts, also submit pages such as /sitemap.xml?page=2.
Step-by-step fix on Blogger
- In your Blogger admin go to: Settings > Crawlers and indexing.
- The sitemap is automatic at /sitemap.xml and may only list recent posts; if you have many posts, also submit pages such as /sitemap.xml?page=2.
- Heavy themes and many widgets slow loading. Remove gadgets you do not use and shrink images before uploading.
- 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 Blogger
- canonical and duplicate URLs: Blogger adds the canonical tag automatically. Mobile ?m=1 URLs and label pages can repeat content; setting archive and label pages to noindex clarifies the signal.
- redirects and 404: Settings > Custom redirects lets you point an old address at a new one with 301; it only works for addresses inside the blog.
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 Blogger?
Settings > Crawlers and indexing.
Related pages
- Blogger: Duplicate without user-selected canonicalFixes
- Blogger: Duplicate, Google chose different canonical than userFixes
- Blogger: Alternate page with proper canonical tagFixes
- Webflow: Discovered - currently not indexedFixes
- Squarespace: Discovered - currently not indexedFixes
- Joomla: Discovered - currently not indexedFixes