Contents
- Indexing isn't automatic: Google decides what it keeps, based on the value it perceives.
- Five causes explain most blockers, and only one is technical.
- The URL inspection tool gives the exact reason page by page: it's the first reflex, not the last.
- "Crawled, currently not indexed" isn't an error: it's a judgment. Re-requesting indexing without changing the page does nothing.
- The right metric isn't the number of indexed pages, but the share of useful pages that generate clicks.
Crawl, index, rank: three distinct steps
A page goes through three independent steps. Google discovers it, via a link or a sitemap. It crawls it, meaning it loads it. Then it decides whether or not to index it.
- Discovery
Google learns the address exists, via a link from an already-known page or via a sitemap. Without this signal, the page stays invisible even if it's been live for months.
- Crawling
The bot loads the page. At this stage, a block in robots.txt or a server error stops everything, and the reason is explicit in Search Console.
- Indexing
Google decides whether to keep the page in its index, or not. This is where most blockers play out, and it's a value decision, not a technical process.
- Ranking
The indexed page competes on queries. An indexed page that appears on no query doesn't have an indexing problem but a relevance problem.
A page can therefore be crawled without being indexed: Google read it and didn't find it worth keeping. It's the most common case, and the most misunderstood. It's not a bug, it's a judgment.
The five real causes
| Cause | Status shown in Search Console | What to do |
|---|---|---|
| The page brings nothing new | Crawled, currently not indexed | Rewrite or merge, not re-request indexing |
| It's linked from nowhere | Discovered, currently not indexed | Add a link from a strong page |
| It's a duplicate | Duplicate, Google chose a different canonical | Clarify the canonical, or remove the variant |
| The site isn't crawled enough | Discovered, currently not indexed | Publish more regularly, cut useless pages |
| A technical block | Blocked by robots.txt, or excluded by the noindex tag | Fix the rule or remove the tag |
The first is by far the most common. Thin content, close to an existing page or a template repeated dozens of times, has no reason to be indexed. The second comes right after: an orphan page, reachable only by its direct URL, sends a clear signal about its importance in the site.
Diagnose in three minutes
Open URL inspection in Search Console and paste the address. Three pieces of information matter.
- The indexing status says whether the page is in the index.
- The coverage gives the exact exclusion reason, with the wording that appears in the table above.
- The live test says whether the page is crawlable now, which distinguishes a current block from an old, already-fixed problem.
If the status reads "crawled, currently not indexed", don't request indexing: Google has already seen the page and set it aside. Re-requesting without having changed the page does nothing, except use up your daily quota.
What actually speeds it up
- An internal link from an already well-indexed page
The fastest and the most neglected. It signals the page's importance and provides a crawl path. On a mid-sized site, it's often the only lever needed.
- An up-to-date sitemap
It helps discovery, without guaranteeing indexing. It declares a page exists, it doesn't prove its value. Useful on large sites, marginal on small ones.
- Regular publishing
A site updated every week is crawled far more often than one frozen for six months. The effect is indirect but durable, and it benefits every page.
Not every page should be indexed
A costly reflex is wanting everything indexed. Filter pages, deep pagination, internal search results and technical pages have no business in the index. Pushing them there dilutes Google's perception of the site's quality.
The right metric isn't the number of indexed pages, but the proportion of useful pages that are, and above all the share of those that generate clicks. The method for separating the two is described in our article on the Search Console queries that pay off.
Frequently asked questions
The Adwise team connects Google Ads, Meta Ads, LinkedIn Ads, GA4 and Search Console so agencies and freelancers can run their campaigns from a single place.