“Discovered — currently not indexed.” Here's what it means and how to fix it.
What it means: Google knows your URL exists but hasn't crawled it yet. Google discovered it, added it to the queue, and keeps deprioritizing it.
Not the same as “Crawled — not indexed.” Discovered = Google hasn't visited. Crawled = Google visited and rejected. Different problem, different fix.
Quick fix: Clean sitemap → Add 3–5 internal links → Improve content to 500+ words → Fix server speed → Submit through multiple channels → Wait 14 days and recheck.
8 reasons Google discovered your page but won't crawl it.
Low domain authority
HardNew domain, few backlinks. Google allocates crawl budget based on perceived importance.
Short term: submit through multiple channels, create social profiles with links. Long term: build quality backlinks, publish substantial content.
Expected timeline: 1-3 months
Crawl budget exhaustion
MediumToo many low-value URLs: filter pages, parameter variations, tag pages. Google spends its budget crawling junk and never reaches your real pages.
Noindex low-value pages. Block crawling via robots.txt for filters/sorts. Remove from sitemap. Consolidate pagination.
Expected timeline: 2-7 days after cleanup
Thin or duplicate content signals
MediumGoogle crawled other pages on your site and found thin content. It now expects the same from uncrawled pages. Site-level signal.
Improve INDEXED pages first (500+ words unique content). Add structured data, specs, FAQs. Remove/noindex pages under 100 words.
Expected timeline: 2-4 weeks
Sitemap pollution
EasySitemap includes noindex pages, redirects, 404s, parameter URLs. Google loses trust in your sitemap and deprioritizes ALL listed URLs.
Audit every URL: must return 200, no noindex, canonical to self, has content. Remove everything else. Resubmit.
Expected timeline: Within days
No internal links (orphan pages)
EasyZero internal links = Google sees the page as unimportant. If the site owner does not link to it, why should Google prioritize crawling it?
Add 3-5 internal links from relevant, indexed pages. Body content, descriptive anchor text. Create hub pages.
Expected timeline: 1-2 weeks
Slow server response
MediumServer takes 5+ seconds to respond. Slow servers waste crawl budget on waiting. Google deprioritizes slow sites.
Upgrade hosting. Enable caching (Varnish/Redis). Use CDN. Optimize database queries. Target under 500ms TTFB.
Expected timeline: Within days once fixed
Recently published
EasyPage is less than 14 days old. Nothing is technically wrong. Google simply has not processed its queue yet.
Wait 7-14 days. If still stuck: submit via GSC. If still stuck after 5 more days: submit through multiple channels.
Expected timeline: 7-14 days naturally
Conflicting robots directives
Easyrobots.txt blocks crawling, or meta robots / X-Robots-Tag conflicts exist. Google cannot crawl what it cannot access.
Check three places: robots.txt, meta robots tag, X-Robots-Tag header. All three must be clean. Common traps: WordPress plugins, staging configs, CDN headers.
Expected timeline: 2-7 days after fix
Quick diagnosis: find your problem in 2 minutes.
Step-by-step: get “Discovered” pages into the index.
When to act vs when to wait.
You fixed a technical issue (robots, canonical, sitemap)
You added internal links to orphan pages
Pages stuck for 3+ weeks with no change
You cleaned and resubmitted your sitemap
You improved site-wide content quality
Page is less than 14 days old
Submitted via GSC less than 5 days ago
No changes made since last submission
Google is updating its index (check for algorithm updates)
Frequently asked questions.
Still stuck on “Discovered”?
Readiness checks identify observable blockers, applicable discovery signals are sent, and independent status checks monitor each URL from D0 through D14. Google decides the outcome and timing.
Get 200 free credits — no card needed →