Fix 'Discovered — Not Indexed' in Search Console (2026)
How
to Fix 'Discovered — Currently Not Indexed' in Google Search Console (2026)
A practical, step-by-step fix
for the most common Blogger indexing error — why Google finds your post but
won't index it, and exactly what to change to get it into search results.
What
'Discovered — Currently Not Indexed' Actually Means
Open Google Search Console,
click Pages under Indexing, and if you scroll to 'Why pages aren't indexed' and
see 'Discovered — currently not indexed' next to several URLs, here's the
plain-language translation: Google knows the page exists — usually from your
sitemap or an internal link — but hasn't crawled it yet, or crawled it and
decided not to add it to search results.
How to Rank Blogger Posts on Google
This is different from 'Crawled
— currently not indexed,' where Google has already visited the page and chosen
not to index it because the content didn't clear its quality bar. 'Discovered'
is earlier in the pipeline — often a crawl-priority problem rather than a
content-quality verdict, which is good news because it's usually the easier of
the two to fix.
💡
Google's own documentation says this status typically means Google intended to
crawl the URL but rescheduled it — often to avoid overloading a smaller or
newer site's server. That's exactly why new Blogger blogs see this status a lot
in their first few months.
Step 1:
Confirm the Page Isn't Already Indexed
Search Console data can lag.
Before troubleshooting, rule out a reporting delay:
1.
Copy
the affected URL.
2.
Search
site:yourblog.com "exact post title" directly on Google.
3.
If
it shows up, the page is indexed and Search Console just hasn't refreshed — no
action needed.
4.
If
it doesn't show up, continue to Step 2.
Step 2:
Diagnose the Real Cause
There isn't one single fix —
there are five common causes, and the right move depends on which one applies
to your post:
|
Likely Cause |
How To Confirm |
Fix |
|
Low crawl budget / new site |
URL Inspection shows 'Discovered' with no last-crawl
date |
Publish consistently, request indexing manually for
priority posts |
|
Weak or missing internal links |
Post has 0–1 internal links pointing to it |
Link to it from at least 2 older, already-indexed
posts |
|
Thin or duplicate content |
Post is short, overlaps heavily with an existing post |
Expand with original detail, merge near-duplicate
posts |
|
Not in sitemap |
URL missing from sitemap.xml |
Re-publish so Blogger regenerates the sitemap,
resubmit in GSC |
|
Slow server response |
PageSpeed Insights shows high server response time |
Compress images, remove unused widgets/gadgets |
Step 3:
Request Indexing the Right Way
5.
In
Search Console, paste the exact post URL into the 'Inspect any URL' bar at the
top.
6.
Click
'Test Live URL' first — confirm it shows 'URL is available to Google' before
requesting indexing.
7.
Click
'Request Indexing.' The URL joins a priority crawl queue.
8.
Do
not resubmit the same URL repeatedly — Google has confirmed this doesn't move
it up the queue and can look like spam behaviour.
⚠️
Request indexing only for posts you've already fixed (added internal links,
expanded thin content, etc). Requesting indexing on a weak page repeatedly just
wastes your limited daily quota and doesn't change the outcome.
Step 4:
Strengthen Internal Linking
Google largely discovers and
prioritizes pages through your internal link structure. A page with zero
internal links pointing to it is telling Google it isn't important — even if
the content is good. Add 2–4 contextual links to it from your already-indexed
posts. How I Started Blogging as a Student
Suggested internal links for
LivingTanmay.com — verify exact URLs against your current sitemap before
publishing, since these are based on your known article topics rather than a
live sitemap pull:
|
Anchor Text To Use |
Point To (verify slug before
publishing) |
|
how to rank Blogger posts on Google |
/how-to-rank-blogger-posts-on-google |
|
fixing sitemap and keyword cannibalization |
your sitemap/keyword-cannibalization guide post |
|
best productivity apps for students |
your Best Productivity Apps post |
|
side hustles and earning online as a student |
your Earn Online as a Student post |
|
hidden ChatGPT features worth trying |
your hidden ChatGPT features post |
|
comparing AI chatbots |
your AI chatbot comparison post |
💡
Want this table filled in with your real, live URLs instead of topic guesses?
Share your sitemap link (yourblog.com/sitemap.xml) or your
atom.xml?redirect=false feed and I'll rebuild this table against your actual
published posts.
Step 5: Fix
Thin or Duplicate Content
If a post covers ground already
covered by another post on your blog — or is under roughly 500 words with no
unique angle — Google may deliberately skip indexing it to avoid diluting its
index with near-duplicates. Two options:
•
Expand
it: add original examples, screenshots, an Indian-student-specific angle, or a
comparison table that doesn't exist elsewhere on your site.
•
Merge
it: fold the content into your strongest existing post on the same topic and
301-redirect the weaker URL.
Step 6:
Check Server Speed and Crawl Health
A slow-loading blog can cause
Google to intentionally throttle how often it crawls you, which shows up as a
backlog of 'Discovered' pages. Run your homepage through PageSpeed Insights and
prioritize:
•
Compressing
all images to under 150KB before upload
•
Removing
unused Blogger gadgets and third-party embed scripts
•
Switching
to a lightweight, mobile-first Blogger theme
How Long
Does It Actually Take?
For a small blog, expect
indexing within a few days to two weeks after a clean fix — internal links
added, content strengthened, indexing requested once. If a post is still stuck
after 3–4 weeks with no change, treat it as a content-quality signal rather
than a crawl-queue delay, and go back to Step 5.
Frequently
Asked Questions
Does 'Discovered — Not Indexed'
hurt my whole site's SEO?
A handful of unindexed posts on
a growing blog is normal and not a penalty. It becomes a concern only when a
large share of your posts stay stuck for weeks, which usually points to a
site-wide content or technical issue rather than isolated page problems.
Should I delete pages that never
get indexed?
Only if they serve no purpose
for readers either. If the page has real value but isn't ranking, improving and
internally linking it is almost always better than deleting it.
Does submitting my sitemap again
help?
Resubmitting an unchanged sitemap rarely helps on its own. What helps is making sure the sitemap is current, then pairing it with stronger internal links and Test Live URL + Request Indexing on the specific post.
Join the conversation