Google search operators

Quick definition

Google search operators are special characters and commands that change how Google interprets a query. site:example.com limits results to one domain, quotation marks require an exact phrase, and filetype:pdf returns only PDF documents.

For SEO work, operators are a fast way to look at the index from the outside. They help you inspect competitors, find duplicate text, and check whether certain URL patterns appear in search at all. They are not a measuring instrument. Results are sampled, can be personalized, and change without notice.

What Google officially documents

Google Search Central lists only a handful of operators for site owners who want to debug their presence in Search:

• site: finds results from a domain, a URL, or a URL prefix.
• filetype: finds results of a specific file type, based on the content-type HTTP header.
• src: finds pages that reference a specific image URL. It only works in Google Images.
• imagesize: finds pages with images of a given size. It also only works in Google Images.

Google's help pages for general users also describe basic syntax: quotation marks for exact matches, a minus sign to exclude a word, and OR in capital letters to allow alternatives.

Google adds an important caveat. Because operators are bound by indexing and retrieval limits, the URL Inspection tool in Google Search Console is more reliable for debugging a specific page.

The operators SEOs use most

Many popular operators are not part of the official documentation. They work at the time of writing, but Google can change or remove them without announcement.

The date filters rely on the date Google associates with a page. That date is Google's own estimate and does not always match the publication date shown on the page.

site: is a sample, not an index report

site: is the most used and most misunderstood operator. Google says clearly that a site: query does not necessarily return all indexed URLs under the prefix. Without additional search terms, the results are not ranked; Google tends to show the shortest URL first, and the rest of the order is close to random.

The number of results at the top of the page is also an estimate. It can change between two refreshes without anything happening on the site. A drop from 4,000 to 2,500 "results" is therefore not evidence of deindexing.

Use site: for questions where a sample is enough. Does this subdirectory appear at all? Are there old staging URLs in the index? Are parameter URLs visible in results? For counting indexed pages, the Page indexing report in Search Console is the right source.

Search operators in keyword research

Operators do not show search volume, but they show how a topic is covered in the index. That makes them a useful companion to keyword research.

A few examples:

• intitle:"how to clean" trail running shoes shows how many pages target a specific task directly in the title.
• allintitle: running shoes for wide feet gives a rough sense of how many pages compete for a precise long-tail phrase.
• site:reddit.com "running shoes" "wide feet" surfaces real questions and wording people use in discussions.
• "best running shoes" -site:example.com shows the competition without your own domain.

Treat these counts as signals, not as a difficulty score. A small number of allintitle: results can point to a gap, but it can also mean nobody searches that way. You still need demand data and a look at the actual results page.

Finding content gaps and competitor angles

Operators help you look at a competitor's site the way a reader would see it in search.

• site:competitor.com/blog intitle:checklist lists their checklist articles.
• site:competitor.com inurl:guide shows how they name guide URLs.
• site:competitor.com "pricing" -inurl:pricing finds pages that discuss pricing outside the pricing page.

From there, compare topics with your own content. If a competitor covers a subtopic in depth and you only mention it in passing, you have a candidate for a content gap analysis. Operators show what exists; they do not tell you whether that content performs well.

Checking indexing and duplicate content

For technical checks on your own site, operators give fast first answers.

• site:example.com inurl:tag shows whether tag archives appear in search.
• site:example.com inurl:? can surface parameter URLs. Results vary, so treat this as a hint.
• site:staging.example.com reveals whether a staging environment slipped into the index.
• "an exact sentence from your page" shows whether other domains republished your text.

The last check is the quickest way to spot duplicate content from scrapers or syndication partners. Use a distinctive sentence, not a generic one, and repeat the test with a second sentence before drawing conclusions.

Link prospecting and cleanup

Operators are also common in outreach research. Queries such as intitle:"write for us" running or "resources" inurl:links running find pages that may accept contributions or link to useful material. Check each page manually. Many such pages exist only to sell links, and paid links must carry sponsored or nofollow under Google's spam policies.

On your own domain, the same technique helps with cleanup. site:example.com "sponsored post" or site:example.com "affiliate" finds older cooperations whose links you may need to qualify.

Combining operators

Operators can be combined. Leave no space after the colon, and use parentheses carefully, because Google does not document how complex combinations are evaluated.

textsite:example.com intitle:"case study" -inurl:tag
"core web vitals" (checklist OR template) filetype:pdf
site:example.com/blog after:2025-01-01 intitle:guide

If a combination returns nothing, simplify it step by step. Silent failures are common, and an empty page does not prove that no matching page exists.

Retired and unreliable operators

Several operators that older guides still recommend no longer work:

• cache: is gone. Google removed cached page links in 2024, and the operator stopped working with them.
• link: no longer returns meaningful backlink data. Backlink research needs a dedicated tool or the Links report in Search Console.
• Older operators such as related: and info: no longer appear in Google's help and should not be relied on.

Other search engines have their own syntax. Bing, for example, documents that NOT and OR must be capitalized and limits a search to ten terms. Do not assume that a query behaves the same way in every engine.

Limits you should know

• No demand data. Operators show documents, not searches.
• Personalization and location. Results depend on language, region, device, and signed-in state. Use a neutral browser profile when comparing.
• Estimates. Result counts are rough and fluctuate.
• Sampling. Results are capped and not exhaustive, especially for large sites.
• Rate limits. Many queries in a short time can trigger a CAPTCHA. Do not automate Google queries in ways that violate Google's terms.

A practical workflow

1. Write down the question you want to answer before you type a query.
2. Start with a simple query and add one operator at a time.
3. Record the exact query, date, language, and region with your notes.
4. Check a sample of results manually instead of trusting the count.
5. Confirm findings for your own site in Search Console.
6. Add demand data before turning an operator finding into a content decision.

Common mistakes

• treating site: counts as the number of indexed pages
• reading a missing site: result as proof of deindexing
• using allintitle: counts as a keyword difficulty score
• following old guides that still recommend cache: or link:
• comparing results from different locations or accounts without noting it
• building a content plan on operator findings without checking demand
• pasting long chains of operators and trusting an empty result

The Crawl Foundry perspective

Operators answer the question "what is visible in Google right now". They do not answer how many people search for a term. In Crawl Foundry, the Search Console connection is read-only and brings the data for your own site into the same workspace, which is the more reliable source for indexing and performance questions.

For the demand side, you need search terms rather than documents. If you want to collect related searches from a seed keyword and keep them in one place, keyword discovery in Crawl Foundry covers that step. Operators remain useful afterwards, for a quick look at how directly the shortlisted terms are already targeted.

Related terms

• Long-tail keywords
• SERP analysis
• SERP features
• People Also Ask
• Thin content
• Content audit
• WordPress SEO

Review sources

• Google Search Central: Overview of Google search operators
• Google Search Central: The site: search operator
• Google Search Central: Image search operators
• Google Search Central: Spam policies for Google web search
• Microsoft Support: Advanced search options in Bing