Discovered vs. Crawled, Currently Not Indexed: What to Check
Learn what both Search Console statuses mean, when to fix a page or wait, and what to check before requesting indexing again.
Nov 22, 2026 · 4 min read
Field Notes from Thunkle, a studio that takes AI-built apps from prototype to secure, production-ready software.
“Discovered, currently not indexed” means Google knows the URL but hasn't crawled it yet. “Crawled, currently not indexed” means Google fetched it but hasn't included it in its index. Both tell you what happened, not whether the page is worth fixing. Start with the URLs that should actually bring in customers or answer a question you want to rank for. Google's Page indexing report explains both statuses.
First, check whether the URL is meant to rank
If the URL is a duplicate filter, login screen or tracking variant, you may not want it indexed. Check whether the clean public version is indexed instead. A service page that's meant to bring in enquiries is different: if its canonical URL isn't indexed, inspect that page before worrying about the exclusion total.
Group affected URLs by page type. One new article waiting a few days is different from a whole section of service pages missing after a redesign. Compare at least one affected URL with a working URL from the same template. That makes it easier to spot a shared fault, such as the whole section pointing its canonical tags at the homepage.
If it's discovered but not crawled, check how Google reaches it
Use URL Inspection on the exact public URL. Look at the report first, then run Test live URL if you need to check access now. With a discovered URL, the last-crawl date is generally blank. The status alone doesn't tell you a small site has a crawl budget problem.
- Check the public response. The intended URL should return
200, without a login prompt, temporary outage or unintended redirect. Check the production crawler rules and whether your CDN or host logs show recurring fetch errors. - Look for a link people can follow. Link the page from a relevant service page, guide or navigation section. If the only place you list a page is the sitemap, give it a useful link in the site's actual content.
- Check the served sitemap. Open the live XML and search for the exact canonical URL. If it isn't there, find out whether the site generated the wrong list or a cache is serving an older one. A successful sitemap submission doesn't prove that every intended page is in the file.
On Thunkle, we found three published articles that returned 200 and had the right canonicals, but were missing from a cached production sitemap. We fixed the published URL list and checked the live XML again. That established the discovery fix, not that Google indexed all three pages straight away.
If it's already crawled, check what Google got
Start with what was available at the last crawl and compare it with what the page serves now. The indexed report and the live test can disagree after a release. A passing live test means Google can access and process the current page for the checks it ran; it doesn't mean the page has been accepted into the index.
- Check the destination and canonical. Make sure Google is seeing the version you intend to rank. Look for a canonical to a different page, conflicting links or a near-duplicate with a stronger claim to answer the same question. A canonical is a signal, not an instruction Google must follow.
- Check the page content. Confirm the version Google can fetch contains the useful answer, service information or examples your visitor sees. A
200shell with missing content, or a page with little more than a template, isn't the same as a complete page. - Decide whether this page deserves to stand alone. Two pages that answer the same question often make more sense as one. Consolidate when the combined page serves both readerships, and use a relevant permanent redirect if you retire an old URL. If the pages serve different jobs, give each the evidence, examples and internal links that make its purpose clear.
When should you fix, consolidate or wait?
- Fix now if an important page has a broken response, the wrong canonical, an accidental indexing block or missing main content. Verify the live correction before requesting indexing.
- Consolidate if results would be better served by a single page and you can name the replacement. Update links and the sitemap to point to it. If you've moved many URLs, use the website migration SEO checklist to track the changes.
- Wait and monitor if the intended page is new, accessible, distinctly useful and linked. Record when it went live and recheck the URL instead of resubmitting it every day. If the issue persists across a group of important pages, investigate the shared template or release.
You can request indexing once after a meaningful fix on an important URL. If you changed many pages, keep the sitemap current. Google's recrawl guidance explains that requesting a crawl doesn't guarantee indexing and sending the same request repeatedly won't speed it up.
If the same status is affecting pages people use to find your business, Thunkle's technical SEO service can compare what Google reports with what your site serves, identify which pages need attention, and scope the fixes. Bring two or three affected URLs and one comparable page that's already indexed. That's a better starting point than the headline count.
Find out why your important pages aren't indexed.
Share a few affected URLs and what the pages should do for your business. Thunkle can trace what Google sees and scope the fixes that matter.
