Open Search Console on a site that launched recently and you will usually find a pile of URLs sitting under “Discovered, currently not indexed.” Click one and the crawl section says last crawl: N/A.
That combination confuses people, because the page is in the sitemap, the sitemap was submitted, and Search Console clearly knows the URL exists. It is easy to read as a bug. It is not a bug. It is Google telling you something specific, and it is worth learning to read.
What the status actually means
Google has found the URL and has not fetched it. Not once. It is in a queue, and it has not come up.
The distinction that matters is between this and the status next to it in the same report:
- Discovered, currently not indexed. Google knows the URL exists. It has never downloaded the page. It has no idea what is on it.
- Crawled, currently not indexed. Google downloaded the page, looked at it, and decided not to index it.
Those are completely different problems and they need opposite responses. “Crawled and not indexed” is a judgment about your content: Google read it and was unimpressed. “Discovered and not indexed” is a judgment about your site: Google has not considered the page worth the trip yet.
Improving the writing on a page that has never been fetched will not help you, because nothing has read it. That is the mistake this status causes most often.
Why it happens, in rough order of likelihood
The site is new, or new to Google. Crawling is budgeted against a rough sense of how important and how fresh a site is, built up over time. A domain with no crawl history has none of that. Being slow to crawl a brand new site is reasonable behavior, not a penalty.
Nothing links to the page. A URL that appears only in your sitemap is a URL nothing on the web, including your own site, treats as worth visiting. A sitemap is a suggestion. An internal link is a vote, and it comes from a page Google already crawls, which means it gets seen sooner.
Nothing links to the site. If no other site links to you at all, there is very little pulling a crawler in. This is the honest reason most new small business sites index slowly, and it is not solved by anything technical.
The page looks like a near duplicate of something else. Ten location pages differing by a town name are a common cause. Google can often infer duplication from URL patterns before fetching. This is the same underlying problem described in why ten thin location pages will lose to three good ones.
Crawl budget. Genuinely last, despite being the first thing most articles blame. Google has said plainly that the large majority of sites never need to think about crawl budget. If your site has a few hundred URLs, this is not your problem. If it has fifty thousand because of filtered category pages, it might be, and that is index bloat rather than a crawl budget question in its own right.
What actually moves it
Internal links from pages that already get crawled. This is the highest leverage thing available to you and it costs nothing. If your homepage is crawled regularly, a link from it to a new article is a far stronger signal than adding that article to a sitemap. Link from the pages Google visits to the pages it is ignoring, with descriptive anchor text.
An honest sitemap. A sitemap is a list of URLs you are asking to have indexed. Every URL in it that is set to noindex, redirects, returns an error or duplicates another URL degrades how much the whole file is trusted. Author archives, paginated archives and tag pages nobody should land on are the usual offenders. Take them out.
Time. Unsatisfying and true. On a new domain, indexing arrives in waves over weeks rather than all at once. Resubmitting a sitemap daily does not accelerate it and neither does requesting indexing on the same URL repeatedly.
Something worth fetching. A page that duplicates what is already indexed elsewhere on your site gives a crawler no reason to prioritize it. This is where the “crawled and not indexed” problem and this one meet.
What does not work
Paid indexing services, indexing bots, and anything that promises to force a URL into Google. If forcing indexing were possible for forty dollars, indexing would not mean anything.
Repeatedly hitting Request Indexing. It is a queue, not a lever. Using it once on a genuinely important page is sensible. Using it on fifty is a way to spend an afternoon.
Removing and re-adding a sitemap. Nothing about that changes the decision.
IndexNow, and the thing people get wrong about it
IndexNow lets a site notify search engines directly when a page is published or changed, rather than waiting to be crawled. You publish a key file, and each time content changes your site sends the URL to a shared endpoint.
It genuinely works, and it is worth implementing. One important limitation: Google does not participate. It has been asked about this repeatedly and the answer has not changed. IndexNow reaches Bing, Yandex and several others, but not Google.
So it does not solve the problem this article is about. It is still worth doing, for a reason that has grown considerably: Bing’s index is what several AI assistants retrieve from when they answer questions. Getting into Bing quickly is now a distribution question rather than a search engine ranking question. That connects directly to what AI assistants say about your business, which is downstream of what they can find.
A realistic timeline
For a new domain with no link profile, expect the important pages to be indexed within a few weeks and the long tail to take longer. Some pages will never be indexed, and on a healthy site that is fine. Not every URL deserves to be in a search index, which is a thing worth internalizing before you go hunting for a technical explanation.
What should concern you is a page that has been crawled repeatedly and still is not indexed, or a site where the homepage itself will not index months after launch. Those are real faults. A pile of “discovered” URLs on a two week old site is not.
The one thing to check before you assume it is normal
Make sure the page is actually available to be crawled. In Search Console, use URL Inspection, then Test Live URL. That fetches the page as Google would, right now, and tells you whether it can be crawled and indexed. It is a different question from whether it has been, and it takes ten seconds.
If the live test says the page is available and the report still says discovered, you have a patience problem rather than a technical one. If the live test says it is blocked or noindexed, you have found a real fault, and that is worth understanding properly because crawlers do not all behave the same way and a page that renders fine for you can be empty to them.
Indexing problems are usually diagnosis problems. The report is not the finding, it is the pointer. If you want the actual finding on your own site, that work is the substance of technical SEO, and it is worth having done once properly rather than guessed at repeatedly. You can send me the site and I will tell you which of the causes above you have.
