Fixing 'Discovered – currently not indexed' on a new site
"Discovered – currently not indexed" is the status I get asked about most on new domains. It is not a penalty and it is rarely a technical bug. It is Google telling you it knows your URL exists but has chosen not to spend a crawl on it yet. The fix is about earning that crawl, not forcing it.
I have cleared this status across several of my own sites and client builds, and the pattern is consistent: the URL is queued, the schedulers deprioritise it, and the page sits in limbo until something changes the cost-benefit calculation Google makes about crawling you. Below is how I diagnose it and the checklist I actually run.
What "Discovered – currently not indexed" actually means
In Google Search Console, this status lives in the Pages report under "Why pages aren't indexed". It means Googlebot has found the URL — usually through your sitemap or an internal link — but has not yet crawled it. No content has been fetched, so it cannot be rendered, evaluated, or indexed. This is distinct from "Crawled – currently not indexed", where Google did fetch the page and then decided the content was not worth indexing. Discovered-not-crawled is a step earlier in the pipeline, and it is almost always a prioritisation decision rather than a quality rejection.
The key mental model: Google does not crawl every URL it knows about. It maintains a queue and assigns each URL a priority. New domains with little authority sit low in that queue, so their URLs can be "discovered" for weeks before a crawler arrives.
Why it happens
In my experience the cause is one or more of these, in rough order of how often I see it:
Low site authority on a new domain. This is the dominant reason. Google allocates crawl effort roughly in proportion to how important it thinks a site is. A brand-new domain with no inbound links has almost no signal, so the scheduler treats its URLs as low value and defers them. Crawl budget is not really the constraint for small sites — interest is. Google simply has not been given a reason to prioritise you.
Thin, duplicate, or templated content. If the URLs that do get crawled turn out to be shallow or near-identical to each other, Google learns to expect low value from the rest and slows discovery of new pages. Programmatic pages and boilerplate category pages are common offenders.
Weak internal linking. URLs that are only reachable from the sitemap, or buried many clicks deep, read as unimportant. A page with no internal links pointing to it is effectively orphaned, and orphaned URLs are the first to be deprioritised.
Slow or unreliable server responses. If your server is slow to respond or returns intermittent 5xx errors, Google throttles its crawl rate to avoid overloading you. A sluggish origin directly suppresses how aggressively new URLs get fetched.
How to diagnose it
Before changing anything, confirm what you are dealing with. I run three checks.
URL Inspection. Paste the affected URL into the inspection tool in Search Console. Confirm the status is "Discovered – currently not indexed", check that the user-declared and Google-selected canonicals agree, and run "Test live URL" to prove the page returns a clean 200 and renders properly. If the live test renders fine but the indexed status is stuck, you have confirmed it is a prioritisation problem, not a rendering or canonical one.
The Pages report. Open the report and click into this specific status to see how many URLs are affected and which ones. If it is one or two pages, treat them individually. If it is hundreds, you have a structural problem — usually content quality or internal linking at scale — and patching single URLs will not move the needle.
Server logs. This is the check most people skip and it is the most decisive. Filter your access logs for Googlebot hits to the affected paths. If Googlebot has genuinely never requested the URL, that confirms the discovery-without-crawl story. Logs also surface slow response times and error spikes that throttle crawling in the first place.
The fix checklist
The order matters here. Requesting indexing first, before you have given Google a reason to value the page, is the most common mistake and it rarely sticks. Earn the crawl, then ask for it.
1. Earn external links to lift authority. This is the lever with the biggest effect on new domains. Even a handful of relevant, genuine inbound links raises the priority Google assigns to your whole site and pulls queued URLs forward. Without this, everything else is marginal.
2. Strengthen internal linking to the orphaned URLs. Add contextual links from your strongest, most-crawled pages — your homepage, hub pages, and popular posts — directly to the stuck URLs. Keep them within a few clicks of the homepage and make sure they sit in the main navigation or a related-content block, not just the sitemap.
3. Improve content depth and uniqueness. Make each affected page substantially more useful and clearly different from your other pages. Consolidate thin or overlapping pages rather than leaving a dozen weak ones competing for the same crawl. Quality is what convinces Google the next crawl will be worth its time.
4. Ensure fast 200 responses and clean sitemaps. Fix any slow responses or intermittent errors so crawling is not throttled. Confirm every URL in your sitemap returns a 200, is canonical to itself, and is not blocked by robots.txt. Remove non-canonical, redirected, or 404 URLs from the sitemap so Google is not wasting attention on noise.
5. Then Request Indexing. Once the page genuinely deserves the crawl, use URL Inspection to request indexing. This nudges the page up the queue. Do it once per important URL — repeatedly resubmitting the same URL does nothing and can look like spam. For larger batches, lean on a fresh, accurate sitemap and let authority do the work.
Realistic expectations on timing
This is where I set expectations honestly. On a brand-new domain, even after doing everything right, indexing can take anywhere from a few days to several weeks. A single high-value page with a Request Indexing nudge often gets crawled within days. Site-wide recovery, where hundreds of URLs are stuck, tracks the slow accumulation of authority and can take one to three months to fully resolve. The status clearing in stages — a trickle of pages moving to "Indexed" each week — is the normal, healthy signal that your fixes are working.
The takeaway I leave clients with: "Discovered – currently not indexed" is Google deferring a decision, not refusing one. Give it authority, a clear internal path, genuine content, and a fast response, and the crawl follows. If you want more insights on technical SEO, read the rest of my case notes, learn a bit about Luke, or see the projects where I have put this into practice.
Where this fits in my work
Diagnosing and fixing indexation problems like this is core to the technical-SEO work I ship, not just advise on. If a stuck site is costing you traffic, request my technical SEO audits and optimisation, or get in touch about your site. Related reading: Technical SEO that actually moves revenue and Topic clusters and internal linking.