The processing path
In plain English: Google must learn about a URL, retrieve it, process it and select a canonical before it can be eligible to rank.
Discovery can come from links or sitemaps. Crawling retrieves accessible resources. Rendering can process JavaScript-driven output. Indexing analyses content and canonical relationships. Ranking happens later for a particular search context.
- Discovered does not mean crawled.
- Crawled does not mean indexed.
- Indexed does not guarantee impressions.
Reasons a URL may be excluded
In plain English: Some exclusions are intentional; others reveal a technical or content problem.
A noindex directive, redirect, duplicate canonical, soft 404, server failure or access restriction can explain exclusion. Discovered—currently not indexed means Google knows the URL but has not crawled it yet. Crawled—currently not indexed means it was fetched but not selected for the index at that time.
Review whether the URL is a unique, useful canonical page before trying to force every excluded URL into the index.
Robots, noindex and canonicals
In plain English: These controls solve different problems.
robots.txt controls crawler access; it is not a reliable way to prevent a URL from appearing in search. If crawling is blocked, Google may be unable to see a page-level noindex directive.
A canonical annotation expresses a preferred representative among duplicate pages, but Google can select another canonical based on its signals. Redirects and consistent internal links are stronger context than contradictory signals.
Keep in mind: Allow Google to crawl a page when it needs to see and obey its noindex directive.
Diagnose rather than promise
In plain English: Fixing eligibility removes a barrier; it does not guarantee selection or ranking.
Use the Page indexing report for patterns and URL Inspection for one important URL. Confirm response status, indexability, rendered content, canonical signals and internal links. Then allow time for recrawling and processing.