SEO / Indexing · 06 min read · Updated Sep 2026
Crawled — currently not indexed: Google fetched the page and left it out
This Search Console status means the URL was fetched and then not selected for the index. It is a quality and duplication decision, not a crawl queue.
A crawled URL that stays out of the index has already been judged. Make it the clearest page for its query, then ask Google to fetch that version.
Read the status as a selection, not a delay
‘Crawled — currently not indexed’ means Googlebot already fetched the URL and then chose not to keep it. There is no remaining queue. The HTML was read, and the page lost the comparison against other URLs that answer the same query. That is the opposite of ‘Discovered — currently not indexed’, where the URL is known and still waiting for a first fetch.
A 200 response does not oblige Google to index the page. Indexing is a choice about whether this URL is the best version of that answer. The usual reasons are a thin or repeated page, a canonical that points somewhere else, a template Google has learned to skip, or a URL that adds nothing beside a stronger page on the same site.
- Keep this status separate from discovered-but-not-indexed.
- Confirm the live status code, canonical, and robots meta before you rewrite.
- Treat a self-canonical 200 as a content decision, not a crawl error.
Sort the sample by template before you edit
Open the page indexing report and inspect the example URLs. Group them by template. A cluster of tag archives, filtered categories, or parameter copies should stay out of the index. A cluster of service pages, guides, or district pages is the incident, because those are the URLs you meant searchers to find.
Compare one affected URL with the page you wish Google would keep instead. If the live canonical already points at that stronger page, the status is doing what you asked. If the canonical is self-referencing and the copy repeats another URL, consolidate the two or give this page its own query, its own evidence, and its own next step. On a Hong Kong site, replacing the district name is not a distinct answer.
Improve the page, then ask for one more fetch
Requesting indexing on a page Google has already rejected does not change the comparison. First make the canonical URL worth keeping. Add the explanation a searcher still needs, state who the page is for and where it applies, and place one ordinary internal link from a URL Google already crawls. Take near-duplicates out of the XML sitemap so they stop competing with the page you want kept.
Use URL inspection on a few representative URLs, not on every row in the report. Request indexing only when the HTML you want is the HTML Google will fetch: indexable, canonical to itself, and visibly different from the neighbouring page. Watch that same template. The status clears when a later fetch is selected for the index, because the page is now the clearest URL for the query, not because the request button was pressed.
- Leave filters, parameters, and thin archives excluded on purpose.
- Link the repaired URL from a page that is already crawled.
- Re-check the same template in the indexing report after the next crawl.
Questions
Why did Google crawl a page and not index it?
Google fetched the URL and decided another page was a better result for that query, or that this URL was too thin or too similar to keep. Fix the canonical, the duplication, or the missing answer before you request indexing again.
How is this different from Discovered — currently not indexed?
Discovered means Google knows the URL and has not fetched it yet. Crawled — currently not indexed means the fetch already happened and the page was not selected. One is a priority problem. The other is a selection problem.
Continue reading
- Duplicate, Google chose different canonical than user
- Indexed, though blocked by robots.txt: search kept a URL it did not fetch
- How to refresh evergreen content without losing its signal
This note is part of the Hong Kong field library from My Search / Visibility, built with Itehk.