How to Fix Discovered Currently Not Indexed Pages?

Discovered currently not indexed? Learn why Google skips your blog posts and how to get them indexed with confidence.

“Discovered currently not indexed” in Google Search Console means Google knows your blog post’s URL exists but has not crawled it yet. To address it, check your XML sitemap, strengthen internal links, review your website’s technical health, and ensure your content provides genuine value. Then inspect the URL and request indexing if appropriate. Google does not guarantee that every submitted page will be indexed.

You publish a carefully researched blog post, add a compelling title, share it on your website, and submit your sitemap. A few days later, you open Google Search Console expecting progress, only to discover that your article is still marked “Discovered currently not indexed.”

It’s frustrating, especially when you’ve spent hours creating something useful. You might wonder whether your website has a technical problem, whether Google dislikes your content, or whether you simply need to wait longer.

The important distinction is that this status concerns crawling, not a final decision about indexing. Google has found the URL but has not yet fetched and processed the page. That makes the troubleshooting process different from fixing a page that Google has already crawled but chosen not to index.

Let’s look at what this status means, why it happens to blog posts, and how to work through the problem without wasting time on repeated indexing requests.

What Does “Discovered currently not indexed” Mean?

Google generally processes web pages through several stages: discovery, crawling, indexing, and potentially showing the page in search results.

Discovery happens when Google learns that a URL exists. It might find the URL through your XML sitemap, a link from another page, or another source. Crawling happens when Googlebot visits the URL and retrieves its content.

When Search Console reports “Discovered currently not indexed,” the URL has been discovered, but Google has not crawled it yet. Google’s official documentation explains that crawling may be postponed when its systems anticipate that crawling could overload the website.

This does not automatically mean your article is poor, your website is penalized, or something is broken. The status is a reason to investigate the circumstances, not a diagnosis by itself.

A useful distinction: Google can know a blog post exists without having read the article.

For the official definition, consult the Page indexing report documentation.

Why Are Your Blog Posts Discovered but Not Indexed?

Several factors can contribute to this status. The most useful starting point is to look for patterns across your website rather than treating every affected URL as an isolated problem.

1. Your Website Is New or Has Limited Crawling History

A recently launched blog may not have an established pattern of crawling. Google needs time to discover its pages, revisit them, and determine which URLs to crawl.

For example, imagine publishing 20 articles on a new website in one week. Google may discover all 20 URLs through your sitemap but crawl only some of them initially.

This does not necessarily indicate a problem. Google explains that most websites should not expect same-day crawling, and discovering a URL does not guarantee immediate crawling or indexing.

What to do: Make sure your important articles are accessible through your website’s navigation and relevant internal links. Allow time for crawling while investigating any persistent issues.

2. Your Website Has Technical or Server Problems

Googlebot needs to access your website reliably. Slow responses, frequent server errors, timeouts, or hosting interruptions can make crawling less efficient.

This is particularly worth investigating when many URLs are affected at once. If your homepage, category pages, and blog posts all show indexing delays, the problem may be broader than an individual article.

Check your hosting logs, server response codes, and website availability. A page returning HTTP 200 is a useful sign, but it does not prove that every technical aspect is correct or that Google will index the page.

What to do: Resolve recurring server errors, ensure important pages load reliably, and verify that Googlebot can access the content without unnecessary redirects or restrictions.

3. Your Blog Posts Have Weak Internal Linking

Publishing an article does not automatically make it easy for Google to discover through your website’s structure.

Suppose you publish an article about choosing running shoes but never link to it from your running guides, category page, or related posts. Google may discover its URL through your sitemap, yet the page remains poorly connected to the rest of your website.

Internal links provide paths to discover pages and help clarify their relationships. Google recommends using crawlable links and ensuring that important pages receive links from other pages on your site.

What to do: Add contextual links from relevant, established articles. Use descriptive anchor text that explains what readers will find when they click.

4. Your Website Publishes Too Many Similar Articles

Content overlap is not necessarily the direct cause of the “Discovered” status, because Google has not yet crawled the affected URL. However, a large collection of near-identical pages can be a warning sign when diagnosing broader crawling and indexing problems.

Imagine a blog publishing separate articles titled “Best Running Shoes for Beginners,” “Top Running Shoes for New Runners,” and “Best Shoes for People Starting Running,” with almost identical recommendations and explanations.

Those articles may serve essentially the same purpose. Rather than publishing more versions of the same information, consider whether one comprehensive article would help readers more.

What to do: Review your existing content before creating new posts. Merge overlapping articles where appropriate, redirect retired URLs when necessary, and give each remaining article a distinct purpose.

5. Your XML Sitemap Is Not Properly Maintained

An XML sitemap tells Google which URLs you consider important enough to include. It can help Google discover new and updated pages, but it does not force Google to crawl or index them.

Common sitemap problems include:

Important blog posts are missing.
The sitemap contains redirected URLs or pages returning errors.
URLs point to noncanonical versions of articles.
The sitemap includes pages you do not want indexed.
The sitemap is inaccessible or incorrectly configured.

What to do: Open your sitemap and confirm that it contains the correct, canonical URLs for your published blog posts. Submit the sitemap in Google Search Console and review whether Google can fetch it successfully.

How to Fix “Discovered currently not indexed” Step by Step

The best approach is to diagnose the issue before making changes. Follow these steps in order, starting with the affected URL and then checking for website-wide patterns.

Step 1: Inspect the Affected URL in Google Search Console

Open Google Search Console and select the correct website property. Enter your blog post’s complete URL into the URL Inspection tool at the top of the interface.

Review the information available about the page, including its indexing status, last crawl details if available, and any reported technical issues.

Pay attention to the distinction between these two statuses:

Discovered currently not indexed: Google knows about the URL but has not crawled it yet.
Crawled – currently not indexed: Google has crawled the URL but has not indexed it at this time.

These statuses require different troubleshooting approaches. For the first, investigate discovery, crawling, server health, and crawl prioritization. For the second, also evaluate content quality, duplication, canonicalization, and indexing directives.

Use the URL Inspection tool to review an individual page.

Step 2: Check Whether the Page Can Be Indexed

Before requesting indexing, confirm that the article is technically eligible to appear in Google Search.

Check the following:

The page returns a successful HTTP response, ideally HTTP 200.
The page is not unintentionally blocked by robots.txt.
The page does not contain a noindex directive.
The canonical tag points to the intended URL.
The page does not redirect to another URL unexpectedly.
The main article content is accessible to Googlebot.

One detail matters here: a robots.txt block and a noindex directive are not interchangeable. Robots.txt controls crawling, while noindex tells search engines not to index a page when they can access and process that directive.

If crawling is blocked, Google may not be able to see a page’s noindex instruction. Fix the underlying configuration rather than adding more directives.

Step 3: Improve Internal Links to the Blog Post

Internal linking is one of the most practical changes you can make.

Start with your website’s homepage, relevant category pages, and existing articles that discuss related subjects. Add a natural link to the affected post wherever it genuinely helps the reader.

For example, if your new article explains how to prune tomato plants, link to it from your existing guides about growing tomatoes, watering vegetable gardens, or preventing common tomato-growing problems.

Avoid adding dozens of irrelevant links simply to make the page look important. The goal is to establish useful connections between related information.

A sensible internal linking structure looks like this:

Main blog category

Organizes related articles

Established related article

Provides a relevant contextual link

New blog post

Receives a clear discovery path

This structure helps readers navigate your content and gives Google additional crawlable paths to the new article.

Step 4: Make the Article Genuinely Useful

Even though content quality is not something you can directly infer from the “Discovered” status alone, it deserves attention when indexing problems affect many posts.

Review your article from a reader’s perspective. Does it answer the question clearly? Does it offer original examples, practical advice, reliable evidence, or insights that are difficult to find in a superficial summary?

For instance, an article about fixing a leaking tap becomes more useful when it explains how to identify the type of leak, which tools are needed, how to shut off the water supply, and when a plumber should be called.

Simply expanding an article from 800 words to 2,000 words will not necessarily improve its value. Length should follow the complexity of the topic, not an arbitrary target.

Google’s guidance on creating helpful, reliable, people-first content is a useful framework for reviewing your work.

Step 5: Check Your Sitemap and Canonical URLs

Confirm that the affected blog post appears in your XML sitemap and that the URL matches the version you intend Google to index.

For example, these URLs may represent different versions of what you consider the same page:

https://example.com/blog-post/
https://www.example.com/blog-post/
http://example.com/blog-post/

Your site should have a consistent URL structure, with redirects and canonical signals configured appropriately. Do not assume that submitting multiple URL variants will accelerate indexing.

Also, avoid including noncanonical URLs, redirected pages, or pages you intentionally want excluded from search results in your sitemap.

Step 6: Request Indexing After Fixing the Issues

Once you’ve checked the page and corrected any problems, return to URL Inspection.

If the page is accessible and eligible for indexing, use Request indexing when the option is available. This asks Google to consider the URL for crawling; it is not a guarantee of immediate crawling or indexing.

Repeatedly clicking the request button without making meaningful changes is unlikely to solve a persistent issue. Google also applies limits to indexing requests.

The better sequence is straightforward: diagnose, fix, request indexing when appropriate, and monitor the result.

Step 7: Monitor Progress Without Making Constant Changes

Check Search Console periodically rather than refreshing the report throughout the day.

Record the affected URLs, the date you made changes, and the status reported during later checks. If your website has server logs available, review them for evidence of Googlebot visits and server errors.

Google explains that most sites should expect crawling to take several days or longer, and there is no universal timeline for indexing. If a URL remains undiscovered by crawling for weeks, investigate the broader pattern instead of repeatedly resubmitting it.

Discovered vs. Crawled vs. Indexed: What’s the Difference?

Understanding these states makes troubleshooting much easier.

Search Console status	What it means	Best next step
Discovered currently not indexed	Google knows the URL but has not crawled it yet	Review links, sitemap, server health, and crawling patterns
Crawled – currently not indexed	Google visited the page but has not indexed it	Review content value, duplication, canonical signals, and directives
Indexed	Google has included the page in its index	Monitor its visibility and performance
Excluded by noindex	Google has received an instruction not to index the page	Remove the directive only if indexing is intended
Page with redirect	The URL redirects to another destination	Check whether the redirect is intentional and inspect the destination

The precise status and reason shown in Search Console should guide your response. A page that has never been crawled needs a different investigation from one that Google has already evaluated.

How Long Does Google Take to Index a Blog Post?

There is no fixed indexing deadline. A new post may be crawled relatively quickly, while another may remain unindexed for days or weeks.

Google’s documentation notes that most sites should not expect same-day crawling. The timing depends on factors such as crawl demand, website availability, URL discovery, and Google’s assessment of which pages to crawl.

Use the following as a practical monitoring framework, not an official Google timetable:

Time since publishing	What to do
First few days	Check the URL, sitemap, internal links, and indexing eligibility
After about one week	Review the status and check for technical or discovery issues
After two to four weeks	Investigate persistent patterns, server logs, site structure, and content overlap
After several weeks or longer	Conduct a broader site audit if important URLs remain unprocessed

These intervals are troubleshooting checkpoints, not guarantees. A technically sound page may still take longer, and waiting alone is not the right response when clear problems exist.

Common Mistakes That Keep Bloggers Stuck

Some actions feel productive but do little to resolve the underlying issue.

Submitting the Same URL Repeatedly

Requesting indexing every day does not force Google to crawl your article. Submit a request after checking the page and correcting relevant issues, then give Google time to process it.

Publishing More Articles Before Fixing Existing Problems

If dozens of articles remain undiscovered, publishing another batch may increase the number of URLs requiring attention without addressing the cause.

Review your current content inventory first. Identify important pages, remove unnecessary duplication, and improve how your existing articles connect to one another.

Assuming Every Blog Post Must Be Indexed

Not every URL needs to appear in Google Search. Search results do not need multiple versions of the same article, thin utility pages, or URLs that provide no distinct value.

Focus on pages that serve a clear purpose for your audience.

Changing the Article’s URL Without a Good Reason

Changing a URL simply because it has not been indexed can introduce unnecessary redirects and disrupt existing links. Keep the URL if it is appropriate, and fix the actual problem instead.

If a URL change is genuinely necessary, implement a suitable permanent redirect and update your internal links and sitemap.

A Practical Checklist for Blog Posts That Are Not Indexed

Use this checklist when diagnosing an affected article.

Indexing troubleshooting checklist

0 of 10

Inspect the URL in Google Search Console

Confirm the page returns HTTP 200

Check robots.txt and noindex directives

Verify the canonical URL

Confirm the article appears in the XML sitemap

Add relevant internal links from existing pages

Review the article for originality and reader value

Check website availability and server errors

Request indexing after resolving relevant issues

Recheck the URL and record any status changes

Reset checklist

Completing this checklist will not guarantee indexing, but it helps rule out common technical and structural problems before you investigate more complex causes.

Frequently Asked Questions

1. Does “Discovered currently not indexed” mean my blog post is rejected by Google?

No. It means Google knows the URL exists but has not crawled it yet. The status alone does not establish that the content has been rejected or that your website has a penalty.

2. Will submitting an XML sitemap guarantee indexing?

No. A sitemap helps Google discover URLs, but Google decides which pages to crawl and index. Make sure your sitemap contains the correct canonical URLs and that the pages are accessible.

3. Should I delete and republish a blog post that is not indexed?

Usually not. First investigate technical accessibility, internal linking, sitemap inclusion, and content quality. Deleting and republishing an unchanged article does not guarantee a different outcome.

4. Can a new website experience this problem?

Yes. New websites may have limited crawling history, and their pages may take time to be crawled. Ensure that important pages are linked internally, accessible, and included in a correctly configured sitemap.

5. What if my blog post changes to “Crawled – currently not indexed”?

That means Google has crawled the page but has not indexed it at that time. Recheck canonicalization and indexing directives, then evaluate whether the article provides enough original, useful information to deserve its own place in search results.

Key Takeaways

Discovered is not the same as indexed. Google knows the URL exists but has not crawled it yet.
Start with the URL Inspection tool to understand the page’s current status.
Check technical accessibility, canonical tags, robots.txt, and noindex directives.
Strengthen internal links so important articles are easy to discover through your website.
Maintain an accurate XML sitemap, but remember that sitemap submission does not guarantee indexing.
Improve thin or repetitive content by adding original insights, practical examples, and meaningful information.
Request indexing after addressing relevant problems, then monitor progress without repeatedly resubmitting unchanged URLs.

Additional Resources

Troubleshoot Crawling Errors: This official guide explains how to investigate crawling delays, server availability, crawl prioritization, and ways to help Google access important pages.