Discovered - currently not indexed: what it means and what to do, in order

What does "Discovered - currently not indexed" mean?

It means Google has found the URL, through a link or a sitemap, but has not fetched it yet, so the page itself has not been judged. Google typically rescheduled the crawl because it expected the crawl to overload the site, which is why the report shows no last crawl date for these URLs.

Google's help defines the status this way: "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 Google has not read this page. The question is not what is wrong with its content, but why Google does not want, or cannot afford, to fetch it yet: how it found the URL, how much it wants to crawl your site, and how well your server answers. The neighbouring status, "Crawled - currently not indexed", asks a different question.

Is it too early to worry about it?

Often, yes. Google's help says it can take a week or so for Google to start crawling and indexing a new page or site, and that once a URL is known, it can take up to a few weeks before Google crawls some or all of the site. A URL younger than that is not a finding yet.

So put a date next to each affected URL: when it was published, or when it entered the sitemap. Set aside everything younger than a few weeks and diagnose the rest. If nearly all affected URLs are young, the useful work is to make sure each one is linked and listed, then to measure again later.

Size matters too. Google says that if your site has fewer than 500 pages, you probably do not need the Page indexing report: searching Google for your key pages, or inspecting them one by one with the URL Inspection tool, is enough.

The author met this status on a new multilingual site of about 260 pages in four languages (macplus.pro) whose early pages were not indexed.

Which URLs are affected: one template, or the whole site?

Read the affected URLs as groups, not one by one. A cause that sits in a template (tag pages, filtered listings, a language folder, location pages) repeats on every URL built from it, so one fix covers all of them.

1. In the Page indexing report, open the row "Discovered - currently not indexed" and export it. The examples list is limited to 1,000 rows, so on a large site the export is a sample, not the full list.
2. Use the sitemap filter above the chart. "All submitted pages" shows only the URLs of your submitted sitemaps; "Unsubmitted pages only" shows URLs Google found elsewhere. A large unsubmitted share means Google is finding URLs you never listed, such as parameters, sort orders or old paths: look at those first.
3. Group the exported URLs by path pattern: folder, language prefix, URL parameters, pagination. Count each group and compare it with the number of URLs that template has on the site.
4. For each group, check how the same template fares elsewhere. Say 40 of your 45 articles are indexed and 300 of your 310 tag pages are not: the question is about tag pages, not about the site.

Is the cause crawl demand, quality or the server?

Google's definition names one cause, server load. Its crawl budget guide names the other, demand: even when the capacity limit is not reached, "if crawl demand is low, Google will crawl your site less." Quality enters through demand, which Google says varies with a site's size, update frequency, page quality and relevance.

Server capacity. Open the Crawl Stats report, in the property settings, and read Host status. It reports problems with robots.txt availability, DNS resolution and host connectivity, which you can fix. Google says a site with fewer than a thousand pages should not need this report: if Host status shows no problem, look elsewhere.

Crawl demand. The factor Google says you can control most is perceived inventory, the URLs it knows on your site: duplicates and variants you do not want crawled take time from the pages you do want. Popularity is the other: URLs that are more popular on the internet tend to be crawled more often. On a young site, adding pages raises the inventory without raising popularity.

Quality. A page Google has not fetched has not been judged, but its siblings may have been. If the crawled pages of a template end up "Crawled - currently not indexed" or as duplicates, the uncrawled ones of that template are likely to wait. That is an inference from the statuses, not something Search Console states: fix what the crawled pages show.

Google writes its crawl budget guide mainly for sites of over a million pages, sites of over 10,000 pages that change daily, and sites with a large portion of their URLs in this status. The ideas apply to smaller sites; the numbers are Google's rough estimates, not thresholds.

What can the URL Inspection tool and "Request indexing" do?

The URL Inspection tool shows what Google knows about one URL, and "Request indexing" asks Google to crawl it. Neither removes the cause. Google says a request does not guarantee that the page will appear in the index, and there is a daily limit to how many you can submit.

1. Inspect a few URLs from each group, not all of them. For a URL in this status you should see "URL is not on Google" and no Last crawl date.
2. Read the Discovery section. Sitemaps lists the submitted sitemaps that contain the URL; Referring page shows a page Google possibly used to find it. An empty Referring page does not prove that nothing links there: Google says the information may not be available to the tool.
3. Run "Test live URL" to check that Google can fetch the page and is allowed to index it. The live test does not check sitemaps or referring pages, and each property has a daily limit of live inspections.
4. Then, only for the pages that matter most, click "Request indexing". The page goes through a quick check, and you cannot request indexing if the live test finds it non-indexable. On a brand-new site, Google's help suggests requesting indexing of the homepage first.

What it cannot do: Google says there is a quota for submitting individual URLs, that requesting a recrawl of the same URL several times won't get it crawled any faster, and that a request does not guarantee inclusion "instantly or even at all". For many URLs, Google points to a sitemap with accurate lastmod dates instead.

Which fixes help: sitemaps, internal links, IndexNow?

The fixes that help change what Google knows about your site: a sitemap that lists only the pages you want indexed, links from pages Google already crawls, and fewer URLs you do not want crawled. IndexNow reaches Bing and the other engines that take part in it, not Google.

Sitemap hygiene. List only canonical URLs that answer 200 and that you want in search. Keep lastmod honest: Google uses it only when it is consistently and verifiably accurate, and ignores priority and changefreq. One sitemap per template lets the "Specific sitemap URL" filter show the indexation of each template separately.

Internal links. Link each affected page from pages Google already crawls and indexes, in the body of the page, with plain <a href> links: Google says most links in other formats won't be parsed. A page reachable only from the sitemap, or only through a menu built by a script, has nothing else to vouch for it.

Fewer unwanted URLs. Stop linking to parameter, sort and internal-search URLs that should not exist on their own, and keep them out of the sitemap.

IndexNow notifies the engines that take part in it. On 15 October 2026, indexnow.org listed Bing, Naver, Seznam.cz, Yandex and Yep among them, and not Google. Each engine still decides for itself what to index.

The Indexing API is not a shortcut either. Google says it can only be used for pages with JobPosting or BroadcastEvent embedded in a VideoObject. Some guides suggest it for ordinary pages; that is outside its stated use.

• Link Weaver: a skill that rebuilds your internal link graph, finds orphan and weakly linked pages, then drafts the links to add

Can Claude or another AI tool diagnose "Discovered - currently not indexed"?

Partly. No AI assistant has its own view of Google's index or of its reasons: it sees what Search Console gives you, which is labels, not reasons. Claude can read your Page indexing export, group the URLs, fetch your pages to test the technical causes and rank the fixes. Whether Google then crawls stays Google's decision.

Asking a chat assistant "why isn't my page indexed?" with only a URL gets you a guess about one page. The useful input is the export of this status, as Search Console downloads it, plus your sitemap. With those, the work above (age, groups, classes, checks) can be done by hand or handed to Claude.

• Index Doctor: reads the Page indexing export in six interface languages, marks pages too recent as too early to judge, and ranks fixes by template
• Site X-Ray: crawls the site for technical causes; it sees the site, not Google, so read it next to the export
• Pages with impressions but no clicks: once pages are indexed, the next question is often why they are shown but not clicked

These skills are part of SEO Skills by PENRA. None of them can make Google index a page; they shorten the reading and the checking.