Discovered Currently Not Indexed Fix for Blogger: New Blog Indexing Solution
A complete step-by-step guide to fix Discovered Currently Not Indexed in Google Search Console for Blogger posts, new blogs and Blogspot websites.
If you are using Blogger and your post is showing Discovered - currently not indexed in Google Search Console, then do not panic. This issue is very common for new Blogger websites, Blogspot blogs and custom domain blogs. It simply means Google has found your URL, but Google has not crawled that URL yet.
Many new bloggers get confused because they submit sitemap, request indexing and still the post stays in Discovered Currently Not Indexed. The reason is simple: discovery and crawling are not the same. Google can know your URL exists, but it may still wait before crawling it.
In this guide, I will explain what Discovered Currently Not Indexed in Blogger means, why this issue happens, what mistakes new bloggers make, and what exact steps you should follow to improve your Blogger indexing.
What Does Discovered Currently Not Indexed Mean?
Discovered - currently not indexed means Google has found your Blogger post URL but has not crawled it yet. In simple words, Google knows that your page exists, but Google has not opened and checked the page content yet.
Simple meaning: Google found your URL through sitemap, internal link or external link, but the page has not been crawled and indexed yet.
This is different from Crawled Currently Not Indexed. In Discovered status, Google has not crawled the page yet. In Crawled status, Google has already visited the page but has not indexed it. So if your Blogger post is discovered but not indexed, your main focus should be crawl priority, sitemap, internal links, website quality and crawl access.
People search this issue with many terms like Discovered Currently Not Indexed Blogger fix, Blogger post discovered but not indexed, Google Search Console discovered currently not indexed, new blog post not indexing, Blogspot indexing problem, Blogger sitemap issue and Blogger indexing problem fix.
Discovered Currently Not Indexed vs Crawled Currently Not Indexed
Before applying any fix, first understand the difference between both Search Console statuses. Many beginners apply the same solution for both, but the focus is different.
| Status | Meaning | Main Focus |
|---|---|---|
| Discovered - currently not indexed | Google found the URL but has not crawled it yet | Improve discovery, crawl priority and internal linking |
| Crawled - currently not indexed | Google crawled the URL but did not index it | Improve content quality and page value |
| Page with redirect | Google found a URL that redirects to another URL | Check final clean URL |
| URL marked noindex | Page is blocked from indexing by noindex directive | Remove noindex if you want indexing |
Want to fix Crawled Currently Not Indexed? Then read this:
Crawled Currently Not Indexed Fix for Blogger: New Blog Indexing Solution
If your Blogger post is in Discovered Currently Not Indexed, then only improving content is not enough. You also need to make sure Google can easily reach and crawl the page.
Why Blogger Posts Show Discovered Currently Not Indexed?
This issue usually appears when Google finds your URL but decides to crawl it later. For new blogs, this is common because Google does not crawl every new website quickly. If your website is new, has fewer internal links, has weak sitemap signals or publishes many posts suddenly, Google may delay crawling.
| Reason | What It Means | What You Should Do |
|---|---|---|
| New blog trust issue | Google is still learning about your website | Publish useful content consistently |
| Weak internal linking | Post is not connected with other posts | Add internal links and Also Read boxes |
| Sitemap delay | Google found URL but has not crawled yet | Submit sitemap and wait properly |
| Too many low-value URLs | Google does not prioritize all pages | Improve quality and remove weak pages |
| Wrong URL version | ?m=1, http or non-preferred URL is discovered | Use clean final URLs everywhere |
| Robots or access issue | Google may not be able to crawl properly | Check robots.txt and custom robots tags |
Real Fix for Discovered Currently Not Indexed in Blogger
Now let us come to the real solution. There is no single button that can force Google to crawl and index every Blogger post instantly. But you can improve the signals that help Google understand that your post is important and worth crawling.
Submit Clean URL
Always inspect and submit the clean Blogger post URL. Do not submit ?m=1 mobile URL.
Submit Blogger Sitemap
Make sure your sitemap is submitted properly in Google Search Console.
Add Internal Links
Link the new post from old related posts so Google can find it easily.
Check Robots Settings
Make sure posts are not blocked by robots.txt or custom robots tags.
Improve Website Structure
Use labels, menus, related post boxes and clean navigation for better discovery.
Update Weak Posts
Improve old thin posts because overall site quality also matters.
Request Indexing
Use URL Inspection and request indexing after checking the live URL.
Wait Properly
Give Google time. Do not request indexing again and again every hour.
Step 1: Use URL Inspection Tool Correctly
The first step is to check the exact Blogger post URL in Google Search Console. URL Inspection helps you understand whether Google knows the URL, whether the page can be crawled, and whether any indexing issue is visible.
- Open Google Search Console.
- Select your Blogger website property.
- Paste your clean post URL in the top inspection box.
- Do not paste ?m=1 mobile URL.
- Click on Test Live URL.
- Check if the page is available to Google.
- If everything is okay, click on Request Indexing.
Want to remove ?m=1 mobile url issue? Then read this:
Blogger ?m=1 Redirect Error Fix: Remove ?m=1 Mobile URL Issue
Step 2: Submit Blogger Sitemap Properly
For a new Blogger website, sitemap submission is very important. Sitemap helps Google discover your posts. But remember, sitemap only helps discovery. It does not guarantee instant crawling or indexing.
You can submit these Blogger sitemap paths in Google Search Console:
sitemap.xml
atom.xml?redirect=false&start-index=1&max-results=500
After submitting sitemap, wait for Google to process it. If your sitemap is submitted but posts are still discovered and not indexed, then work on internal links, content quality and website structure.
Step 3: Add Internal Links From Old Posts
Internal linking is one of the most powerful fixes for new blogs. If your new Blogger post is not linked from anywhere, Google may find it in sitemap but may not crawl it quickly. When you add links from old related posts, Google gets a stronger signal that the new page is important.
For example, if your article is about Discovered Currently Not Indexed in Blogger, then you can internally link to these related posts:
- Blogger sitemap submit guide
- Google Search Console setup for Blogger
- Blogger post not indexing fix
- Crawled Currently Not Indexed fix
- Blogger redirect error fix
- How to add Also Read box in Blogger
Want to automatically add also read box? Then read this
This helps both users and Google. Users get more helpful guides, and Google understands your content structure better.
Step 4: Check Blogger Robots Settings
Sometimes new bloggers accidentally block important pages with custom robots settings. If your post is blocked, Google may not crawl it properly. So before doing anything advanced, check your Blogger settings.
| Setting | Correct Setup | Why It Matters |
|---|---|---|
| Custom robots.txt | Do not block post URLs | Google should access your articles |
| Custom robots header tags | Do not use noindex on posts | Noindex can stop indexing |
| Post URL | Use clean URL | Avoid ?m=1 and tracking URLs |
| HTTPS | Keep HTTPS enabled | Clean secure URL is better |
| Canonical | Clean post URL should be canonical | Avoid duplicate URL confusion |
If you are not sure about robots settings, do not randomly edit them. Wrong robots settings can create more indexing issues.
Step 5: Use Clean Blogger URLs Only
Blogger sometimes shows mobile URLs with ?m=1. This is common, but you should not submit these URLs in Google Search Console. Always submit the clean desktop version of your Blogger post.
Correct URL: https://www.example.com/post-title.html
Avoid URL: https://www.example.com/post-title.html?m=1
Also make sure your internal links use the final clean URL. Do not link to old URLs, redirected URLs, or mobile parameter URLs inside your posts.
Want to remove ?m=1 mobile url issue? Then read this:
Blogger ?m=1 Redirect Error Fix: Remove ?m=1 Mobile URL Issue
Step 6: Improve Website Structure for Crawling
If your blog has poor structure, Google may discover many URLs but crawl them slowly. New blogs need clean navigation and strong internal linking because Google has less trust and less crawl history for them.
Website structure matters a lot because Google should easily understand which pages are important and how your content is connected.
Step 7: Do Not Publish Too Many Low-Quality Posts
Many new bloggers publish 20-30 short articles quickly and then wonder why Google is not indexing them. If your website has many thin or similar posts, Google may discover them but delay crawling or indexing.
Instead of publishing many weak posts, publish fewer but stronger articles. A strong Blogger post should have clear headings, real explanation, examples, FAQs, internal links, images if needed and useful information that solves the user problem.
Step 8: Request Indexing After Checking the Live URL
After checking sitemap, robots settings, internal links and clean URL, you can request indexing using Google Search Console. But do it properly.
Copy Clean URL
Open your Blogger post and copy the clean final URL from browser.
Inspect URL
Paste the URL in Google Search Console URL Inspection tool.
Test Live URL
Check if Google can access the live page without blocking issue.
Request Indexing
If everything is okay, request indexing and wait for Google to process it.
Best Checklist to Fix Discovered Currently Not Indexed
Use this checklist whenever your Blogger post is discovered but not indexed in Google Search Console.
How Long Does Discovered Currently Not Indexed Take?
There is no fixed time. Some Blogger posts move from discovered to crawled in a few hours, some take a few days, and some can take longer. New blogs usually take more time because Google has less crawl history and trust for the website.
If your blog is new, do not check Search Console every hour. Focus on publishing helpful content, improving old articles, adding internal links and building one category strongly.
Common Mistakes New Bloggers Make
Most new bloggers make the same indexing mistakes. If you avoid these, your Blogger indexing can improve slowly but strongly.
| Mistake | Why It Hurts | Better Option |
|---|---|---|
| Publishing random topics | Website topical focus becomes weak | Build one category properly first |
| No internal links | Google may not prioritize the page | Add links from related posts |
| Submitting ?m=1 URLs | Creates URL confusion | Submit clean post URL only |
| Thin content | Low value pages may not be crawled quickly | Add complete and useful information |
| Wrong robots settings | Google may not access posts properly | Keep posts crawlable and indexable |
Final Fix Plan for New Blogger Websites
If your new Blogger website has many posts in Discovered Currently Not Indexed, follow this simple plan for the next few weeks.
Choose One Main Topic
Do not write random topics. Build one strong category first, like Blogger SEO, Education, Jobs or Tools.
Publish Strong Content
Write complete guides with headings, examples, FAQs, tables and real solutions.
Interlink Every Post
Add links between related posts so Google can discover your content faster.
Submit Sitemap
Keep your sitemap submitted and active in Google Search Console.
Update Weak Posts
Improve old thin posts instead of only publishing new articles.
Track Weekly
Check Search Console weekly and track which URLs move from discovered to crawled or indexed.
Conclusion
Discovered Currently Not Indexed in Blogger is not always a dangerous error. It means Google has found your URL but has not crawled it yet. For new blogs, this is very common because Google takes time to decide which URLs should be crawled first.
The real fix is not only pressing Request Indexing again and again. The real fix is to improve crawl signals by adding internal links, submitting sitemap, using clean URLs, checking robots settings, improving content quality and building a proper website structure.
If you follow the steps above, your Blogger posts will have a better chance of moving from discovered to crawled and then indexed. Keep improving your blog, stay consistent, and do not panic if Google takes time.
FAQs on Discovered Currently Not Indexed in Blogger
What does Discovered Currently Not Indexed mean in Blogger?
It means Google has found your Blogger post URL but has not crawled it yet. The page is discovered by Google, but it is not crawled and indexed right now.
Why is my Blogger post discovered but not indexed?
This can happen because of new blog trust issue, weak internal linking, sitemap delay, crawl priority, wrong URL version, robots settings or low website quality.
How do I fix Discovered Currently Not Indexed in Blogger?
Submit clean URL, check live URL, submit sitemap, add internal links, check robots settings, improve content quality and request indexing after proper checks.
Is Discovered Currently Not Indexed bad for SEO?
It is not always bad, especially for new blogs. But if important posts stay in this status for a long time, you should improve crawl signals and internal linking.
Should I request indexing again and again?
No. Request indexing after checking the live URL and improving the page. Pressing the indexing button again and again without changes is not a real fix.
Does sitemap guarantee indexing?
No, sitemap does not guarantee indexing. It helps Google discover URLs, but Google still decides when to crawl and index them.
Can internal linking help with discovered but not indexed?
Yes, internal linking can help because it gives Google more paths to discover and crawl your important posts.
Should I delete posts that are discovered but not indexed?
No, do not delete them immediately. First improve the content, add internal links, check technical settings and wait. Delete only if the post is duplicate or useless.
How long does it take to index a new Blogger post?
There is no fixed time. Some posts index quickly, while new blog posts can take days or longer depending on crawl priority, site quality and internal linking.
