{"id":247,"date":"2026-07-11T21:55:03","date_gmt":"2026-07-11T12:55:03","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/discovered-currently-not-indexed\/"},"modified":"2026-11-15T18:46:51","modified_gmt":"2026-11-15T09:46:51","slug":"discovered-currently-not-indexed","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/discovered-currently-not-indexed\/","title":{"rendered":"Discovered &#8211; currently not indexed"},"content":{"rendered":"<h2 class=\"wp-block-heading\">What this status means<\/h2>\n<p class=\"wp-block-paragraph\">&#8216;Discovered &#8211; currently not indexed&#8217; means Google knows a page URL exists but has not yet visited (crawled) that page. The short answer: it is normal for a few freshly published pages to sit in this status for a while. You only need to dig into the cause when many older pages stay stuck here for a long time.<\/p>\n<p class=\"wp-block-paragraph\">This status appears in Search Console&#8217;s <a href=\"\/en\/seo-glossary\/page-indexing-report\/\">Page indexing report<\/a>. Google&#8217;s official documentation defines it as &#8220;The page was found by Google, but not crawled yet.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a> In other words, Google has only learned that the URL exists, through links on other pages or a sitemap, and has not read the page&#8217;s content yet.<\/p>\n<h2 class=\"wp-block-heading\">The gap between the official explanation and field data<\/h2>\n<p class=\"wp-block-paragraph\">Google&#8217;s official documentation and field SEOs disagree on the cause. Google sees it as crawl rescheduling to avoid server load. Practitioners point out that sites with fast servers get stuck in the same status, and they see &#8216;crawl demand&#8217; and content quality as the real bottleneck.<\/p>\n<figure class=\"wp-block-table jt-verdict\"><table><tbody><tr><th>Google&#8217;s official position<\/th><td>It describes the typical cause as &#8220;Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl.&#8221; In other words, it frames this as a crawl scheduling issue meant to protect the server. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/td><\/tr><tr><th>Expert diagnosis<\/th><td>Sites with fast servers get stuck in the same status. Onely explains that the real bottleneck is not server capacity but &#8216;crawl demand,&#8217; and that this status is often tied to content quality problems across the whole site. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.onely.com\/blog\/how-to-fix-discovered-currently-not-indexed-in-google-search-console\/\" target=\"_blank\" rel=\"noopener\">Onely (measured)<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n<p class=\"wp-block-paragraph\">The difference comes down to perspective. The official documentation records the reason the crawler gave at that moment (postponing the crawl to protect the server). Field data observes results across many sites and finds that server capacity is rarely the real obstacle. The practical call is simple. If your server responds quickly but pages keep staying in &#8216;Discovered,&#8217; read it as a signal about internal links and content quality, not a hosting problem.<\/p>\n<h2 class=\"wp-block-heading\">How it differs from &#8216;Crawled &#8211; currently not indexed&#8217;<\/h2>\n<p class=\"wp-block-paragraph\">It is often confused with the similarly named <a href=\"\/en\/seo-glossary\/crawled-currently-not-indexed\/\">&#8216;Crawled &#8211; currently not indexed&#8217;<\/a>, but the two are at different stages. Google&#8217;s official documentation describes the latter as &#8220;The page was crawled by Google but not indexed. It may or may not be indexed in the future.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a> Side by side, the two statuses look like this.<\/p>\n<figure class=\"wp-block-table\"><table><thead><tr><th>Item<\/th><th>Discovered &#8211; currently not indexed<\/th><th>Crawled &#8211; currently not indexed<\/th><\/tr><\/thead><tbody><tr><td>Crawled?<\/td><td>Not crawled yet<\/td><td>Crawled<\/td><\/tr><tr><td>What Google knows<\/td><td>Only that the URL exists<\/td><td>The page content as well<\/td><\/tr><tr><td>Main background per official docs<\/td><td>Crawl rescheduled over concern about overloading the site<\/td><td>Indexing decision put on hold after the crawl<\/td><\/tr><tr><td>Bottleneck<\/td><td>Crawling stage<\/td><td>Indexing (quality evaluation) stage<\/td><\/tr><\/tbody><\/table><\/figure>\n<p class=\"wp-block-paragraph\">To sum up, &#8216;Discovered&#8217; is a crawl queue problem, and &#8216;Crawled&#8217; is an indexing decision made after Google has seen the content. Causes and fixes differ, so the first step is to tell the two statuses apart when reading the report.<\/p>\n<h2 class=\"wp-block-heading\">How it relates to crawl budget<\/h2>\n<p class=\"wp-block-paragraph\">Google defines <a href=\"\/en\/seo-glossary\/crawl-budget\/\">crawl budget<\/a> as &#8220;the set of URLs that Google can and wants to crawl.&#8221; It explains that crawl budget is determined by two elements: the &#8216;crawl capacity limit,&#8217; meaning how much Google can crawl without burdening the server, and &#8216;crawl demand,&#8217; which depends on site size, update frequency and popularity. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/large-site-managing-crawl-budget?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> The &#8216;overload&#8217; in the definition of &#8216;Discovered&#8217; ties directly to this crawl capacity limit.<\/p>\n<p class=\"wp-block-paragraph\">However, Google limits its crawl budget guide to large sites with 1 million or more unique pages whose content changes about once a week, or sites with 10,000 or more pages whose content changes daily. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/large-site-managing-crawl-budget?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> Ahrefs quotes Google&#8217;s Gary Illyes as saying that &#8220;90% of websites don&#8217;t need to worry about crawl budget.&#8221; <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/discovered-currently-not-indexed\/\" target=\"_blank\" rel=\"noopener\">Ahrefs (measured)<\/a> For a typical site with hundreds to thousands of pages, it makes more sense to look for the cause in internal links and content before crawl budget.<\/p>\n<h2 class=\"wp-block-heading\">How to respond<\/h2>\n<h3 class=\"wp-block-heading\">When no action is needed<\/h3>\n<p class=\"wp-block-paragraph\">When the list includes a few recently published pages. Google adjusting its crawl schedule is normal behavior, and crawling and indexing usually happen over time. Google&#8217;s official documentation also states plainly, &#8220;you shouldn&#8217;t expect every URL on your site to be indexed.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/p>\n<h3 class=\"wp-block-heading\">When action is needed<\/h3>\n<ul class=\"wp-block-list\"><li>If only a few important pages are affected, request indexing in the URL Inspection tool. Note that Google states &#8220;submitting a request does not guarantee that your page will appear in the Google index.&#8221; There is also a daily submission limit, so for many pages it recommends submitting a sitemap. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/li>\n<li>Strengthen internal links pointing to the page. Ahrefs explains that Google may treat pages with few or no internal links as unimportant, and recommends standard HTML anchor tags rather than JavaScript links. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/discovered-currently-not-indexed\/\" target=\"_blank\" rel=\"noopener\">Ahrefs (measured)<\/a><\/li>\n<li>Review content quality across the whole site, not page by page. Onely explains that when a site has many thin or duplicate pages, Google lowers crawl demand for the entire domain, and new pages following the same pattern inherit that distrust. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.onely.com\/blog\/how-to-fix-discovered-currently-not-indexed-in-google-search-console\/\" target=\"_blank\" rel=\"noopener\">Onely (measured)<\/a><\/li>\n<li>For a large site, improve crawl efficiency as Google&#8217;s crawl budget guide suggests: consolidate duplicate URLs, make pages load more efficiently and add server resources. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/large-site-managing-crawl-budget?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><\/ul>\n<h2 class=\"wp-block-heading\">References<\/h2>\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">Page indexing report &#8211; Google Search Console Help<\/a><\/li>\n<li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/large-site-managing-crawl-budget?hl=ko\" target=\"_blank\" rel=\"noopener\">Crawl budget optimization (Large site owner&#8217;s guide to managing your crawl budget) &#8211; Google Search Central<\/a><\/li>\n<li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289?hl=ko\" target=\"_blank\" rel=\"noopener\">URL Inspection tool &#8211; Google Search Console Help<\/a><\/li>\n<li><a href=\"https:\/\/ahrefs.com\/blog\/discovered-currently-not-indexed\/\" target=\"_blank\" rel=\"noopener\">How to Fix &#8220;Discovered &#8211; currently not indexed&#8221; &#8211; Ahrefs Blog<\/a><\/li>\n<li><a href=\"https:\/\/www.onely.com\/blog\/how-to-fix-discovered-currently-not-indexed-in-google-search-console\/\" target=\"_blank\" rel=\"noopener\">How to Fix &#8220;Discovered &#8211; Currently Not Indexed&#8221; in GSC &#8211; Onely<\/a><\/li><\/ul>","protected":false},"excerpt":{"rendered":"<p>&#8216;Discovered &#8211; currently not indexed&#8217; means Google knows a page URL exists but has not crawled it yet. Google&#8217;s official documentation says the usual reason is that the crawl was rescheduled to avoid overloading the site. Field data, however, points to &#8216;crawl demand&#8217; and content quality as the real bottleneck, since sites with fast servers get stuck in the same status. A few new pages sitting here briefly is normal; only check internal links and quality when many older pages stay stuck for a long time.<\/p>\n","protected":false},"template":"","glossary_categories":[17],"class_list":["post-247","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-search-console"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/247","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/247\/revisions"}],"predecessor-version":[{"id":2332,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/247\/revisions\/2332"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=247"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}