Google Search Operators: The SEO Guide to site:, intitle: & More

What Google search operators are and why SEOs use them

Google search operators like site:, intitle:, or quotation marks turn a guess about indexing or rankings into a direct, verifiable query. Instead of scrolling through normal results hoping to spot a pattern, you type a query that answers the question directly: is this page indexed, who else is targeting this phrase, what's competing with my title tag. For SEO work, operators replace a handful of manual checks with a single targeted search you run from any browser. They don't replace tools like Google Search Console or a crawler for full-site audits — they're for spot-checking one page or one query without opening anything else. Understanding how operators fit into the bigger picture of crawling and indexing is easier if you've read how search engines work first, since operators are really just filtered views into that same index.

Using site: to check what's indexed for a domain

The site: operator shows which pages Google has indexed for a given domain, and it's the fastest way to catch indexing problems before they show up as lost traffic. Typing site:example.com returns a rough list of indexed URLs for that domain — useful for confirming a new page made it into the index after publishing, or for spotting pages that shouldn't be there, like staging URLs or old category pages you thought were removed. The count Google shows is an approximation, not an exact figure, so don't use it as a precise index-size metric; treat it as a directional signal, not a KPI to report on.

Combining site: with a keyword tells you whether a specific page's indexed content actually contains the phrase you're trying to rank it for, which is a faster gut-check than opening the page and running Ctrl+F. A query like site:example.com "running shoes" shows whether that exact phrase appears anywhere on the indexed version of the domain — if it doesn't show up at all, the page likely needs the content rewritten before you troubleshoot why it isn't ranking. This is also the first thing to check after a migration: running site: against the old and new domain structure can surface whether old URLs are still being served instead of the new ones, a common cause of the crawl waste covered in the guide to how Googlebot crawls your site.

Using intitle: and inurl: to find pages targeting a term

The intitle: and inurl: operators restrict results to pages where a word appears in the title tag or the URL, which makes them the fastest way to see who's directly targeting a keyword rather than just mentioning it. Running intitle:"content audit template" returns only pages with that exact phrase in the title tag — a clean way to see how many competitors have built a dedicated page around a term, versus pages that just reference it in passing. This is a quick substitute for a full SERP title scan when you're scoping out keyword difficulty before committing to a content brief.

inurl: does the same job for URL slugs, and it's particularly useful for auditing your own site's structure. Searching inurl:category site:example.com can reveal every category-type URL Google has indexed, which helps catch duplicate or near-duplicate category pages created by faceted navigation or filtering parameters — a common technical issue covered in more depth in technical SEO basics. Combine the two with allintitle: or allinurl: if you need both conditions matched at once, though these stricter variants return fewer, more exact-match results and are worth testing before you build a recurring check around them.

Using exact-phrase quotes to match precise wording

Wrapping a phrase in quotation marks forces Google to match that exact wording instead of treating each word as a separate, loosely related term. This matters for SEO in two main situations: checking duplicate content, and checking phrase-level ranking targets. If you suspect a paragraph has been scraped or syndicated without permission, searching "the exact sentence from your page" will surface every site where that string appears verbatim — a fast way to confirm plagiarism before escalating it, and related to the kind of abuse described in what is negative SEO. For keyword work, quoting a target phrase like "best running shoes for flat feet" shows you only pages built around that precise phrasing, which is a sharper competitive view than a broad match search that pulls in tangentially related pages.

Quotes are also the quickest way to confirm whether Google is actually indexing a specific string of text on your own page — useful when you've just published new copy and want to confirm it was crawled and parsed as expected, rather than blocked by rendering issues covered in the primer on server-side rendering SEO.

Using the minus operator to exclude irrelevant terms

The minus operator — a hyphen directly before a word, with no space — removes results containing that term, and it's the cleanest way to cut noise out of a competitive or diagnostic search. A query like running shoes -nike strips out every result mentioning Nike, which is useful when a dominant brand is crowding out the smaller competitors or informational pages you actually want to study. For SEO diagnostic work, pairing exclusion with site: helps isolate a subsection of a domain: site:example.com -site:example.com/blog returns indexed pages outside the blog folder, a fast way to check whether non-blog sections are being indexed as expected without manually filtering a longer list.

The minus operator is also handy when a brand name or common term is polluting a site: or intitle: check — for example, excluding a recurring boilerplate phrase that appears in every page title, so you can isolate the pages where the title actually differs. It's a small operator, but it's the difference between a query that gives you a clean, scannable result set and one buried in irrelevant matches.

The related: operator returns domains Google considers topically similar to the one you specify, which makes it a quick way to map a competitive landscape without a dedicated competitor-research tool. Searching related:example.com surfaces sites Google groups with that domain, which can turn up competitors you hadn't considered, especially in niches where the obvious big players aren't the only relevant comparison. It's worth noting that related: has become less reliable over time and sometimes returns no results at all for smaller or newer domains, so treat it as a rough starting point for competitor discovery, not a dependable recurring check.

Why Google operator behavior can change without notice

Google can alter, restrict, or quietly deprecate how any search operator behaves at any time, without announcing it, because operators were built as debugging and discovery tools for Google's own index, not as a stable public API with a support contract. The related: operator's declining reliability is a documented example of this drift, and operators like info: and some forms of link: have already been scaled back or removed in past years. The practical implication: never wire an operator-based check into an automated or recurring workflow — a script, a monthly report, a client deliverable — without re-verifying that the operator still behaves the way you expect at the time you run it. A query that returned a clean, countable result set last quarter can silently return something different, or nothing at all, with no warning in between. For anything you need to monitor continuously rather than spot-check, pull the data from Google Search Console or a dedicated crawler instead, and save operators for the manual, one-off checks they were actually designed for.

Google search operators cheat sheet: the checks worth memorizing

Operator checks by task

1
Is this page indexed?
site:example.com/page-url
2
Does this page target this phrase?
site:example.com "exact phrase"
3
Who else has built a page around this term?
intitle:"exact phrase"
4
What does my indexed URL structure look like?
inurl:folder-name site:example.com
5
Has this content been copied elsewhere?
"exact sentence from the page"
6
How do I cut a dominant term out of the results?
keyword -excluded-term
7
Who's topically similar to this domain?
related:example.com

Each recurring SEO question maps to one operator to run.

The operators worth keeping on hand are site:, intitle:, inurl:, exact-phrase quotes, the minus sign, and related:, and each maps to one of five recurring SEO questions: indexing status, title/URL targeting, exact-phrase matching, noise exclusion, and competitor discovery. The list below pairs each question with the exact operator to run, so you can reach for one by task rather than by trying to remember its name:

Is this page indexed? → site:example.com/page-url
Does this page target this phrase? → site:example.com "exact phrase"
Who else has built a page around this term? → intitle:"exact phrase"
What does my indexed URL structure look like? → inurl:folder-name site:example.com
Has this content been copied elsewhere? → "exact sentence from the page"
How do I cut a dominant term out of the results? → keyword -excluded-term
Who's topically similar to this domain? → related:example.com

Google search operators full list: what else is worth knowing

Beyond the operators covered in depth above, five more — filetype:, cache:, OR, the wildcard, and AROUND(X) — come up often enough in SEO work to name directly, even though each carries a caveat that keeps it a secondary tool rather than a daily one:

filetype: — restricts results to a specific file format, useful for finding indexed PDFs, spreadsheets, or slide decks on a domain, e.g. filetype:pdf site:example.com.
cache: — in many regions this no longer reliably returns Google's cached version of a page, so verify it still works before relying on it.
OR — broadens a query to match either term, e.g. "running shoes" OR "trainers", useful for phrase variants across regions.
* — acts as a wildcard placeholder inside a quoted phrase, useful for finding variations of a known phrase structure.
AROUND(X) — an undocumented proximity operator some SEOs use to test how close two terms appear to each other, though support for it is inconsistent and shouldn't be treated as stable.

This isn't an exhaustive list of every operator Google has ever supported — some, like parts of link:, have already been scaled back — so treat any operator not covered in detail above as unverified until you've tested it yourself against a current query. There's no official "google search operators full list pdf" that Google maintains and keeps current, which is itself a reason to lean on a short, re-tested working list instead of a static document.

Frequently asked questions

Is there a Google search operators PDF worth downloading?

A downloadable PDF isn't necessary for most SEO work, since the operator set that's actually reliable is small enough to keep as a short bookmarked list rather than a static document. The bigger risk with a PDF cheat sheet is that it goes stale the moment Google changes operator behavior, and a static file won't warn you when that happens the way a live, re-tested query will. If you want something portable, copy the task-based list from this guide into your own notes rather than relying on a third-party PDF that may already be out of date.

What's different about Google search operators in 2026 versus earlier years?

Nothing about the core syntax has changed on a fixed schedule — site:, intitle:, inurl:, quotes, the minus sign, and related: have been part of Google's search syntax for years, but their reliability has drifted gradually rather than all at once. related: and cache: have become noticeably less dependable, and operators like info: have been pulled back or removed entirely in past years. There's no fixed yearly changelog Google publishes for this, which is exactly why the re-verification habit matters more than memorizing a list: test the operator against a live query before you build a workflow around it, rather than assuming this year's behavior matches what you read in an older guide.

Can Google search operators replace Google Search Console for checking indexing?

Operators give a fast, approximate spot-check, but they can't replace Search Console's exact, verified indexing data tied to your own property. The site: count is Google's own estimate and can be noticeably off from the real indexed total, so use it to answer "is this roughly in the index" quickly, then confirm anything that actually matters — a missing page, a sudden drop — in Search Console's coverage report, which draws from the same crawling and indexing pipeline described in how search engines work.

Do Google search operators work the same way on mobile and desktop search?

Operator syntax itself doesn't change between mobile and desktop, but results can differ because Google evaluates mobile and desktop versions of a page under mobile-first indexing, so a site: or exact-phrase check run from a mobile browser may reflect a slightly different rendered version than the one you see on desktop. If a page behaves inconsistently across devices in an operator search, it's worth checking whether the mobile and desktop versions are actually serving equivalent content.