Google Search Operators: Complete List and Examples
On this page
Google search operators are the commands that turn Google from a search box into a research tool. Add site:, quotes, filetype:, intitle:, or date filters, and you can find pages normal keyword searches miss.
They are useful for SEO audits, competitive research, link prospecting, and debugging what Google has actually indexed. If you also need country, language, or AI-mode controls, pair operators with Google search URL parameters.
This guide gives you the complete operator list, practical examples, and power-search workflows you can reuse before automating the same searches with a SERP API.
What are Google search operators?
Google search operators are special characters and commands that extend standard keyword searches. They tell Google how to find something, not just what to find.
Google’s own help documentation calls them “operators” and officially documents a core set — site:, filetype:, before:, after:, exact-match quotes, and the minus sign — on its Refine web searches page. Most of the operators SEO practitioners rely on daily, though, are undocumented conventions that Google supports without listing.
They’re distinct from Google Search Parameters:
- Operators (
site:,filetype:,"") go directly into the search bar alongside your keywords. - Parameters (
gl=us,hl=en,udm=14) get appended to the URL and control backend settings like geolocation, language, or AI features.
Operators are filters on your keywords; parameters change the search environment itself.
Essential search operators for precision
The most useful operators, with quick notes on when each one earns its keep.
1. "" (Exact match)
Encloses a phrase to find results containing that exact sequence of words.
- Usage:
"best coffee shop in London" - Why it’s useful: drops results where the words are separated or reordered. Useful for quotes, product names, or multi-word keywords.
2. - (Exclude term)
Put a minus sign directly before a word to exclude results containing that term.
- Usage:
apple -fruit(finds Apple Inc., not the fruit) - Why it’s useful: filters out noise on ambiguous terms. Handy for competitive analysis (e.g.,
"CRM software" -salesforce).
3. OR (Combine searches)
Finds results that contain either term. Must be capitalized.
- Usage:
(SEO OR "search engine optimization") training - Why it’s useful: covers synonyms or alternative phrasing in one query. Group terms with parentheses
().
4. * (Wildcard)
Acts as a placeholder for any word or phrase. Google fills in the blank.
- Usage:
"the * of SEO"(matches “the future of SEO,” “the basics of SEO”) - Why it’s useful: surfaces phrase variations and incomplete quotes.
5. site: (Domain-specific search)
Restricts your search to a single website or domain.
- Usage:
site:cloro.dev SEO(finds all pages on cloro.dev mentioning SEO) - Why it’s useful:
- Content audits. See what Google has indexed for your site (
site:yourdomain.com). - Competitive analysis. Inspect a competitor’s content strategy (
site:competitor.com "pricing"). - Content gaps.
site:yourdomain.com keyword -inurl:blogfinds keyword pages outside your blog.
- Content audits. See what Google has indexed for your site (
6. filetype: (Specific file types)
Limits results to a particular file extension (e.g., PDF, DOCX, PPT, XLS).
- Usage:
site:gov filetype:pdf "economic report" - Why it’s useful:
- Research. Pull whitepapers, academic studies, or official documents.
- Competitive intelligence. Surface competitor presentations, annual reports, occasionally spreadsheets that shouldn’t be public.
- Content opportunities. See which formats are ranking for your keywords.
7. intitle: / allintitle: (Keyword in title)
Finds pages with your keyword(s) in the title tag of the webpage.
- Usage:
intitle:"SEO guide"(finds pages with “SEO guide” in the title) allintitle:requires all subsequent words to be in the title:allintitle:best SEO tools- Why it’s useful:
- SEO analysis. Pinpoint pages specifically optimized for a term.
- Content ideation. See what angles competitors take on a topic.
- Resource discovery. Find high-relevance articles or tools.
8. inurl: / allinurl: (Keyword in URL)
Finds pages with your keyword(s) in the URL string.
- Usage:
inurl:blog SEO(finds blog posts with “SEO” in the URL) allinurl:requires all subsequent words to be in the URL:allinurl:ai tools guide- Why it’s useful:
- Technical SEO. Identify categories, tags, or specific sections of a site.
- Targeted content. Find articles inside a specific URL structure (e.g.,
inurl:reviews "product X").
9. before: / after: (Date range)
Restricts results to a specific timeframe. These are two of the few operators Google officially documents, and Google notes you can combine them to search within a date range.
- Usage:
"AI search" after:2024-01-01 before:2024-12-31 - Why it’s useful:
- Trend analysis. Watch how a topic evolves over time.
- News and event tracking. Pull recent coverage of a launch or incident.
- Freshness. Filter out stale results.
Pair these with time-based parameters like tbs=qdr:d for finer control.
10. related: (Find similar sites)
Finds websites that are similar in content or audience to a given URL.
- Usage:
related:nytimes.com - Why it’s useful:
- Competitor discovery. Find peers you didn’t know about.
- Link building. Identify outreach targets.
- Audience expansion. Locate other content hubs your audience reads.
11. intext: / allintext: (Keyword in body text)
Finds pages containing your keyword(s) anywhere in the body copy, not just the title or URL.
- Usage:
intext:"schema markup" SEO(finds pages whose body text contains the exact phrase “schema markup”) allintext:requires all subsequent words to appear in the body:allintext:core web vitals audit- Why it’s useful: forces a term into the actual content rather than the metadata, which cuts thin pages that only mention the keyword in the title.
12. AROUND(X) (Proximity search)
Finds pages where two terms appear within X words of each other.
- Usage:
SEO AROUND(5) tools(matches pages where “SEO” and “tools” sit within 5 words of each other) - Why it’s useful: looser than exact match, tighter than two loose terms. Useful for contextual relevance.
- Caveat:
AROUND(X)is undocumented and returns inconsistent results — Ahrefs classifies it as an unreliable operator rather than a fully supported one, so verify the output before trusting it at scale.
How to exclude a website from Google search
Excluding a site or domain from search results is the single most-asked operator question, so it gets its own section. Three patterns cover everything you need.
Exclude one website with -site:
The minus operator combined with site: removes results from a specific domain.
"best running shoes" -site:reddit.com
This returns running-shoe content excluding every page on reddit.com. Read it as: “find best-running-shoes results, then omit anything where the URL is on reddit.com.”
Exclude multiple websites at once
Repeat the -site: pattern for each domain you want to drop.
"best running shoes" -site:reddit.com -site:quora.com -site:youtube.com
There’s no upper limit. SEO teams routinely chain 5–10 exclusions to filter out aggregator and forum noise on commercial queries.
Exclude a whole top-level domain
Use a TLD as the value to drop a whole class of sites.
"climate report" -site:.gov -site:.edu
Returns climate reports, excluding government and university domains. Useful when you specifically want commercial or news perspectives.
Variants that mean the same thing
People search for site exclusion using several phrasings. They all map to the -site: operator:
- “exclude website from google search”
- “google search exclude site” / “google search omit site”
- “how to exclude a website from google search”
- “exclude domains from google search”
The query is always keyword -site:domain.com. The minus must touch the operator with no space (-site: not - site:).
Excluding a URL path (not a whole site)
If you want results from a domain but excluding a specific path, combine site: and -inurl::
site:example.com SEO -inurl:/blog/
Returns example.com’s SEO pages excluding anything under /blog/. Useful when a competitor’s blog dominates and you want to surface their landing pages instead.
Search syntax, commands, arguments — the same operators by different names
If you’ve been searching for google search syntax, commands for google search, google search arguments, or google search shortcuts, you’ve been searching for the same thing as “Google search operators”. Different communities use different terms:
| Term | Where you’ll see it |
|---|---|
| Operators | Google’s official docs, most SEO writing |
| Commands | Power-user / hacker community |
| Syntax | Developer-leaning content |
| Arguments | Borrowed from CLI / programming terminology |
| Shortcuts | Casual / consumer-facing content |
The full set is the same: site:, intitle:, allintitle:, inurl:, allinurl:, intext:, allintext:, filetype:, before:, after:, related:, define:, weather:, stocks:, plus the punctuation operators "", -, *, OR, AROUND(N), (). A handful of once-common Google search operators — link:, cache:, +, ~, and info: — have been retired and no longer work; the next section covers which died when.
For the parameter side of search refinement (URL-level controls like &gl=us, &hl=en, &udm=14), see the companion guide on Google search parameters.
Deprecated Google search operators to skip
Several Google search operators that older guides still list have been retired. Chasing them wastes time, and some return stale or partial data that looks valid but isn’t. Here’s what died and when.
| Operator | What it did | Status |
|---|---|---|
link: | Listed pages linking to a domain | Dropped in 2017 |
info: | Showed Google’s info card for a URL | Dropped in 2017 |
~ (tilde) | Auto-included synonyms | Dropped in 2013 |
+ (plus) | Forced an exact word | Dropped in 2011 |
cache: | Opened Google’s cached copy of a page | Removed in 2024 |
The link:, info:, ~, and + operators were all quietly retired years ago; Ahrefs documents each deprecated operator and the year it stopped working in its operator reference.
The cache: operator is the most recent casualty. Google removed the cached-page link from search results in February 2024, and Search Engine Journal reported that the cache: operator itself was retired shortly after. Google’s Search Liaison, Danny Sullivan, confirmed the change, calling it “one of our oldest features” and pointing users toward the Internet Archive’s Wayback Machine for historical snapshots instead.
If you need a page’s earlier state now, skip cache: entirely and go straight to the Wayback Machine or a SERP API that stores its own historical results.
Combining Operators for Power Searches
Google search operators get more interesting once you stack them.
Example 1: Find unlinked brand mentions on news sites.
"Your Brand Name" -site:yourdomain.com site:news.google.com
Finds Google News mentions of your brand that aren’t on your own website.
Example 2: Discover competitor content gaps.
site:competitor.com intitle:"how to" -inurl:2023
Searches a competitor’s site for “how to” articles, excluding anything published in 2023.
Example 3: Whitepapers on AI ethics from non-profits.
"AI ethics" filetype:pdf (site:org OR site:edu) intitle:report
Targets authoritative documents on a niche topic.
Localizing Google search results
There is no first-class operator for changing your search location in 2026. The historical loc: operator stopped working reliably around 2020, and Google has been consolidating geo-control into URL parameters instead.
To run a search as if you were in a different city or country:
- Country-level: append
&gl=<country-code>to the URL (&gl=us,&gl=fr,&gl=jp). - Language-level: append
&hl=<language-code>(&hl=en,&hl=de). - City-level: Google’s web UI doesn’t expose this, but city-level SERPs are accessible via the SERP API by passing a
locationfield with a Google canonical geotarget (e.g.,"Austin,Texas,United States").
For details on every URL parameter (geo, language, time, device, AI mode), see the companion Google search parameters guide. For programmatic city-level results across Google’s ~100,000 supported locations, the local rank tracking page documents the API call shape.
Practical use cases
A few places Google search operators earn their keep:
- SEO audits. Spot indexed pages, canonical issues, duplicate content, or accidentally exposed admin paths (e.g.,
site:yourdomain.com inurl:admin). - Content research. Find unique angles, expert sources, and competitor strategies.
- Lead generation. Locate prospects by job title, company type, or problems they post about.
- Competitive analysis. Measure competitor content volume, keyword targeting, and platform presence.
- Reputation management. Track brand mentions across specific sites or timeframes.
- Link building. Surface guest post opportunities (
"write for us" intitle:blog) or resource pages ("industry statistics" inurl:resources).
Common mistakes with Google search operators
Most failed queries come down to a handful of syntax slips. A few to watch for:
- Spaces after the colon. Google search operators like
site:andintitle:must touch their value with no space:site:cloro.devworks,site: cloro.devdoes not. - Lowercasing
OR. TheORoperator only works uppercase. A lowercaseoris treated as a normal search word. - Mixing
allin…operators with other operators.allintitle:andallinurl:grab every word that follows them, so combining them withsite:orfiletype:usually breaks the query. Use the single-termintitle:/inurl:versions when you need to stack. - Trusting dead operators. As covered above,
link:,cache:,+, and~no longer return reliable results — if a tutorial leans on them, it’s out of date. - Expecting exact result counts. Google’s reported result totals are estimates, so operators are for finding pages, not for precise counting.
When a search behaves oddly, strip it back to a single operator, confirm that one works, then add the next. Google search operators fail silently rather than throwing errors, so isolating them one at a time is the fastest way to debug a stacked query.
Tools to master operators
- Google Search bar. Practice directly in Google.
- Browser extensions. Tools like “Advanced Search Operators” help build or highlight operator usage.
- SEO platforms (Ahrefs, SEMrush). Most bake operator logic into their site explorers and content gap features.
- cloro. Programmatic execution of complex queries with structured output, including AI Overviews. Useful when you need to combine operator precision with geolocation parameters or AI features.
Google search operators work for one-off checks. For continuous monitoring, see how to track ranks on SERP automatically.
Beyond manual search: automation with cloro

Typing operators by hand stops working once you need to run hundreds or thousands of queries. That’s where scraping tools come in.
Platforms built for scraping Google Search results apply these operators internally and return filtered data.
cloro takes the operators and parameters covered above and runs them at scale, returning structured data. Whether you’re auditing all indexed pages with a specific title keyword or watching for negative brand mentions across news sites, you can pair traditional SERP data with AI visibility tracking in the same workflow.

About the author
Ricardo Batista
Founder, cloro
Ricardo is one of the founders and engineers behind its SERP and AI-search scraping infrastructure. Before cloro he scaled a financial comparison site to $7M ARR and ran the full-country operations of a unicorn to $65M ARR, then went back to building. He writes about search engine scraping, generative-engine optimization, and turning live search and AI-answer data into something teams can act on.
Frequently asked questions
What are Google Search Operators?+
Special commands (like `site:`, `filetype:`, `intitle:`) that you add to your search query to filter and refine the results. They're also called Google search syntax, search arguments, or search shortcuts — same thing, different terminology.
How do I exclude a website from Google search?+
Use the minus operator with the `site:` operator: `keyword -site:domain.com`. For example, `"best CRM" -site:salesforce.com` returns CRM results excluding salesforce.com. To exclude multiple domains, repeat the pattern: `keyword -site:domain1.com -site:domain2.com`.
What are Google search commands and how are they different from operators?+
They're the same thing. "Commands", "operators", "syntax", and "arguments" are interchangeable terms for the special characters and keywords (`site:`, `filetype:`, `intitle:`, `before:`, etc.) you add to a Google search to filter results. The official Google documentation calls them "search operators"; the community uses "commands" and "syntax" interchangeably.
Are search operators free?+
Yes, they are built into Google Search. However, using them aggressively via automated scripts can trigger CAPTCHAs.
Can I combine operators?+
Absolutely. For example, `site:nytimes.com intitle:AI filetype:pdf` finds PDF files about AI specifically on the NYTimes website.
What is the difference between search operators and parameters?+
Operators (`site:`) are typed directly into the search bar to refine results, while parameters (`&gl=us`) are appended to the URL to control backend settings like location or language. See Google search parameters for the parameter side.
How can I use operators to find content gaps?+
You can search `site:yourcompetitor.com keyword -site:yourdomain.com` to see what topics your competitors rank for that you don't yet cover.
Does Google support search localization operators?+
Not as a search-bar operator — geolocation lives in the URL parameter `&gl=
Related reading

How to Scrape Google Search Results With Python (2026)
Learn how to scrape Google search results with Python, Playwright, or a SERP API. Compare HTML parsing, browser automation, and anti-bot risk.

Google Search Parameters: 2026 URL Guide for Scrapers
The complete guide to Google search parameters — gl, hl, uule, udm, tbs — to control location, language, time filters, and AI Overviews when you scrape at scale.

How to Scrape Gemini: API, URL Context, and Web UI
Learn how to scrape Gemini with the API, URL context, or web UI automation. Compare structured outputs, citations, and anti-bot trade-offs clearly.