Search engine query language

Search engine query language refers to special operators for refining search: site:, intitle:, inurl:, filetype:, and others. Used by SEO specialists for auditing, competitor research, and keyword analysis.

In brief

Search engine query language is a set of special operators (commands) for refining search queries: restricting search by domain, title, URL, file type, or word presence in text. Used for SEO audits, competitor research, and link building opportunity discovery.

What is search engine query language

Search engine query language is a set of special operators that refine and restrict search queries. Instead of plain text, you add operators that give Google or Yandex precise instructions: search only on a specific site, only in page titles, only in URLs, or only in files of a certain type.

SEO specialists use operators daily: to verify site indexing, find duplicate content, analyze competitors, detect technical issues, and discover link placement opportunities. Mastering query language is a fundamental technical SEO skill.

Google regularly changes or limits supported operators. Some operators work precisely (site:), others work as filters (intitle: accounts for synonyms). Always verify operator behavior in current documentation.

Main search engine operators

site:example.com
Shows pages from Google's index for the specified domain only. Use to check the number of indexed pages.
intitle:word
Finds pages where the specified word is in the title tag. All words in title: allintitle:word1 word2.
inurl:word
Finds pages where the word appears in the URL. Use to find pages by URL structure.
intext:word
Finds pages where the word appears in the page's content text.
filetype:pdf
Restricts search to specific file types: pdf, doc, xls, ppt.
"exact phrase"
Searches for an exact phrase match — words must appear in the specified order.
-word
Excludes a word from search results.
OR (|)
Finds pages containing one OR another word: seo OR optimization.

Practical SEO uses for operators

  • Index check: site:example.com — how many pages are indexed. Too many or too few signals a problem
  • Duplicate detection: site:example.com intitle:"page title" — are there pages with identical headings
  • Competitor analysis: site:competitor.com inurl:/blog — only the competitor's blog section pages
  • Guest posting: "guest post" + niche + intitle:"write for us" — finding platforms for guest content
  • Broken link building: site:resource.com inurl:resources filetype:html — resource pages for link building
  • Brand mention check: "brand name" -site:yoursite.com — unlinked mentions

Advanced operator combinations

  • site:example.com -inurl:https — HTTP pages on an HTTPS site (potential migration issues)
  • site:example.com intitle:"index of" — open directories on the server
  • related:competitor.com — sites similar to a competitor (for link building)
  • cache:example.com/page — Google's last cached version of a page
  • "powered by wordpress" site:.edu inurl:blog "write for us" — multi-level combination for finding platforms

Yandex operators

Yandex supports similar but not identical operators:

site:example.com
Same as Google — site pages in Yandex's index.
url:example.com/page
Exact page URL in Yandex's index.
title:word
Word in the title (equivalent to intitle:).
host:example.com
All pages of a specific host, including subdomains.

Common questions

site: shows only pages in Google's index. If there are fewer than expected — there may be indexing issues: noindex directives, robots.txt blocks, duplicate content, or page quality problems. Use Google Search Console for accurate data.
Partially. site:, intitle:, inurl: are supported by Yandex, but with behavioral differences. Yandex also supports url: and host: operators that don't exist in Google. Test each operator in the specific search engine.
This is a Google dorking technique. Example: intitle:"admin login" site:example.com — finds login pages on a site. Used in ethical hacking and SEO audits to check technical page accessibility. Never use for unauthorized access.
No technical limits, but excessive operator-based queries can trigger CAPTCHAs from Google. For bulk checks, use Screaming Frog, Ahrefs, or the Google Search Console API instead of manual searching.
Direct contacts

Discuss your project?

Share your goals and website context — I will suggest a practical next step.