usdigitalmarketingindex.com SEO
Why might Search Console label a URL ‘Crawled – currently not indexed’?
Updated November 15, 2026
Because Google fetched the page and, for now, decided not to include it in its index. Search Console’s documentation states it plainly: “The page was crawled by Google but not indexed”. The same entry adds that Google does not index every page on the web, that this is a common message for many sites, and that it does not necessarily indicate an issue needing attention (Search Console’s page indexing report documentation). The status confirms access worked. It does not say why the page was left out. The reasons worth testing are that the page duplicates or closely resembles another, that it offers little a searcher would need, or simply that the decision is recent and may change. None of these is proven by the label alone.
What a completed crawl establishes
A crawl having happened rules several things out.
| Established by this status | Not established |
|---|---|
| The URL was reachable | Why it was not indexed |
| It was not blocked by robots.txt | That the page is poor |
| The server answered | That anything is wrong |
| Google has seen the content | That the decision is final |
This is also not a crawl budget matter. The page was crawled. And it is not a penalty. Manual actions are reported separately, in the Manual Actions report.
The status answers one question only. A page that receives no impressions is not necessarily in it: the page may be indexed with nobody searching for what it covers, and telling the two apart is the subject of the guide to how to tell an indexing failure from a page with no measurable search demand.
Quality and duplication hypotheses
Treat each explanation as a hypothesis with evidence for and against. A worksheet for one URL, filled in with a made-up case, shows the method.
| Hypothesis | Evidence that would support it | What was found (made-up case) | Standing |
|---|---|---|---|
| The page duplicates another page on the site | Near-identical main content at another URL; Google's selected canonical differs | A filtered version of a category page; same products, different order | Supported |
| The page duplicates content on other sites | Text supplied by a manufacturer or syndicated | Product description is the manufacturer's standard text | Possible |
| The page has little content of its own | Main content is a few lines, or mostly template | 40 words of body text below a large template | Supported |
| The page is not linked within the site | No or few internal links | Reachable only from the sitemap | Possible |
| The rendered page differs from what visitors see | URL Inspection's rendered HTML is missing the main content | Main content present in rendered HTML | Not supported |
| The crawl was recent and the status is provisional | Last crawl date within days | Last crawled five weeks ago | Not supported |
| The page returns an error-like response with a 200 status | Empty state or not-found wording | Normal content | Not supported |
In the made-up case two hypotheses are supported and two remain possible. That is the shape an honest diagnosis takes: a short list of likely contributors, not a single verdict.
Index selection evidence
Use URL Inspection on the affected URL and read four fields.
- Last crawl date. A recent date means the decision is fresh.
- Google-selected canonical. If Google names a different URL, the page is being treated as a duplicate of that one, and the status belongs to a canonical question.
- The rendered HTML, from a live test. Confirm the main content is present in what Google renders.
- Crawl allowed and indexing allowed. Confirm no noindex rule is present.
Then look at the pattern across URLs. Export every URL in this status and group by template.
- If they are filter and parameter variants, they are duplicates Google declined, which is the outcome you would want. The fix is to stop exposing them.
- If they are thin pages of one type, such as tag archives or empty categories, the template is the issue.
- If they are your main articles and product pages, look hard at whether each offers something distinct.
On duplicates, Google’s documentation describes the mechanism: when it finds pages whose primary content is the same or very similar, “it clusters them together” and chooses one (Google’s explanation of canonicalization).
Rechecking over time
Decide what to do per group, then give it time.
| Finding | Action |
|---|---|
| URLs you do not want indexed | None needed on the status; remove links to them or consolidate |
| Duplicates of another page | Consolidate, redirect, or point a canonical to the preferred URL |
| Pages with little of their own | Add substance, merge into a fuller page, or remove |
| Pages not linked internally | Link from relevant pages |
| Good pages, crawled recently | Wait, and recheck |
| Good pages, crawled long ago, nothing found | Improve what distinguishes the page, then request indexing |
After changes, use URL Inspection to request indexing for a few representative URLs, and review the report again after several weeks. The count can fall without any change on your part, and it can rise as new pages are crawled.
Keep a record for each URL investigated: the date, the four inspection fields, the hypotheses and their standing, the action taken, and the date of the recheck. Without it, the same pages are re-diagnosed from scratch every quarter.
Two cautions. Do not conclude that the whole site is being judged low quality from this status on a set of filter URLs. And do not rewrite a page on the strength of the label alone. Establish first which hypothesis the evidence supports.
A URL that has not been fetched at all carries a different status, with different causes, explained in the guide to why Search Console labels a URL discovered and currently not indexed.
The reading to keep: crawled and not indexed is a decision about inclusion. Find out which pages it applies to before deciding that it is a problem.
Add your comment to this answer