What site:yourdomain.com really tells you about your launch
Type site:yourdomain.com into Google and you get a rough count of how many of your pages it has indexed. It is the fastest launch smell-test there is, and it is widely misread. Here is what the number actually tells you, and what only Search Console can.
Last updated June 17, 2026site:yourdomain.com in Google returns an estimate of how many of your pages are in its index. It is a 10-second diagnostic: far fewer results than you have pages means an indexing problem, far more means bloat (duplicate or parameter URLs Google should not be holding). The number is a rough estimate, not an exact count, and it never tells you which pages are missing or why. For that, use Search Console’s Page Indexing report, which is the source of truth for your own site.
- Run
site:yourdomain.com: the “About N results” line is an estimate of your indexed pages, useful as a smell test, not a precise figure. - Fewer indexed than expected points to an indexing problem: a JavaScript shell, a stray
noindex, blocked crawling, thin pages, or simply being too new. - More indexed than expected is bloat: parameter URLs, staging pages, tag archives, or duplicate paths Google should not be holding.
-
site:finds the smell; Search Console finds the cause. Use the Page Indexing report and URL Inspection for exact numbers and the reason a page is missing.
It tells you, in about ten seconds and with no login, roughly how many of your pages Google has actually put in its index, and whether that number is alarming. Search site:yourdomain.com and read the “About N results” line at the top. That estimate is the single fastest read on whether your launch is visible to Google at all. It is also the most misunderstood number in SEO, because people treat an estimate as a fact and a smell test as a diagnosis. Here is how to read it honestly.
01 · The checkHow to run it, and what to read
The operator restricts Google to a single domain. On its own it lists what Google has indexed for you; the count at the top is the headline number.
site:pagewatch.dev # everything Google has indexed for you
site:pagewatch.dev/blog # just one section
site:pagewatch.dev intitle:pricing # check a specific page is indexedHow many of a site’s pages a search engine has actually indexed, compared with how many the site has. Shallow index depth (few pages indexed relative to what exists) is one of the most common, and most fixable, reasons a new site gets little search traffic.
Compare the count to the number of real, indexable pages you know you have. The gap, in either direction, is the signal. A close match is healthy. A large gap is where the diagnosis starts.
02 · Too few, too manyThe two failure modes
Almost every problem site: surfaces is one of two shapes.
| What you see | What it usually means | First thing to check |
|---|---|---|
| Far fewer pages than you have | An indexing problem | A client-side JavaScript shell, a stray noindex, a robots.txt block, a missing sitemap, or a too-new domain |
| Roughly what you expect | Healthy index depth | Nothing; spot-check a few key URLs and move on |
| Far more pages than you have | Index bloat | Parameter or filter URLs, tag and archive pages, paginated duplicates, an indexed staging subdomain |
Too few is the launch-killer. If you shipped 40 pages and site: shows 3, search traffic is not your real problem yet; getting indexed is. The most common cause for an AI-built product is that the pages are a JavaScript shell crawlers read as empty, which is its own failure mode.
Too many is subtler but real. Bloat means Google is spending attention on URLs you never meant to publish, which muddies its sense of which pages actually matter. Prune it with canonical tags, noindex, or robots.txt.
03 · The limitsWhat it does not tell you
The reason site: is a smell test and not a verdict is that it answers “roughly how many,” and nothing else.
The “About N results” count is a rough estimate that can shift between two identical searches minutes apart. It does not tell you which pages are missing, why a page was skipped, or whether an indexed page is the canonical one. Reading it as a precise number, or as a diagnosis, is how people draw the wrong conclusion from the right tool.
So site: is perfect for the question “is something obviously wrong here?” and useless for “what exactly is wrong and how do I fix it?” For that, you need a tool that can see your actual index status, which means a tool tied to your verified domain.
04 · Search ConsoleFrom smell test to source of truth
The real number, and the reasons behind it, live in Google Search Console’s Page Indexing report. It tells you exactly how many pages are indexed, how many are excluded, and the specific reason for each exclusion (noindex, crawled but not indexed, duplicate, blocked, and so on). The URL Inspection tool goes one page deeper: paste any URL and it reports whether that page is on Google, why or why not, and lets you request indexing.
The division of labour is clean. site: is the open, no-login check you can run on any domain, including a competitor’s, to gauge scale. Search Console is the authoritative, private view of your own site that explains the cause. Use the first to notice the problem, the second to fix it.
Is your launch actually getting indexed?
Nilkick checks whether your pages can be crawled and indexed in the first place, the upstream causes of a thin site: count, alongside your sitemap, structured data, and crawler settings.
05 · The footprint frameWhere this fits your launch
Being indexed at all is the floor of your footprint: the half of launch readiness that asks whether anyone, human or machine, can find you. A product can be beautifully built and completely parseable and still be invisible, because none of that matters if Google is not holding your pages. site: is the cheapest possible check that you have cleared that floor. Once you have, the next footprint question is what Google shows for your name specifically, which is your brand SERP, and whether you are getting indexed fast enough to matter at launch.
Common questions
site: is one of the search operators that still works reliably, alongside intitle:, inurl:, and filetype:. Several old operators were retired (cache:, link:, and info: no longer function), but site: is intact. It restricts results to one domain and shows an estimated count of indexed pages at the top of the results.noindex tag or robots.txt block left on from staging, a missing or broken sitemap, or simply a brand-new domain Google has not finished crawling. Check the URL Inspection tool in Search Console to see the status of a specific page.?sort=, ?ref=), tag and archive pages, paginated duplicates, or a staging subdomain that got indexed. Bloat dilutes which of your pages Google treats as important, so it is worth pruning with canonical tags, noindex, or robots.txt.site: is the instant, no-login smell test you can run on any domain, including competitors. Search Console gives you exact indexed counts, the reason each excluded page was skipped, and tools to request indexing, but only for sites you own. Start with site: to spot that something is off, then use Search Console to find and fix it.Get your free launch-readiness score
See what else is between your product and its first real users — Nilkick scores your readiness and hands you the map. Free, no login.
https:// optional · no account · we don't email you
How to get a new site indexed by Google fast
To get a new site indexed: verify in Search Console, submit a sitemap, request indexing, and stay crawlable. But there is no instant-index button for Google, and a new domain often waits. The honest levers.
Brand SERP: what Google shows when someone searches your product name
Your brand SERP is the page Google returns for your exact product name. For a new product it is often thin, wrong, or hijacked by a namesake. What it includes, and how to own it.
What is launch readiness?
Launch readiness is how prepared a just-shipped product is to win its first users, not how finished it is. The definition, the two bars it measures, and why footprint counts more.