Add to Preferred Sources
Understanding what causes discovered currently not indexed in Google Search Console — and what it means for your South African SEO performance — starts with what the status reports: Google found the URL, usually through your XML sitemap or an internal link, but has not fetched it yet. Nothing on that page has been read or judged, so rewriting its copy is not the lever. What decides whether the fetch happens is your server's crawl capacity and Google's demand for crawling your site — and site-level quality sits inside that second half.
Google's own documentation confirms the mechanism: "Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl." That reschedule becomes indefinite when the underlying conditions do not change — and on South African sites, many on shared hosting with load-shedding interruptions, pages discovered not indexed for capacity reasons are more common than global guides assume. For the wider GSC picture, see the guide on how to improve website indexation.
Quick Answer
What causes discovered currently not indexed? Google has found the URL but has not fetched it yet, and according to Google's crawl budget documentation the cause sits in one of two halves: crawl capacity — what your server can serve without being overloaded — or crawl demand, how much Google wants to crawl your site at all. Demand is where quality enters: the same documentation says crawling resources are allocated to a site by factoring in popularity, overall user value, content uniqueness and serving capacity. The queued page's own copy has not been judged — but site-wide quality, a pruned URL inventory and stronger internal links are what move crawl demand.
On This Page
What Causes Discovered Currently Not Indexed
How It Differs from Crawled — Currently Not Indexed
Diagnosing Your Situation: Three Hypotheses
Five Specific Triggers to Check
Why South African Websites Are Especially Affected
Pages stuck in Google's discovery queue?
Send us your Google Search Console Page Indexing report and we will identify whether you have a crawl capacity or crawl demand problem — and what to fix first.
Get a Free Indexation AuditWhat Causes Discovered Currently Not Indexed in Google Search Console
The "Discovered — currently not indexed" status means a URL sits in Google's queue with no fetch behind it, which is a scheduling outcome rather than a verdict on the page. According to Google's official crawl budget documentation, crawl budget is the set of URLs Google both can and wants to crawl, and it has two halves: the crawl capacity limit (what your server can serve without degrading) and crawl demand (how much Google wants to crawl your site). Crawling can stay low on demand grounds even when your server has capacity to spare.
Crawl capacity is the rate at which Googlebot can fetch pages without overloading your server. When response times lengthen or 5xx errors appear, the limit goes down — fewer pages get fetched per day, and pages already in the discovered queue fall further back.
Crawl demand is how much Google wants to crawl your site and the URLs on it. According to Google's crawl budget documentation, demand is shaped by popularity, staleness, and perceived inventory — where duplicate or unimportant URLs waste a lot of Google's crawling time on your site. That documentation answers "how do I get more crawl budget?" in two ways: add serving capacity, and improve content quality, because crawling resources are allocated to each site by factoring in popularity, overall user value, content uniqueness and serving capacity.
That second answer is the part most guides drop. A URL sitting at "Discovered — currently not indexed" has not had its own content assessed — but the quality of the site around it is an input to whether the fetch is ever scheduled. A page reachable only from your sitemap has near-zero demand signal, and a site whose inventory is largely thin, duplicated or auto-generated gives Google less reason to raise crawl demand for any of it.
The Most Important Thing to Understand
Rewriting the copy on a page carrying the discovered currently not indexed status will not, by itself, get that page crawled, because Google has not read it. Site-level quality is a separate lever and a real one: Google's crawl budget documentation ties the crawling resources a site receives to popularity, overall user value and content uniqueness, so pruning low-value URLs and raising the standard of what you publish is one of the main influences on whether the queue clears.
The Key Difference Between These Two GSC Coverage Statuses
"Discovered — currently not indexed" and "Crawled — currently not indexed" describe two different points in the pipeline: the first means Google has not fetched the URL at all, the second means Google fetched the page, assessed it, and declined to index it. Confusing them is the most common diagnosis error in technical SEO audits, because only the second is a verdict on that page's own content. Site-wide quality touches both — one through indexing decisions, the other through crawl demand.
| GSC Status | What it means | Last crawl date in URL Inspection | Root cause | Fix direction |
|---|---|---|---|---|
| Discovered — currently not indexed | Google found the URL but has not yet fetched it | Empty — no crawl has happened | Crawl capacity, or crawl demand (link support plus site-level quality) | Server speed, internal links, pruning low-value URLs, raising site-wide quality |
| Crawled — currently not indexed | Google fetched the page but did not add it to the index at that point | Populated — Google visited the page | Several distinct causes: canonical selection against a near-duplicate, the page's own value, site-level quality, filter or parameter URLs, or a page too new to have link support | Diagnose which cause applies before acting — consolidation and canonicalisation resolve it more often than rewriting the page |
The URL Inspection Tool is the fastest diagnostic for any Google Search Console discovered not indexed case: open the affected URL and read the "Last crawl" field. Empty means a "Discovered" issue — scheduling and access. A date means Google visited and judged that specific page — a content problem, covered in our guide on how to improve crawlability and indexation.
Diagnosing Your Situation: Capacity, Link Support or Site Quality
Diagnosing a "Discovered — currently not indexed" backlog means separating three hypotheses before you change anything: constrained crawl capacity, low crawl demand from weak link support, and low crawl demand from a URL inventory or content standard that gives Google little reason to crawl deeper. A site with 80 pages and five affected URLs is far more likely to be a demand problem; a WooCommerce retailer with 15,000 parameterised variants is usually the reverse. They often coexist, so run the check before acting on the guess.
| Situation | Leading hypothesis | First check | First fix |
|---|---|---|---|
| Small site (<500 pages), few URLs affected | Low crawl demand — pages lack link signals | Count internal links to affected pages | Add contextual internal links from high-traffic pages |
| Any size — affected URLs only appear in sitemap, no internal links | Orphaned pages — no demand signal at all | Crawl the site; confirm zero inbound internal links | Link affected pages from relevant content, or remove them from the sitemap if they have no SEO value |
| Medium to large site with a large and growing affected count | Crawl budget dilution from low-value URLs | GSC Crawl Stats: check crawl rate trend and response times | Block parameter variants, faceted navigation, and internal search URLs via robots.txt |
| Any site — Crawl Stats showing rising average response time or 5xx errors | Server capacity — Googlebot throttling | GSC Crawl Stats: server response time and error rate | Improve hosting, enable page caching, fix redirect chains |
| New domain (<6 months), few backlinks | Low domain authority = low overall crawl demand | GSC Links report: total inbound links | Build topical authority, earn backlinks to establish crawl cadence |
| Large share of already-indexed pages are thin, duplicated or auto-generated | Low crawl demand from site-level quality and inventory value | Sample 20 indexed URLs: are they distinct, useful pages a reader would want? | Consolidate or remove low-value pages; improve the pages Google already fetches |
Each row is a hypothesis, not a verdict. The companion guide on crawl budget explains the mechanics; the orphan pages guide covers finding the URLs that sit structurally isolated from the rest of your site.
Five Specific Triggers That Keep Pages Stuck in the Crawl Queue
Five technical conditions account for most "Discovered — currently not indexed" backlogs on South African websites: slow server response, redirect chains, URL bloat, pages with no internal links, and weak site-level quality and authority signals — the first two on the capacity side, the rest on the demand side.
1. Slow Server Response Time
Googlebot monitors Time to First Byte on every request, and when response times lengthen or 5xx errors appear the crawl capacity limit goes down: fewer discoveries get fetched and queued pages wait longer. Check the trend under Settings → Crawl Stats.
2. Redirect Chains on Internal Links
Google's crawl budget documentation tells site owners to avoid long redirect chains, which it says have a negative effect on crawling. Practitioners report that each redirect hop consumes a separate crawl slot, so a link that redirects twice uses three fetches where one would do. Point internal links directly at the final canonical URL.
3. URL Bloat from Faceted Navigation or Parameters
E-commerce and directory sites generate thousands of URL variants through filtering — colour, size, price, location. According to Google's crawl budget documentation, duplicate or unwanted URLs waste a lot of crawling time, and if too much of it goes on URLs Google should not be crawling, its crawlers might not explore the rest of the site. On a WooCommerce site, an unblocked filter layer is often the single largest driver of "Discovered — currently not indexed" for core pages.
4. Pages With No Internal Links (Orphan Pages)
A URL submitted in a sitemap with no internal links carries almost no crawl demand signal: the sitemap says the page exists, nothing else says it is worth fetching. Google documents link extraction from known pages as a main route to new URLs, so pages buried deep or linked only from a generated sitemap are slowest to be reached. The guide on finding orphan pages shows how to identify and fix this systematically.
5. Weak Site-Level Quality and Authority Signals
Crawl demand for a domain is partly determined by its popularity and the value of what it publishes. According to Google's crawl budget documentation, the crawling resources allocated to a site factor in popularity, overall user value, content uniqueness and serving capacity — so a newer SA business site with few inbound links and a long tail of thin pages carries low crawl demand across the board, not only on the affected URLs. The response is not to rewrite the queued page but to raise the standard of what you publish, consolidate duplicates and build topical authority.
Check This Before Anything Else
Before requesting re-indexing through the URL Inspection Tool, open GSC's Crawl Stats report (Settings → Crawl Stats). If average server response time is trending high, or 5xx errors are consistent, fix the server first — requesting indexing on a throttled site achieves very little.
Fixing the Issue: Server, Links, and URL Architecture in Priority Order
Fixing a "Discovered — currently not indexed" backlog runs from site-wide constraints down to individual URLs: server capacity first, then the URL inventory and quality that suppress crawl demand, then link support for the specific pages you care about. To fix discovered currently not indexed pages, start at the top of that order rather than with the page's own copy — the quality work that counts here is aimed at the site's inventory. If you want an outside view of which URLs are dragging down crawl demand, our technical SEO services begin with a free audit before any monthly retainer is agreed.
Step 1: Audit Your Crawl Stats Report
In GSC, go to Settings → Crawl Stats and review average server response time and the breakdown of responses by type. Response times trending upward, or a meaningful share of 5xx errors, mean your hosting is constraining the crawl — fix that first. Talk to your host, enable page caching (LiteSpeed Cache, WP Rocket, or equivalent), and check whether shared hosting is limiting TTFB at peak times.
Step 2: Clean Your XML Sitemap
Your sitemap should contain only canonical, indexable pages returning HTTP 200 — remove anything that redirects, errors or carries a noindex tag. A sitemap full of soft-404s and blocked pages is a weaker crawl priority signal, and Screaming Frog audits one against live URL responses in a single pass.
Step 3: Block Low-Value URLs via robots.txt
Identify the URL patterns consuming crawl budget without delivering indexable value — session parameters, filter combinations, internal search results, deep pagination — and disallow them in robots.txt. On WooCommerce that usually means query-string variants from filter plugins; on WordPress, /?s= and /author/ are common quick wins. Blocking is the fast half. The slower half is consolidating or removing the thin and near-duplicate pages you publish, because that is what lifts the site-level quality signals behind crawl demand.
Step 4: Fix Redirect Chains
Crawl your site with a tool such as Screaming Frog and find every internal link pointing at a redirecting URL. Fixing them is worth the effort because each redirect in a chain consumes a crawl slot, and Google's crawl budget documentation lists long redirect chains as having a negative effect on crawling. Point those links straight at the final canonical destination — chains cluster on sites that changed URL structure without updating internal links, a process covered in the crawlability improvement guide.
Step 5: Add Internal Links to Affected Pages
For each affected page, find the topically related pages you already have and add a contextual internal link in body content, not navigation. Practitioners report that links placed on the most frequently crawled pages — the homepage, main category pages, most-linked posts — surface a queued URL fastest, so start there rather than with a footer or sidebar block.
Step 6: Request Indexing for Priority Pages
After the structural fixes, request indexing for a small number of your most important affected pages rather than large batches. Submission does not raise your crawl capacity; it signals priority on specific URLs once the underlying issues are fixed. Allow several weeks for the status to update — crawl schedules vary by site.
Not sure which fix applies to your site?
Tell us your GSC coverage numbers — total discovered pages, total indexed pages, and your site size — and we will advise on which lever to pull first for your specific situation.
Get a Free Technical ReviewWhy South African Websites Are Especially Affected
South African websites carry three local conditions that compound the "Discovered — currently not indexed" problem beyond what global guides address: shared hosting that degrades time to first byte, load-shedding that interrupts availability, and WooCommerce URL architecture that inflates the crawlable inventory.
Shared hosting and TTFB. Most South African SME websites run on shared hosting, where CPU, memory and database connections are split among hundreds of co-tenants and TTFB climbs at peak times. Google's crawl budget documentation is explicit that slower response times lower the crawl capacity limit, so hosting that degrades under normal load is a structural crawl problem. Moving to a VPS, or configuring LiteSpeed Cache properly where you are, is often the highest-leverage fix.
Load-shedding and server availability. Scheduled outages cause intermittent downtime and 5xx spikes where a host's UPS and generator capacity does not cover the full stage, and Google's documentation is clear that 5xx responses lower the crawl capacity limit. Practitioners working with SA websites report that crawl rate in Crawl Stats dips after extended load-shedding stages, though that is observed correlation rather than a platform-confirmed mechanism. If your host is not load-shedding resilient, the fix is on their side.
WooCommerce URL architecture. WordPress with WooCommerce is the dominant e-commerce stack among South African retailers, and without deliberate robots.txt configuration it generates large numbers of URL variants through attribute filtering, sorting parameters and cart flows — consuming crawl budget on sites without the demand to absorb it. Block parameter-driven filter URLs and audit your crawl depth so important pages are not buried.
Why South African Businesses Choose Growth Pulse Media
Technical SEO problems like "Discovered — currently not indexed" are rarely isolated: they follow upstream decisions about architecture, hosting and URL structure that compound over time. Growth Pulse Media's approach to SEO in South Africa starts with a technical audit — crawl stats, internal link graph, sitemap health, server performance — before page-level content work. Google has not fetched these particular pages, so rewriting them changes nothing on its own; the site-wide quality and inventory work that does move crawl demand pays off once the crawl path is clear.
We work with a limited number of clients at a time, so the person who scopes your audit is the person who executes it, and all work is in-house. Recommendations are specific to your URL architecture, hosting environment and South African audience. For realistic timelines after technical fixes, the guide on how long SEO takes in South Africa sets honest expectations.
Who This Fix Is Not For
Sites where the affected URLs are intentionally low-value. If the affected pages are filtered product variants, auto-generated location permutations or internal search results, the status is correct behaviour. Block them in robots.txt and send the crawl budget to pages that deserve a place in the index.
Sites expecting bulk URL submission to solve the problem. Submitting 200 URLs through "Request Indexing" does not raise your crawl capacity, and if the structural cause — slow server, URL bloat, orphaned pages, weak site quality — is untouched, it makes no lasting difference. Submission is the final signal, not the solution.
Very new domains expecting immediate full indexation. A newer domain with limited backlinks has lower crawl demand, so some pages sitting at "Discovered — currently not indexed" is expected rather than alarming. The priority is authority through content and links, not technical interventions designed for large sites under crawl budget pressure.
Sites wanting to add pages faster than authority can sustain. Publishing into a domain whose crawl rate cannot keep pace grows the discovered queue faster than it clears, and thin volume makes it worse by pulling site-level quality signals down. Earn crawl demand before scaling page production.
Ready to clear your indexation backlog?
Share your GSC Page Indexing data and we will diagnose the specific cause — crawl capacity, demand, or architecture — and give you a prioritised fix list at no cost.
Get Your Free GSC AuditFrequently Asked Questions
What does "discovered currently not indexed" mean in Google Search Console?
It means Google has found your URL — through a sitemap entry or an internal link — but has not yet fetched or read the page. The status is a scheduling and priority issue rather than a verdict on the page. Because no fetch has happened, that page's own content is not what put it in this state, though your site's overall quality and its internal link structure both influence whether Google gets to it.
How long does it take for "discovered currently not indexed" pages to get indexed?
On small sites with strong internal linking, healthy response times and limited URL bloat, affected pages often reach the index within a few weeks without intervention. On larger sites with structural problems — URL bloat, slow servers, redirect chains, a thin content inventory — the status can persist until the cause is addressed. There is no fixed timeline; it depends on your site's crawl capacity and demand.
Does "discovered currently not indexed" mean my content is low quality?
Not the content on that page — Google has not fetched it, so it has made no judgement about the page itself. Site-level quality is a different matter: according to Google's crawl budget documentation, the crawling resources a site receives factor in popularity, overall user value and content uniqueness, so a large tail of thin or duplicated pages can suppress crawl demand across the site. Had Google evaluated this page and declined it, the status would read "Crawled — currently not indexed" instead.
What is the difference between "discovered currently not indexed" and "crawled currently not indexed"?
"Discovered" means Google has not yet fetched the page — the URL Inspection Tool shows an empty last-crawl date. "Crawled" means Google visited but declined to index it, and the Tool shows a recent crawl date. Discovered pages need crawl prioritisation: faster server responses, stronger internal links, a smaller low-value URL inventory. Crawled pages need page-level content work, though site-wide quality feeds into both.
Should I use the "Request Indexing" button in URL Inspection for discovered pages?
Use it selectively for your highest-priority pages once the structural cause is fixed. Submitting individual URLs does not raise your site's crawl capacity; it sends a prioritisation signal for those URLs. Submitting hundreds at once is ineffective. Fix server speed, internal linking or URL bloat first, then request indexing for a small set of important pages.
Can internal linking really fix "discovered currently not indexed" issues?
Yes, for demand-side problems it is one of the most effective levers available. Practitioners report that internal links from frequently crawled pages are the strongest available signal that a queued URL is worth fetching, and Google documents link extraction from known pages as one of the main ways it finds URLs. A page reachable only from your sitemap has minimal crawl demand, and contextual in-content links from related pages are often enough to move it out of the discovery queue.
Get Your Google Search Console Indexation Audit
Growth Pulse Media provides technical SEO audits for South African businesses that cover crawl budget, internal link graph, server performance, and URL architecture — the four levers behind "Discovered — currently not indexed." All work is done in-house by the same team that diagnoses the problem. No obligation — we will get back to you within 24 hours.
Request Your Free Audit