After this lesson you should be able to
- Use the operators that still work and avoid those that no longer do
- Build query sets for resource pages, roundups and directories
- Combine operators to isolate page types rather than topics
- Recognize where operator-based prospecting misleads you
Why operators still matter
Link tools show you pages that already have links. Search operators show you pages that exist. That distinction is the whole argument for learning them.
A resource page that has been linked to by four of your competitors is, by definition, already known to everyone with a tool subscription. A resource page nobody has pitched is invisible to link tools precisely because it is unworked. Operators are how you find the second kind, and the second kind converts better because the editor has not received the same email forty times this month.
Two honest caveats before the patterns. First, operators are approximations. Google matches them loosely, ignores some of them under some conditions, and caps how many results it will return regardless of how many exist. Treat the result count as decorative. Second, operator prospecting is manual work by design. If you find yourself wanting to automate thousands of queries against a search engine, you are heading for blocks, distorted results, and terms-of-service problems. The technique works at the scale of a person clicking.
The operators worth knowing
These are the ones that still earn their place. Everything else is either deprecated, unreliable, or a novelty.
| Operator | What it does | Example |
|---|---|---|
site: | Restricts results to a domain or TLD | site:harvard.edu |
inurl: | Requires a string in the URL | inurl:resources |
intitle: | Requires a string in the page title | intitle:"useful links" |
allintitle: | Requires every following term in the title | allintitle: rose care resources |
| Quotes | Exact phrase match | "recommended reading" |
- | Excludes a term, domain or pattern | -inurl:blog -site:pinterest.com |
OR | Either term; must be uppercase | intitle:resources OR intitle:links |
* | Wildcard inside a quoted phrase | "best * for beginners" |
filetype: | Restricts to a file extension | filetype:pdf |
Parentheses group terms, and they matter more than people expect: (intitle:resources OR intitle:links) "beekeeping" behaves quite differently from the same query without them.
Deprecated or unreliable, and worth knowing so you stop wasting queries on them: inanchor: and allinanchor: no longer behave predictably, related: has become unreliable and returns little of value, the + operator was retired, and the ~ synonym operator is gone. Date-range operators exist in the interface as tools rather than as query syntax, and the interface version is the one to use.
Queries for resource pages
A resource page is a page whose editorial purpose is to link out. That makes it the highest-intent prospect type there is: you are not persuading someone to link, you are asking to be considered for a list they already maintain.
The pattern is always the same — one topic term, one page-type signal, one or more exclusions. Substitute your own topic for the examples.
"beekeeping" (intitle:resources OR intitle:"useful links")"beekeeping" inurl:resources -inurl:blog -inurl:category"beekeeping" intitle:links inurl:links"beekeeping" "recommended websites" -"add url" -"submit""beekeeping" ("helpful resources" OR "further reading" OR "other sites")site:.gov "beekeeping" inurl:resourcessite:.edu "beekeeping" (intitle:resources OR inurl:links)
Two refinements. The exclusion -"submit your site" or -"add your link" removes the low-value pages that will list anyone; whether you want that depends on the campaign, but you should decide deliberately rather than by accident. And the -inurl:blog -inurl:category -inurl:tag trio removes the enormous volume of blog archive pages that happen to contain your topic word, which is otherwise most of what you get.
Vary the topic term as well as the page-type term. Practitioners use different vocabulary from marketers — a page about apiculture will not surface for beekeeping, and the apiculture page is usually the better prospect.
Queries for roundups and directories
Link roundups are recurring posts that collect the week's or month's best links in a niche. They are a genuinely underused prospect type because they have a standing content need, which means the ask is welcome rather than imposed.
"beekeeping" (intitle:"link roundup" OR intitle:"weekly roundup")"beekeeping" ("this week in" OR "best of the week") inurl:blog"beekeeping" intitle:roundup -inurl:tag"beekeeping" "link roundup" inurl:2026"beekeeping" ("friday roundup" OR "monday roundup" OR "weekly digest")
The inurl: year filter is the one that matters. A roundup series that stopped three years ago is not a prospect, and roundup pages are unusually prone to looking alive when they are not. Check the most recent instalment before you add the domain to anything.
Directories and association listings deserve a warning first. General-purpose web directories that accept anyone are, at best, worthless, and I have watched sites carry hundreds of them with no measurable effect. The directories worth pursuing are ones with a membership qualification: trade associations, professional bodies, accreditation schemes, regional business bodies, supplier lists maintained by manufacturers.
"beekeeping" (intitle:"member directory" OR intitle:"find a")"beekeeping association" inurl:members"beekeeping" ("our members" OR "member list") -inurl:login"beekeeping" ("approved suppliers" OR "authorized dealers" OR "where to buy")site:.org "beekeeping" inurl:directory
The test for a directory is simple: could anyone with a credit card get listed? If yes, skip it. If listing requires being a real business in a real category, it is worth the application.
Operators for broken links and for finding people
Broken link building starts with the same resource-page queries, because a resource page maintained for a decade is where dead links accumulate. Find the pages first with the patterns above, then run a link checker across them; there is no operator for is this link broken, and any claim otherwise is wishful.
A related pattern finds pages about a resource that no longer exists, which is the other half of the tactic:
"beekeeping" ("page not found" OR "404") inurl:resources"defunctsite.com" -site:defunctsite.com
That second query is also the core of unlinked mention work and of contact discovery. To find who writes about a subject rather than what:
site:example.com "by" inurl:authorsite:example.com (inurl:author OR inurl:staff OR inurl:team)"@example.com" -site:example.comsite:example.com "contributing editor" OR "staff writer"
The third one is worth understanding. It looks for the domain's email pattern appearing anywhere on the open web — conference speaker pages, academic papers, press releases, GitHub commits. It will not find you a specific person's address, but it frequently reveals the format the organization uses, which turns guessing into confirming. Lesson 4.4 covers what to do with that.
Limits, and the mistakes that follow from ignoring them
Results are capped and estimates are wrong. Search engines will not show you more than a few hundred results per query, and the reported total is a rough estimate that changes between refreshes. Never report an operator result count as a market size. Get past the cap by varying the query, not by paginating.
Personalization and location shift results. Your results are not the results. Use a clean browser profile, set the location deliberately when you care about it, and expect two people running the same query to see different lists.
The operator matched a string, not a meaning. inurl:resources matches human resources pages, resource extraction companies, and any CMS that puts the word in a path. Every operator query needs a human pass before the results become prospects.
Automation gets you blocked and lied to. Firing thousands of operator queries from a script produces CAPTCHAs, blocks, and — worse — silently degraded results you then treat as data. Do it at human pace, or use a search API that permits it.
Don't stop at Google. Bing handles some operators differently and surfaces older pages that Google has quietly dropped. Site-internal search, and the search on the trade association's own website, will often find the exact resource page no external operator surfaces.
Questions
Do search operators still work in 2026?
The core set does: site:, inurl:, intitle:, quoted phrases, minus exclusions and uppercase OR all behave usefully. Anchor-text operators and related: have degraded to the point of uselessness, and + and ~ were retired years ago. Results are matched loosely and capped, so treat operators as a discovery aid rather than a database query.
Why do I get so many irrelevant results from inurl: queries?
Because the operator matches a string in a URL, not a concept. inurl:resources catches human resources pages and CMS paths that use the word structurally. Add exclusions for the recurring offenders — typically -inurl:blog -inurl:category -inurl:tag — and keep a per-project list of the exclusions your niche needs.
Can I automate operator searches at scale?
Not against the public search interface. You will hit CAPTCHAs, rate limits and terms-of-service issues, and long before that you will get quietly degraded results you mistake for real ones. If you need volume, use a search API that licenses this, and even then vary the queries rather than paginating deeper.
Is Google the only engine worth using for prospecting?
No. Bing applies some operators more literally and retains older pages Google has dropped, which matters when you are hunting long-standing resource pages. The internal search on a trade association or university site will often find the exact listing page that no external operator surfaces at all.