"Discovered – Currently Not Indexed" — What It Really Means

Short answer: "Discovered – currently not indexed" means Google has found the URL, usually through your sitemap or a link, and has not yet crawled it. It is a statement about crawl priority, not about the page's quality. On a new site with little authority, it is usually caused by publishing more pages than Google is currently willing to crawl. On-page changes do not help, because Google has not looked at the page.

Table of Contents

1. What the Status Means
2. Our Situation
3. What We Ruled Out
4. The Actual Cause
5. What Does Not Help
6. What Does Help
7. Key Takeaways

What the Status Means

Search Console's page indexing report sorts unindexed URLs by reason. Two are often confused.

The difference decides your response. If the page was crawled and rejected, look at the page. If it was never crawled, the page's content cannot be the reason, because Google has not seen it.

Our Situation

Our site was new. We published a large amount at once: documentation, industry pages, comparisons, features, and blog articles, close to two hundred URLs in a short period.

Some weeks later, the page indexing report looked like this:

Zero in the "crawled" row was the important number. Google was not crawling the pages and turning them down. It was not crawling them.

What We Ruled Out

The natural reaction is to assume something is wrong with the pages. We checked the usual suspects, with measurements.

A technical fault

We did find one. A trailing-slash redirect meant our canonical URLs were themselves redirects (the full story). We fixed it, and it was worth fixing. But on inspection it explained only the five canonical-related rows, not the 113. It is tempting to credit a real bug with the whole problem. The numbers did not support that.

Thin content

We counted words per page type. Median length was above 1,400 words for both industry pages and blog articles, and several hundred for documentation pages. Not thin.

Poor internal linking

We built a link graph from the rendered HTML. Every page was reachable within three clicks of the homepage, and there were no orphans.

Duplicate content

A naive comparison suggested documentation pages were about half identical to one another. That turned out to be shared navigation and footer. With that removed, the overlap between similar pages fell to roughly a quarter, which is normal for a set of related guides.

We briefly considered removing documentation pages from the sitemap to concentrate crawling, and decided against it. It would have cost long-tail visits to specific setup guides for a benefit we could not demonstrate.

The Actual Cause

With content, linking, and duplication ruled out, what remained was crawl demand.

Google allocates crawling according to how much it expects a site's pages to matter. A new domain with almost no links pointing to it has given Google little reason to prioritise it. Present such a site with two hundred URLs at once and Google will crawl a few, note the rest, and come back gradually.

So the constraint was not on the site. It was off the site: authority, measured largely by who links to and mentions you.

That is an uncomfortable conclusion, because it means there is nothing to change in the code.

What Does Not Help

• Clicking "Validate fix". It asks Google to recheck a fix. There was nothing fixed to check.
• Rewriting titles and descriptions. Google has not read them.
• Adding more content to the pages. Same reason.
• Resubmitting the sitemap repeatedly.
• Requesting indexing for every URL by hand. It is rate-limited and intended for individual pages.
• Changing sitemap dates to look fresh. This actively harms trust in your sitemap (why).
• Publishing even more pages. It lengthens the queue.

What Does Help

1. Earn links and mentions. This is the real lever. Directories in your field, partner pages, guest articles, community answers, product listings, and anything genuinely worth referencing.
2. Prioritise. Decide which twenty pages matter most and make sure they are the most linked internally, from the homepage and from each other.
3. Publish steadily. A regular cadence of a few pages gives Google a reason to return, where a single bulk release does not.
4. Fix genuine technical issues, even if they are not the main cause. Redirects on canonical URLs, slow responses, and server errors all waste the crawling you do get.
5. Keep the sitemap honest. Accurate last-modified dates and only canonical, indexable URLs.
6. Request indexing for a handful of key pages by hand, not for hundreds.
7. Be patient and watch the trend. The indexed count rising week by week is the sign that it is working.
8. Bring traffic from elsewhere. Pages that people visit and share from other channels gain signals independently of search.

Key Takeaways

• "Discovered" means not yet crawled; the page's content is not the reason.
• Check for and rule out thin content, weak linking, and duplication with real measurements.
• On a new site, the usual cause is low crawl demand from low authority.
• The fix is off-site: links, mentions, and a steady publishing pace.

Conclusion

We spent time looking for something broken, and the honest finding was that nothing on the site was holding it back. Indexing is earned by being a site worth crawling, and that takes time and other people's attention.

The trailing-slash bug we fixed along the way.