GlossarySEO
What does the site: search operator show?
Also called: site: search, site: operator, site:example.com
Definition
The site: operator limits Google results to one domain or URL prefix, as in site:example.com/blog. It's a quick spot check, but Google says it doesn't necessarily return every indexed URL.
site: search operator, explained
Typing site:example.com into Google returns pages from that domain. Adding a path narrows it: site:example.com/glossary. Combined with a keyword, it shows which of your pages Google associates with that word, which is handy for finding internal linking candidates or accidental duplicates.
Google's documentation is explicit about the limits. The site: operator doesn't necessarily return all the URLs indexed under the prefix, and bigger sites shouldn't expect to see all their URLs. It was designed for searchers, not site owners. The result count shown at the top is a rough estimate that can swing wildly between queries and days.
So use it for yes-or-no spot checks and discovery, not measurement. Good uses: checking whether a staging subdomain leaked into Google (site:staging.example.com), finding old pages you forgot existed, seeing how Google titles and describes your pages, and spotting spam pages injected by a hack. For whether a specific URL is indexed, Google points you to the URL Inspection tool. For how many pages are indexed, use the Page indexing report in Search Console.
One more trick: site: combined with -inurl: or a quoted phrase helps find duplicate or thin sections quickly. Searching site:example.com "lorem ipsum" or a line from your template's placeholder text is a fast way to find unfinished pages that slipped into the index. Treat what you find as a lead to check in Search Console, not as the full picture.
Why it matters for founders
Founders often run site: on launch day, see a small number and panic. It's the wrong gauge. It's a great way to catch leaks and oddities, though.
Example
You search site:app.example.com and find 200 logged-in dashboard URLs in Google. You add noindex to the app shell and require authentication, and they drop out over the following weeks.
Common mistakes
- Treating the
site:result count as your indexed page count. - Checking a single URL with
site:instead of URL Inspection. - Never checking whether staging or app subdomains are indexed.
- Panicking when a new page isn't in
site:results the same day.
Sources
Checked
Related terms
- IndexingIndexing is when a search engine analyzes a crawled page and stores it in its index, the database it serves results from. A page that isn't indexed can't appear in search results.
- URL Inspection toolURL Inspection is a Search Console tool that shows Google's indexed view of one URL, including index status, Google-selected canonical and last crawl, and can run a live test or request indexing.
- Page indexing reportThe Page indexing report in Search Console shows how many of your known URLs are indexed and groups the rest by the reason they aren't, like noindex, redirect, duplicate, 404 or crawled but not indexed.
- Google Search ConsoleGoogle Search Console is Google's free tool for site owners. It shows which queries bring impressions and clicks, which pages are indexed and why others aren't, and alerts you to manual actions and security issues.