All guides/
Indexing diagnosis

Discovered vs crawled, currently not indexed

The two Search Console states describe different points in processing. Neither proves one cause, and a sitemap submission cannot guarantee indexing.

Read the states as observations

“Discovered, currently not indexed” means Google knows the URL but the report does not show a completed crawl that led to indexing. “Crawled, currently not indexed” means a crawl occurred but the page is not indexed at the time of the report.
The labels can change after processing. Keep the inspection date and do not turn either state into a permanent diagnosis.

Group affected URLs by one pattern

Export URLs and group them by template, section, publication period and sitemap source. Choose a small cohort that shares one likely cause.
Separate errors, redirects, noindex pages and non-canonical URLs first. They need different decisions and should not dilute a content review.

For discovered URLs, inspect access and discovery

Check server reliability, robots rules, internal links, sitemap membership and whether the site produces too many low-value URL variants. A URL in a sitemap can still be delayed or ignored.
Link important pages from stable crawlable pages. Do not keep resubmitting unchanged sitemaps or strengthen URLs that should not be indexed.

For crawled URLs, inspect purpose and canonical choice

Confirm the response, rendered content, canonical, duplication and whether the page adds a useful answer beyond nearby URLs. Thin differences between filters, tags or locations may not justify separate indexing.
Improve or consolidate the pattern, not only one example. Keep pages out of the index when they have no independent search purpose.

Retest the changed cohort

Record the change and date, then inspect a bounded sample after processing time. Compare status, selected canonical, crawl date and the page that appears for relevant queries.
A successful URL Inspection request is not proof of indexing. Report what changed and what remains unknown.
StateFirst checksDecision
DiscoveredAccess, links, sitemap, URL volumeImprove discovery or remove noise
CrawledRendered answer, canonical, duplicationImprove, consolidate or exclude

Worked example: two URLs need different actions

`/guides/desk-size-chart/` is discovered but not indexed. It returns 200 and is in the sitemap, but no HTML page links to it. Link it from the relevant desk category and guide index, keep one sitemap entry and inspect it after processing time. Repeated sitemap submission would not repair the missing site path.
`/guides/desk-dimensions/` is crawled but not indexed. It repeats most of the size chart and declares itself canonical. Decide whether it has a separate job. In this example it does not, so merge its unique explanation into the size chart, redirect it and update links. If it had a distinct calculator or audience, enrich and map that role instead.
URL and stateVerified evidenceAction
/guides/desk-size-chart/ — discovered200, sitemap, no internal linksAdd useful crawlable links
/guides/desk-dimensions/ — crawledNear duplicate, self-canonicalConsolidate and redirect

Will resubmitting a sitemap force these URLs into the index?

No. A sitemap helps discovery and communicates preferred URLs, but Google decides whether and when to crawl and index each page.

Should every affected URL be sent through Request Indexing?

No. Fix the shared pattern first and reserve manual requests for important examples. Requests do not replace useful content, links or canonical signals.

Does SEODatum assign these Search Console states automatically?

This guide does not claim that. Start from Search Console evidence you can verify, then use project audit and ranking evidence for the surrounding diagnosis.

Investigate a bounded URL cohort

Use Search Console evidence with SEODatum technical audit findings, then assign an owner and retest date to the selected pattern.
Open SEODatum