Short answer: "Discovered, currently not indexed" means Google knows the page exists but hasn't crawled it yet. Google's own explanation is that it wanted to crawl the address but rescheduled, usually because crawling it then might have overloaded the site. On a small, young site the real reason is more often priority: Google hasn't yet decided the page is worth the visit. Rule out the technical causes first, then make the page easier to reach and more worth reading.
This is the second in our series on things that broke on real sites and the rule each one left behind. This one came up on a client's site in October, on pages that really mattered.
"Discovered" is Google saying it knows where you live. It hasn't knocked yet.First, the jargon
Discovered or crawled: not the same problem
Search Console's Pages report lists two statuses that sound alike and mean different things.
- Google has found the address, from your sitemap or a link
- It hasn't read the page yet
- Usually a crawl priority problem
- Fix: make the page easier to reach and give Google a reason to visit
- Google has read the page
- It decided not to add it to the index, for now
- Usually a quality or duplication question
- Fix: make the page more useful, or merge it with a similar one
The two need different fixes, so it's worth knowing which one you're looking at before you change anything. Google's definitions are in its Page indexing report help.
What brokeSix pages, including the contact page
In October, a renovation company in East London had six pages sitting in "Discovered, currently not indexed". They weren't stragglers. The list included the contact page, the projects hub, two individual project pages, the areas hub and the cookies page. Some of the most important pages on the site, and Google hadn't read them.
The tempting conclusion is that something's broken. So we checked that first, one cause at a time:
- All six were listed in the sitemap
- None was blocked by robots.txt
- None carried a noindex tag
- All were linked from other pages. The contact page and projects hub each had 47 internal links pointing at them
One page stood out. A project page had only three internal links, even though a related article mentioned the project by name four times without linking to it once.
What we did: requested indexing in Search Console for five of the six, skipping the cookies page because it wasn't worth spending a request on. Then we turned those four existing mentions in the article into real links. No new copy, just finishing a job the article had half done.
The rule it left: when a page is discovered but not crawled, check the boring causes first, then look at how many links point at it from pages Google already trusts. If you mention a page by name, link to it.
And on our own site
Our own Search Console showed the same thing at the end of October: 20 pages in "Discovered", all of them new pages from the previous few weeks. We left those alone, because a new page waiting a few weeks for a first crawl is normal on a young site.
The more useful list was "Crawled, currently not indexed", with 11 pages. Two were thin, so we expanded them. Two were near-duplicates covering the same ground about AI search, so we merged them into one stronger article and redirected the other. That's the difference between the two statuses in practice: one asks for patience and links, the other asks for a better page.
Check yoursRule out the technical causes first
Most of these take a minute each, using the URL Inspection tool in Search Console.
| Check | Where | What good looks like |
|---|---|---|
| It's in your sitemap | yourdomain.co.uk/sitemap.xml | The exact address is listed, with the same www, https and trailing slash as the page |
| Crawling is allowed | URL Inspection, then "Crawl allowed?" | Yes. Nothing in robots.txt blocking it |
| Indexing is allowed | URL Inspection, or the page source | No noindex tag or header |
| It points at itself | The canonical tag in the page source | The canonical is the page's own address, not another page |
| It's linked from real pages | Your menu, related pages, articles | Several links from pages that are already indexed, not just the footer or sitemap |
| It's not a near-copy | Compare with your similar pages | Clearly different from every other page on the site |
| The server copes | Settings, then Crawl stats, then host status | No recent problems with robots.txt fetching, DNS or server connectivity |
If one of those fails, fix it and you've probably found your answer. If they all pass, it's priority, and that's where the work is.
If everything checks out
- Request indexing for the pages that matter. In URL Inspection, inspect the live page, then request indexing. Spend it on contact, services and key hubs, not cookie policies.
- Link to it from pages Google already likes. A sentence-level link from an indexed article or service page is worth more than another footer link. Search your own site for places you already mention the page and haven't linked it.
- Make it worth the visit. A thin page with a heading and three lines gives Google little reason to come back. Answer the questions a customer would ask on that page.
- Give it a few weeks. New pages on young sites can sit in "Discovered" for a while. Check back, don't refresh daily.
What not to do
- Don't request indexing over and over. Once is enough. Asking again doesn't move you up the queue.
- Don't pay for indexing tools. Anything promising to force pages into Google is, at best, doing what URL Inspection does for free.
- Don't add a pile of thin pages to fix it. More pages on a low-authority site means more pages competing for the same small crawl budget.
- Don't panic about the cookies page. Some pages don't need to be in Google at all.
If your important pages are stuck and you can't see why, our website and visibility audit works through this list, your Search Console data and your internal links, and tells you what to fix first. Or start with why your website isn't showing on Google.
