Lees deze gids in het Nederlands →
“Discovered – currently not indexed” means Google found your URL but never fetched it; “Crawled – currently not indexed” means Google fetched the page and declined to keep it. That one difference — fetched or not — decides which fix will work.
- Discovered = a discovery/priority problem: fix it with internal links and crawl priority, not content changes.
- Crawled = a value problem: Google saw the page and passed. Improve or consolidate the content.
- Google itself says indexing “can take anywhere from a few days to a few weeks” — on new sites, waiting is often the right move.
- In Reddit threads we reviewed, pages sit stuck from 2.5 weeks to 3+ months; one programmatic site had 29 pages unfetched after 8+ months of sitemap submission.
- The most-cited fix across r/SEO and r/bigseo is internal links from strong, already-indexed pages — not resubmitting in URL Inspection.
“Discovered – currently not indexed” means Google knows your URL exists but hasn’t crawled it yet — usually a crawl-budget or low-priority signal. The page was never fetched.
“Crawled – currently not indexed” means Google did fetch the page and then chose not to index it — usually a quality, duplication, or thin-value signal.
That one difference — fetched or not — decides your fix. Discovered is a discovery/priority problem; Crawled is a value problem.
The one difference that matters
Which one do you have?
Fixes that actually work
The Indexing-API “trick”
When it’s normal
FAQ
The one difference that changes your fix
Both statuses live in the same Google Search Console report, and people treat them as the same problem. They aren’t. The wall between them is a single question: did Googlebot actually fetch the page?
Found, not fetched
What it means: Google saw the URL (in your sitemap or a link) but hasn’t crawled it. It’s sitting in a queue.
Fetched, not kept
What it means: Google crawled the page, evaluated it, and decided it wasn’t worth adding to the index — yet.
Get this right and everything downstream gets simpler. Chasing “crawl budget” when your real problem is thin content wastes weeks — a point practitioners on r/bigseo make repeatedly about pages “stuck for 8+ weeks” that no amount of re-submitting fixes.
Which one do you have? A 30-second decision
- Is the URL reachable in ≤3 clicks from your homepage?
- Does it sit in your sitemap and get internal links?
- Is your server fast and error-free in the logs?
- Is the content substantially unique vs. other pages?
- Does it answer a real query better than what ranks now?
- Is it canonical, or a near-duplicate of another URL?
Answer the three questions in your column. Each “no” is a lever you can pull — in the order they’re listed.
Fixes that actually work (and the order to try them)
If it’s Discovered — make the page easy and worth reaching
- Add internal links from strong, already-indexed pages. This is the single most-cited fix in practitioner threads: a link from a page Google already trusts pulls the stuck URL into the crawl queue faster than re-submitting ever will.
- Flatten the click depth. Pages buried 5+ clicks deep read as low-priority. Surface them from hubs and category pages.
- Check your server logs for crawl waste. If Googlebot is burning its budget on parameter URLs, faceted filters, or 5xx errors, your good pages starve. Block the junk in robots and fix the errors.
If it’s Crawled — give Google a reason to keep it
- Raise the page’s unique value. Add first-hand detail, data, or a clearer answer than the current top results. “Crawled – not indexed” is often Google saying we already have this.
- Consolidate thin or near-duplicate pages. Ten shallow pages that each get rejected are worse than one strong page. Merge and redirect.
- Fix canonical confusion. If two URLs look the same to Google, it keeps one and drops the other. Make your canonicals explicit. See our full canonical guide.
- Then — and only then — request indexing. Use URL Inspection sparingly once the page genuinely deserves it. Re-submitting a weak page changes nothing.
On r/SEO the recurring conclusion is that persistent “crawled – not indexed” on an otherwise healthy site usually isn’t a technical glitch — it’s Google’s read on content quality or domain authority. The fix is rarely a button; it’s the page being worth indexing.
The Indexing-API “trick” — why it’s tempting, and why it can backfire
You’ll find guides (and Reddit threads) showing how to force pages in via Google’s Indexing API — a step-by-step with a service account and a batch of URLs. It can work in the short term. But two things are true and usually left out:
- Google’s own docs say the Indexing API is only for JobPosting and BroadcastEvent pages. Using it for ordinary posts is off-label.
- Google has added an explicit spam warning to that documentation. Abuse can cost you far more than the pages were worth.
Treat the Indexing-API route as a red flag, not a shortcut. If a page needs a workaround to get indexed, that’s a signal the page — or the site’s authority — isn’t there yet. Fix the cause.
When “not indexed” is completely normal
Not every unindexed URL is a problem. New sites and new pages sit in these statuses for days to a few weeks while Google gauges the site. If your page is a week old on a young domain, the honest answer is: keep publishing, keep earning links, and wait. Panic-submitting daily does nothing but make you anxious.
| Search Console status | Did Googlebot fetch it? | Root cause | Fix that works |
|---|---|---|---|
| Discovered – currently not indexed | No | Crawl priority / discovery | Internal links, sitemap, reduce click depth |
| Crawled – currently not indexed | Yes | Quality / duplication judgement | Improve or merge content, fix canonicals |
| Excluded by noindex | Yes | Your page says “stay out” | Remove the noindex, recrawl |
| Blocked by robots.txt | No (not allowed) | Crawl rule | Fix the Disallow rule |
What do practitioners report actually worked?
We put the Reddit threads behind this guide through a structured source review (via NotebookLM, September 2026). Across r/SEO, r/bigseo, r/TechSEO and r/localseo, five fixes come back again and again as the ones that actually moved stuck pages:
- Internal links from strong pages. “I had this issue until I added more internal linking.” (r/SEO)
- A slight slug change, which makes Google treat the URL as new: “The only way I have to fix them is a slight slug edit.” (r/bigseo)
- A few backlinks to the stuck page: “Just sent a couple of backlinks to the page and it was fixed.” (r/SEO)
- Fixing page speed. One site owner with 2–3 minute load times: “I added a lazy load images code… about 3 days later, all the pages were indexed again.” (r/SEO)
- The Indexing API — one r/TechSEO test reported 94% indexed within 48 hours versus 8.4% via the sitemap. It works short-term, but it’s outside Google’s rules for normal pages; we explain the risk in our Indexing API guide.
The scale varies wildly: threads describe 3 stuck pages on a local-business site, 29 on a programmatic site after 8+ weeks, and 8,000 flagged on a news site. And the frustration with generic advice is real — “Anyone solved this beyond ‘earn backlinks and wait’?” (r/bigseo). That’s exactly why the split above matters: first determine which status you have, then apply the fix that matches it.
Is it crawl budget? On sites under about 10,000 pages, almost never. Google’s own thresholds are in crawl frequency and crawl budget explained.
Timing matters. A sudden jump in this status right after a Google update can be algorithmic — see our coverage of the September 2026 spam update.
FAQ
How long should I wait before worrying?
On an established site, a genuinely valuable page usually indexes within days to two weeks once it’s linked internally. On a brand-new domain, several weeks is normal. Worry when a well-linked, high-value page stays stuck past ~3–4 weeks. See typical indexing timeframes.
Does “crawled – currently not indexed” fix itself?
Sometimes — Google re-evaluates over time. But if the cause is thin or duplicate content, waiting won’t help. Improve the page’s value first, then let Google recrawl.
Will a paid indexing service fix it?
Rarely, and not durably. Those services mostly help get backlinks discovered, not your own thin pages accepted. If Google crawled your page and declined it, paying to ping it again doesn’t change its judgement. We cover which services do what — honestly — in our reviews.
Is “Discovered” or “Crawled” the worse problem?
Neither is inherently worse — they’re different jobs. Discovered is usually the easier fix (linking, crawl budget). Crawled means Google already judged the page, so it can take more work.
What is the difference between Discovered and Crawled currently not indexed?
Discovered means Google knows the URL exists but has not fetched it yet, which is a crawl-priority problem. Crawled means Google fetched and evaluated the page but chose not to index it, which is a content-value problem.
Does changing the URL slug really get a page indexed?
Practitioners on r/bigseo report that a slight slug edit can work because Google treats the new URL as a fresh page. It is a workaround, not a fix: the underlying quality or priority issue usually remains.
How many pages stuck in these statuses is normal?
On large or programmatic sites, hundreds or thousands of excluded URLs can be normal. Worry when well-linked pages you actually want to rank stay stuck past three to four weeks on an established site.
Comments
5 responses to “Crawled vs. Discovered — Currently Not Indexed: what each one means, and how to fix it”
[…] Read this guide in English → […]
[…] Related: Crawled vs. Discovered — currently not indexed → […]
[…] Related: Crawled vs. Discovered → […]
[…] If GSC says “Discovered – currently not indexed” That’s this exact stage: found, not fetched. The fix is links and crawl priority, not content. Full playbook in Crawled vs. Discovered — currently not indexed. […]
[…] Be indexable first. No index, no citation. Fix crawling and indexing before anything else — start with Crawled vs. Discovered. […]