Google Site Search
Restricts Google search results to pages from a specific site, subdomain, or URL prefix so you can inspect what Google has indexed.
If you treat site: results as a complete inventory of every live URL, you will miss pages that are not indexed yet.
Key points
- Use
site:example.com keywordto find indexed pages on a specific topic. - Combine with
filetype:pdfto surface PDFs Google has indexed from your site. - Add
intitle:orinurl:to narrow results to pages where your keyword appears in the title or URL. - Put exact phrases in quotation marks to reduce false positives in site search results.
- Remember that
site:shows only indexed pages — not every page on your server. - Use different queries for
site:example.comandsite:subdomain.example.com— they return different sets.
Finding a contact page with the site operator
You maintain example.com and want to check if Google has indexed your contact page. You search site:example.com contact and see 12 results, but none is the /contact URL you published last week. Then you search site:example.com inurl:contact and the page appears fifth. That tells you the page is indexed but ranked lower than internal pages. The operator revealed visibility, not absence.
Three ways the site operator gets misused
- Treating it as a sitemap A
site:query only shows indexed URLs, not every page a site publishes. For a full inventory, check your XML sitemap or perform a content audit. - Omitting keywords Searching
site:example.comalone returns a broad, noisy list. Always add a keyword, phrase, or secondary operator to focus results on the pages you care about. - Wrong subdomain scope
site:example.comandsite:blog.example.comreturn different sets. Each subdomain is indexed independently, so choose the right prefix for the section you are auditing.
Three signals the operator can reveal
- Indexing delays A page published days ago that does not appear in
site:results may not have been crawled yet. The operator helps you spot delays without logging into Search Console. - Duplicate content If
site:example.comreturns multiple similar URLs for the same page content, Google may be showing duplicates. That is a signal to check canonical tags and robots.txt directives. - Unintended indexed pages A
site:search can expose staging pages, test directories, or old blog drafts that you forgot to block with robots.txt or noindex tags.
Three things that change the results you see
- Recrawling and reindexing Google's index updates constantly. A page missing today may appear tomorrow after recrawling. The
site:snapshot is always a moment in time, not a permanent record. - Ranking and filtering Google ranks and filters indexed pages independently of your XML sitemap or internal navigation. A site search may show pages in a different order than you expect, especially after algorithm updates.
- Content improvements Improving content can increase google search results, which may shift the pages displayed in site: searches as Google re-evaluates relevance.
Common questions
How do I search specific words on a website with Google?
Type site:example.com followed by a space and the words you want, like site:example.com pricing guide. The results only come from that domain.
Does site:show every page on a website?
No. It shows only pages Google has crawled and indexed. Live but unindexed pages — for example, brand new pages — will not appear.
Can I use site:on a subdomain?
Yes. Search site:blog.example.com to restrict results to the blog subdomain. Each subdomain is indexed separately from the main domain.
Sources
- Google Search Central: How Google Search Works Explains crawling, indexing, and serving — the mechanics behind site: results.
- Google Search Central: How To Use the Site Search Operator Official documentation for the site: operator, including syntax and examples.
- Google Search Help: Refine Google searches General guide to search operators including site:, intitle:, and filetype:.