Google site: Search Operator: Explore What Google Can Show From a Site

Search within one domain

site:example.com

Google may show indexed and serving URLs from the domain, including subdomains. For a more specific area, use a URL prefix:

site:https://www.example.com/tutorials/

Find pages related to a term

The original Plus2Net article used this technique to locate where a phrase appeared within one section. That remains useful.

site:www.plus2net.com/php_tutorial/ "math functions"

This can help you find pages Google associates with a topic, identify older articles that may need internal links, or inspect possible duplicate coverage before creating another page.

For larger internal-linking work, however, use the section sitemap or URL inventory as the primary reference, following the approach in our Pillar Pages and Topic Clusters guide.

Look for unexpected spam or hacked content

Google's own documentation gives site: searches as one way to look for suspicious content on a site. For example:

site:example.com casino
site:example.com viagra

If unexpected pages or topics appear, investigate the website, server logs, CMS/users and Search Console security information. A site: search is only a clue; it is not a complete malware scanner.

You can test a page or prefix, but use URL Inspection for authoritative debugging

site:https://www.example.com/page.html
site:https://www.example.com/page.html keyword

If an important page does not appear in a site: result, do not conclude immediately that it is not indexed. Google recommends using Search Console's URL Inspection tool for a more reliable indexing diagnosis.

See Google Search Console and Bing Webmaster Tools.

What the site: operator cannot tell you reliably

• It does not provide an exact total of all indexed URLs.
• The order of results is not a normal ranking report.
• A missing URL does not prove that the page is not indexed.
• It is not a substitute for Search Console indexing reports or URL Inspection.
• It should not be used to recreate obsolete ideas such as Google's old “supplemental index” checks.

Use site: for exploration, Search Console for verification

1. Run a broad site: query to see examples of what Google is showing.
2. Add a topic or suspicious keyword when investigating a specific issue.
3. Use a directory prefix when checking one site section.
4. Use URL Inspection for an important URL that needs a definitive indexing check.
5. Use Search Console reports for scalable monitoring.

A useful search operator, not an index counter

The site: operator remains useful for quick site-specific searches, content discovery and debugging. Its biggest limitation is also the most important modernization change: do not use it to estimate the exact number of pages Google has indexed.