Three weeks of 'Crawled - not indexed' on a fresh domain: what the GSC data actually shows
What “Crawled - currently not indexed” means It means Google fetched a page and chose not to add it to the index yet. It does not mean the URL is invisible forever, and it does not tell you which specific signal is mis
What “Crawled - currently not indexed” means
It means Google fetched a page and chose not to add it to the index yet. It does not mean the URL is invisible forever, and it does not tell you which specific signal is missing. The useful next step is to separate crawl access from indexing decisions, then watch for changes in Search Console rather than repeatedly resubmitting the same URL.
I have been tracking a small set of Vietnam airport travel guides on a new site. The latest Search Console snapshot shows 0 of 17 tracked guide pages indexed, with 16 reported as “Crawled - currently not indexed”; the remaining URL has a different inspection state. Googlebot has fetched most of these pages already. That evidence rules out a basic discovery failure for the crawled set, but it does not tell us that the pages are useful enough, distinct enough, or trusted enough to index.
What I measured
I kept three signals separate:
- Crawl and inspection status: whether Google has fetched a URL and what the inspection tool currently reports.
- Search performance: impressions, clicks, and query positions. These only tell a ranking story after pages begin appearing in results.
-
Submission responses: whether an API accepted a notification. A
200response means the request was accepted; it is not proof that Google indexed the page.
That distinction prevents a common reporting mistake: treating a successful submit call as an indexing result. Sitemaps help Google discover canonical URLs and learn about updates. IndexNow notifies participating engines such as Bing. Neither one can force an indexing decision.
Changes that are easy to verify
I checked that each guide has a self-referencing canonical, a working sitemap entry, and links from relevant hub pages. I also checked that the pages load without an authentication wall and return the expected page rather than an error or a duplicate shell. For a guide about immigration timing, for example, the Vietnam airport immigration wait-time guide should be reachable from the site’s navigation and explain what varies by airport and arrival bank, not just repeat a generic promise.
I then resubmitted the sitemap and notified the engines about URLs that had actually changed. Those are operational nudges, not ranking tactics. I did not rewrite every page just to make the word count larger: the useful test is whether each URL answers a distinct traveler question with current, specific information.
What I would do next
For a small site with no indexing history, I would avoid changing many variables at once. Keep a dated record of inspection verdicts and crawl dates. Fix technical errors immediately; otherwise, improve one genuinely weak page at a time and add a relevant internal link where it helps readers. Give Google time to recrawl before judging the change.
A page can be crawled but excluded because it is redundant, low value, or simply not selected yet. Search Console does not expose a definitive diagnosis for every URL. If a page later earns impressions, use its actual queries to refine the answer. If it remains unindexed after a longer observation period, compare it with the pages already indexed and look for overlap or missing first-hand detail instead of sending the same request every day.
For readers planning a Hanoi arrival, the Noi Bai airport page has airport-specific service details. Travelers who already know they need assistance can review the booking options. Both links are there for the relevant next step; the technical lesson remains simple: measure crawling, indexing, and search visibility as separate stages.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.