Discovered - Currently Not Indexed on a New Domain

You launched a site. The homepage is indexed. Forty other URLs sit in Search Console under Discovered - currently not indexed, and they have been sitting there for three weeks. Every forum thread tells you your content is thin. Most of those threads are wrong.

Google has not read your content. It cannot have an opinion about it yet. That is the entire point of the status, and it changes which fixes actually work.

What does 'Discovered - currently not indexed' mean?

It means Google knows the URL exists and has not crawled it. Google's Page Indexing report documentation defines it as: 'The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl.'

So Googlebot has your URL — from a sitemap, an internal link, or an external link — and made a scheduling decision to not spend a fetch on it. No fetch, no HTML, no evaluation, no index.

Practical consequence: rewriting the page does not help. Adding 800 words does not help. Google has not seen the first version. Open URL Inspection on one of the stuck URLs and look at the crawl date — on a Discovered URL, it is empty.

How is 'discovered' different from 'crawled - not indexed'?

One is a crawl decision, the other is a quality decision, and the fixes do not overlap. Google defines Crawled - currently not indexed as: 'The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.'

Mixing these up is the most expensive mistake on a new site. Owners rewrite forty Discovered pages that Google never read, see no change, and conclude SEO is a scam. The pages were never the problem.

If your stuck URLs really are in the Crawled bucket, that is a different job — see our breakdown of crawled but not indexed pages on service-business sites.

Why won't Google spend a crawl on your new site's pages?

Because crawling costs Google money and your domain has not earned the spend yet. Google's crawl budget guide splits crawling into two halves: crawl capacity limit (how hard Google can hit your server without hurting it) and crawl demand (how much Google wants your URLs at all).

Google names three factors behind crawl demand: perceived inventory, popularity, and staleness. On popularity it is explicit — 'URLs that are more popular on the Internet tend to be crawled more often to keep them fresher in our systems.'

A four-week-old domain with zero external links scores near zero on popularity. Your homepage got crawled because it is the one URL anything points at. The other forty are, from Google's side, unproven URLs on an unproven host. It reschedules them.

The capacity half matters too, and it is the half you control today. Google states: 'If the site responds quickly for a while, the limit goes up, meaning more connections can be used to crawl. If the site slows down or responds with server errors, the limit goes down and Google crawls less.' A 900ms TTFB on shared hosting is a self-inflicted crawl cap.

How do you raise crawl demand on a fresh domain?

Four levers, in the order they actually move the needle. Nothing here is exotic; the mistake is skipping the boring ones and pressing Request Indexing forty times instead.

• Link the stuck URLs from the homepage. Your homepage is the only page with any authority. If a URL is three clicks deep or orphaned (reachable only from the sitemap), it is a low-priority URL to Google. Get every important page within two clicks of the homepage, in real crawlable HTML links, not a JS mega-menu.
• Keep sitemap lastmod honest. Google says it 'uses the <lastmod> value if it's consistently and verifiably (for example by comparing to the last modification of the page) accurate.' If your CMS stamps today's date on all 40 URLs every night, you have taught Google your lastmod is noise. It stops using it.
• Earn three or four real external links. Not directories. A local chamber, a supplier page, a partner, a podcast, a client's 'who built this' link. Popularity is a stated crawl-demand factor, and this is the only lever that touches it.
• Make the server fast and boring. Sub-300ms TTFB, no 5xx, no timeouts under Googlebot's bursts. Capacity rises when the host holds up.

The homepage-linking lever is the one people skip because it feels too dumb to work. It is usually the one that flips the count. If you are not sure which of your pages are orphaned, that falls out of a crawl in any technical pass — see internal linking for service-business sites and our technical SEO service if you want it done for you.

Does a 60-page site have a crawl budget problem?

No. Google's crawl budget guide opens by telling most sites to stop reading: 'If your site doesn't have a large number of pages that change rapidly, or if your pages seem to be crawled the same day that they are published, you don't need to read this guide.' Its own scope examples are large sites at 1 million+ unique pages, and medium sites at 10,000+ with daily changes.

You have 60 URLs. You do not have a crawl budget problem. You have a crawl demand problem — Google is not out of capacity for you, it simply does not want your URLs badly enough yet.

This distinction saves you from a month of wasted work. Nobody needs to prune your 60 pages, tune your robots.txt, or fight faceted-navigation crawl waste. Those are 100,000-URL e-commerce problems being sold to 60-page plumbers.

Why is mass 'Request Indexing' the wrong move?

Because it is rate-limited and it does not compound. Google's recrawl documentation is blunt: 'there's a quota for submitting individual URLs and requesting a recrawl multiple times for the same URL won't get it crawled any faster.'

So the ritual — inspect URL, request indexing, repeat for 40 URLs, repeat again next week — burns an hour a day, exhausts your quota, and leaves the underlying demand signal exactly where it was. Google also tells you what to do at volume instead: submit a sitemap.

And a sitemap is not a command either. Google's sitemap documentation says submitting one 'is merely a hint: it doesn't guarantee that Google will download the sitemap or use the sitemap for crawling URLs on the site.' Same page: 'Google ignores <priority> and <changefreq> values.' If an agency's indexation plan is priority tags and daily changefreq, they are optimizing two fields Google throws away.

Use Request Indexing for what it is good at: one or two genuinely important URLs, once. A new money page. A fixed noindex tag. Not a batch job.

How long should a new domain take to get fully indexed?

Plan on weeks, not days, and judge by trend rather than by date. Google's own line on a submitted URL is that 'crawling can take anywhere from a few days to a few weeks' — and that is for a URL you explicitly asked for, on an established site. A brand-new domain with no external links sits at the slow end of that.

A sane read of the Page Indexing report on a fresh 60-page site:

The number to watch is not 'am I indexed today' — it is whether the Discovered bucket is shrinking week over week. If it is, the machine is turning. If it has been flat for a month, you skipped a lever. Set up the report properly first with our Search Console guide for service businesses, and set expectations on the wider timeline with how long SEO takes to work.

Anyone who promises you full indexation on a date, or guarantees rankings off the back of it, is selling you something Google does not sell them.

What should you do this week?

Three tasks, roughly four hours total, and they cover about 80% of stuck-Discovered cases on a new service-business site.

• Crawl your own site and list every URL that is not reachable from the homepage in two clicks. Add real HTML links until that list is empty.
• Open your sitemap. Check lastmod is a real modification date, not today's date on every row. Fix the generator if it is lying.
• Measure TTFB on a cold request. Over 600ms, move hosting or add caching before you blame Google.

If that does not move the Discovered count in three to four weeks, the problem is external — nobody links to you, so nothing wants to crawl you. That is a link and PR job, not a technical one, and no amount of Request Indexing substitutes for it.

If you would rather someone else diagnose which of the two buckets your URLs are actually in and fix the crawl path, that is exactly what our technical SEO work covers — month to month, no lock-in, no ranking guarantees. Get my free audit and we will tell you which bucket you are in before you spend a dollar.