Skip to content
Go back

Search Google Like a Pro. site:, filetype:, and Other Operators That Actually Work

Updated:
Edit Views

Table of contents

Open Table of contents

Introduction

For a long time I searched Google the same way everyone does: two or three words, scroll through whatever came back, open five tabs, close four of them. Then I added filetype:pdf to a query and the PDF spec I’d been hunting through blog summaries appeared in the first result.

That was embarrassing and useful in equal measure.

This guide covers the operators that work in 2026, with examples you can copy. No deprecated commands that old SEO articles still recommend. Just the queries that actually filter results.

The One Rule That Breaks Half Your Queries

Before anything else: no space after the colon.

That single space tells Google you’re searching for the literal word “site:” as a keyword. The operator doesn’t fire. This applies to every operator in this guide filetype:, intitle:, inurl:, all of them.

Yes No Your query Space after colon? Operator ignored Operator active
The One Rule That Breaks Half Your Queries

The Core Operators

site: — Search Inside One Domain

Restricts results to a single domain. Useful when the site’s own search is weak, missing, or doesn’t surface older content.

You can also scope it to a subdomain or a specific path:


filetype: and ext: — Find Specific File Formats

Forces Google to return only results of a specific document type. Most people skip this one entirely, which is a shame.

ext: works the same way.

Common formats that work reliably: pdf, doc, docx, xls, xlsx, ppt, pptx, txt, csv. Do you need more formats? Check this out Common media types

Government and university websites frequently publish spreadsheets and reports that never appear in normal search results. site:*.gov filetype:pdf or site:*.edu filetype:pdf is a fast way to find primary sources.


- — Exclude Words or Domains

The minus sign removes results that include a specific word. One of the cleanest ways to filter noise.

You can also exclude entire domains:

This is especially useful when you want official documentation but searches keep surfacing forum threads and blog summaries instead.


"quotes" — Exact Phrase Match

Forces Google to match the phrase exactly, in that word order. No synonyms, no rearranging.


OR and | — Either This or That

Searches for results matching one term or the other. Must be uppercase OR.

The pipe | does the same thing.


intitle: and allintitle: — Words in the Page Title

intitle: requires the word to appear in the <title> tag. allintitle: requires all words in the title.


inurl: and allinurl: — Words in the URL

Searches for terms inside the URL itself, not the page content. Pages are often categorized by their URL structure (/blog/, /docs/, /api/), so this is a fast way to find the right section.


before: and after: — Filter by Date

Filters results by publication or indexation date.


* — Wildcard

Substitutes an unknown word in a phrase.

Useful when you remember the structure of a phrase but not the exact wording.


.. — Number Range

Finds values within a numeric range. Works for prices, years, version numbers.


How to Build Combined Queries

Single operators are useful. Combinations are where things get precise. Here’s how the pieces fit together.

Show spoiler
Yes No Yes No Yes No Yes No Yes No Specific domain? site:domain.com Skip Specific format? filetype:type Skip Exact match? "quotes" Skip Time bounds? before/after Skip Noise to remove? -noise Skip Your Query
How to Build Combined Queries

Quick Reference Table

GoalOperatorExample
Limit to one sitesite:site:developer.mozilla.org fetch
Specific file formatfiletype:filetype:pdf security checklist
Exact phrase"...""cannot find module"
Exclude a word-react tutorial -hooks
Either of two termsORdocker OR podman
Word in titleintitle:intitle:"write for us"
Word in URLinurl:inurl:blog astro
After a dateafter:after:2025-01-01
Before a datebefore:before:2024-06-01
Wildcard word*"how to * in react"
Number range..laptop 700..1000 usd

What No Longer Works in 2026

A lot of older articles still list operators that have been quietly removed. Worth knowing so you don’t waste time debugging a dead query.

Where Operators Are Actually Useful

A few real workflows where search operators save meaningful time:

FAQ

Can I combine multiple operators in one query? Yes, and that's where precision comes from. Start with one or two, check results, then add more. Stacking too many at once can return zero results because the criteria conflict.
Why does site: show a weird number of results? Google's result count for site: queries is an estimate, not an exact count. It's often wrong. Use it to get a rough sense of scale, not a precise figure.
Do operators work in Google Image Search? Some do. site: and filetype: work. intitle: in Image Search looks for the term in the image filename. Results are less consistent than in web search.
Does Google's AI Overview affect operator results? AI Overviews appear above results but operator queries still filter the blue-link results below. The filtering behavior hasn't changed, though AI Overviews push those results further down the page.

Conclusion

Five operators handle most situations: site:, filetype:, "quotes", -, and OR. Learn those and searches get a lot quieter. Add intitle:, inurl:, before:, and after: when you need another layer.

The gap isn’t knowing these exist, it’s having them ready when a search is producing garbage. Two or three operators chained together lands you on the right result instead of page three.

Copy two or three templates from the table above, swap in your own topics, and try them today. You’ll notice the difference immediately.


Share this post on:

Previous Post
Husky and Conventional Commits — How to use Git Hooks Without the Pain
Next Post
Docker Base Images — bookworm-slim, alpine, distroless, and Chainguard Wolfi