Discovered or Crawled – Currently Not Indexed: How to Diagnose Each

“Discovered – currently not indexed” and “Crawled – currently not indexed” describe different stages in Google Search Console. Neither label alone proves a penalty or a sitewide failure. The useful question is whether the affected URLs are pages you actually want in search, and what Google could access when it evaluated them.

What each status means

Discovered means Google knows the URL but has not crawled it yet. Crawled means Google has visited the URL but has not indexed it. The Page indexing report may update after a delay; inspect a representative URL and compare the reported state with a live test. Google explains these statuses in its Page indexing report documentation.

A search results site: query is not a dependable diagnostic for one URL. Use URL Inspection for the indexed state, last crawl, canonical information, crawl and indexing permissions, and a live test. A live test checks the current page, while the indexed result reflects what Google last processed.

First decide which URLs deserve investigation

Export examples from each status and classify them: approved landing pages, product or service pages, articles, pagination, tags, filters, parameters, redirected URLs, and deliberate duplicates. A large count of excluded URLs can include perfectly expected URLs. Prioritize important canonical pages with internal links and a clear purpose.

Create a small worksheet with URL, page type, status, last crawl, sitemap inclusion, internal link source, HTTP response, robots directive, canonical, content assessment, owner, and next check date. Sample pages from each template rather than assuming every URL has the same cause. Our SEO audit report template provides a fuller issue log.

Diagnose discovered but not crawled

• Open several representative URLs in URL Inspection. Confirm that the page resolves for users and is linked from relevant crawlable pages.
• Check the sitemap for the preferred canonical URL. Sitemaps help discovery but do not guarantee crawling or indexing.
• Review server uptime, response times, rate limiting, and recent traffic from verified Googlebot if logs are available.
• Look for large groups of faceted, calendar, search result, or parameter URLs competing with important pages for crawl attention.
• Strengthen clear internal paths from category or hub pages to valuable URLs; avoid orphaned pages.

Do not submit every discovered URL repeatedly. Correct structural and access problems first, then monitor a representative cohort. Google’s crawling troubleshooting guide covers access failures, and the technical SEO checklist gives a broader review.

Diagnose crawled but not indexed

Inspect the indexed information and live page. Check the HTTP status, robots meta or X-Robots-Tag, canonical target, rendered content, and links. If Google selected another canonical, investigate duplicate or near-duplicate pages and conflicting signals rather than treating this status as a standalone instruction to request indexing.

Compare the page against other pages on your site that serve the same intent. Is it substantially distinct, complete, current, and useful? A thin location variation, empty category, near-identical product page, or placeholder article may not merit a separate index entry. Consolidate duplicates where appropriate and improve pages with a genuine purpose. Do not add arbitrary text just to increase word count.

If content is loaded with JavaScript, verify the rendered HTML and resources through URL Inspection. Check whether the main copy and navigation links are visible to Google. For a deliberate noindex page, the non-indexed state is expected; document it rather than trying to “fix” it.

A practical order of operations

• 1. Define the desired indexable set and choose representative URLs by template.
• 2. Confirm the URL, response, crawl permission, indexing directive, canonical, rendered content, and internal links.
• 3. Fix confirmed access or template defects before requesting recrawl.
• 4. Improve or consolidate weak and duplicative pages where the page purpose warrants it.
• 5. Update links and sitemap entries to preferred URLs, then request indexing for a small number of important changed pages if useful.
• 6. Record the deployment and revisit URL Inspection and report trends over time.

Google does not guarantee indexing after a request. The status can persist while a page is reevaluated. Measure whether the important URL cohort improves, and avoid interpreting a single report snapshot as an immediate result. For a broader analysis of queries and landing pages, use our Search Console SEO audit workflow.

When to escalate

Escalate promptly if a release, migration, server rule, or accidental noindex affects important pages across a template. Collect example URLs, timestamps, responses, rendered output, and changes made. If only a few new pages are affected and the live tests are healthy, monitor them before changing the entire site. The right remedy depends on the evidence, not the label alone.