Google Search Commands Guide: Operators, Syntax, and Advanced Dorking
The reference manual for search engineers: boolean operators, scope syntax across URL, title, and body, Julian dates, and wildcard filtering.
1. Base Operators and Boolean Logic
Base search operators alter query parser tokenization and weighting before issuing index lookups:
+: mandatory inclusion flag (prevents discarding common stopwords such as articles or conjunctions). Example:+the network.-: boolean negation. Purges documents containing the subsequent term or command. Example:database -oracle."": exact phrase matching. Mandates strict word sequence and positional adjacency. Example:"distributed systems".*: wildcard placeholder. Replaces one or more unspecified tokens within phrase queries. Example:"enterprise * architecture"...: numeric continuous range. Scopes results within continuous numeric thresholds (years, metrics, prices). Example:report 2004..2008.OR(or|): boolean disjunction. Retrieves documents containing either operand. Example:postgresql OR mysql.
2. Index State Commands: site, cache, link, and related
These commands query engine state tables directly:
site:: restricts document retrieval to an exact domain or subdomain hierarchy. Essential for crawling volume verification and orphaned asset discovery. Example:site:kerouac3001.com.cache:: delivers the exact HTML snapshot captured during the crawler's latest indexing pass, crucial for verifying rendered text discrepancies. Example:cache:kerouac3001.com.link:: legacy operator querying a representative subset of crawled inbound hyperlinks. Example:link:kerouac3001.com.related:: extracts entities identified as structurally and semantically adjoining in classification graphs. Example:related:slashdot.org.info:: returns core index metadata recorded for a specified canonical URL.
3. Scoping Operators: title, url, text, and anchor
Scoping operators confine lookups to isolated document partitions:
| Scoped Operator | Global Operator | Target Field | Syntax Rules |
|---|---|---|---|
intitle: | allintitle: | <title> tag | intitle: binds strictly to the first word; allintitle: binds the full query |
inurl: | allinurl: | URL string | Evaluates matches strictly across URI path segments |
intext: | allintext: | Body text (<body>) | Ignores document metadata, titles, and URI components |
inanchor: | allinanchor: | Link anchor text | Queries text within incoming hyperlink citations |
Critical Syntax Rule: never insert whitespace between the colon : and the subsequent argument (valid: inurl:admin, invalid: inurl: admin).
4. Specialized Operators: filetype and daterange (Julian Dates)
Specialized operators allow strict filtering across file MIME types and crawl acquisition timestamps:
filetype:(orext:): restricts retrieval to binary document formats (pdf,doc,xls,txt,xml). Example:audit filetype:pdf.daterange:: isolates pages crawled within a designated chronological window. The command rejects standard Gregorian dates (DD/MM/YYYY) and strictly requires Julian Day Numbers (JDN):
Syntax: daterange:2454041-2454071
Query construction requires converting start and end dates via astronomical Julian conversion tables, enabling precision auditing of freshness and discovery velocity.