Parameters
The operators go inside
query. Search operators in the API reference lists each one with its exact rules.
Search two sites for an exact error string
This sample searches GitHub and Stack Overflow in one request for pages that contain the exact phraseother side closed, and prints the host and URL of each result. It runs with no API key:
github.com or stackoverflow.com. This run was made on 19 November 2026:
Example output · results vary
OR binds only the two site: terms next to it, so connection pool timeout and the quoted phrase apply to both sites.
Build a query
Start from a plain-language description, then add one operator per hard rule:
A word with no operator is never a hard filter. To require a word, quote it.
Operator or parameter
Some filters exist both as an operator and as a request parameter. Keep each kind of filter in one place:
See Filter by domain for the
site and exclude_domains parameters in depth.
Common mistakes
A query that doesn’t parse never fails. An unbalanced quote or parenthesis, or a dangling
OR, is read as plain words, and the search still runs.
In the SDKs, CLI and MCP
Operators are part of the query string, so every client takes them unchanged: the first argument ofsearch in each SDK, the query argument of keenable search in the CLI, and query in the MCP tool search_web_pages (see MCP server).
API reference
- Search operators: every operator and its rules.
- Search request:
query,siteandexclude_domainsin full. - Write the query: describe the page you want before you add operators.