The best X search for customers isn't your brand name or a hashtag. It's the sentence a buyer types when they're stuck: "any recommendations for," "alternative to," "is there a tool that." Pair those phrases with two or three operators and X's search turns into a free lead list that refreshes all day.
I put together the strings below on November 21, 2026 and checked every operator against a source: X's help center, X's developer docs, or the most-cited community reference. I couldn't log in to X to run them, so I've marked which operators X documents and which are community-known, and I left out any I couldn't source.
Disclosure: I build Needle, which appears once further down as one option. Everything else here works with a free X account.
If you're deciding whether X is worth it at all, I covered that in X alternatives for social listening and Bluesky vs X for B2B signal. This post is the how-to.
In brief
- Search for questions, not keywords. "any recommendations" + category, "alternative to" + competitor, and competitor complaints beat hashtags for buyer intent.
- Three filters do most of the work:
-filter:links(drops most promotional posts),lang:enand a date filter likesince:2026-11-14. - Don't filter fresh leads by likes.
min_faves:is real (X's developer docs name it), but new questions have few likes. Use it for research. - Save the winners. X documents saving searches on mobile; on desktop, bookmark the results URL. Put competitors and ideal customers in private Lists.
- Reply by hand, once, on topic, with disclosure. X bans keyword-triggered auto-replies, copy-paste replies and replies irrelevant to the post.
Which X search operators are documented, and which are community-known?
X's advanced search help page (checked Nov 21, 2026) documents the fields in the advanced search form: all words, exact phrases, any of these words, excluded words, hashtags, language, posts from, replying to or mentioning an account, location, and date ranges. It says advanced search "is available when you're logged in." The form writes operators into the search box for you, but the page doesn't print their syntax.
X's API operator reference fills one gap: it says "The equivalent operators on X web search are named min_faves: and min_retweets:." For the rest, the standard reference is Igor Brigadir's twitter-advanced-search repository, which tested each operator and records a "last checked" date (most in 2022, the newest in January 2024).
| Operator | What it does | Source |
|---|---|---|
"exact phrase" |
Matches the phrase | X help center (form field) |
A OR B |
Either term (OR must be uppercase) | X help center (form field); repo |
-word |
Excludes a word or phrase | X help center (form field) |
#hashtag |
Posts with a hashtag | X help center |
lang:en |
Language (auto-detected, not always right) | X help center (form field); repo |
from:user / to:user / @user |
Posted by / replying to / mentioning | X help center (form fields); repo |
since:YYYY-MM-DD / until:YYYY-MM-DD |
Date range (until is exclusive) |
X help center (form field); syntax from repo |
min_faves:N / min_retweets:N |
Minimum likes / reposts | X developer docs |
min_replies:N |
Minimum replies | Community (repo) |
-min_faves:N |
Maximum likes | Community (repo) |
filter:links / -filter:links |
With / without a URL (includes media) | Community (repo) |
filter:replies / -filter:replies |
Only replies / no replies | Community (repo) |
url:domain |
Posts linking a domain (use _ for -) |
Community (repo) |
? |
Posts containing a question mark | Community (repo) |
list:ID |
Posts from members of a public List | Community (repo) |
Two practical limits from the repo: queries top out around 22 to 23 operators, and date operators need to be combined with something else. Its author also notes these are web search operators that "will largely not work" with X's APIs, which use different syntax (more on that below).
22 copy-paste search strings for buyer intent
Replace the bracketed parts. Run each one, then switch to the Latest tab so you see the newest posts first. Change the since: date to about a week before today.
People asking for recommendations
"any recommendations" (CRM OR "sales pipeline") -filter:links lang:en"can anyone recommend" "[category]" -filter:links"looking for a tool" ([keyword] OR [keyword]) -filter:links lang:en"is there a tool that" [problem] since:2026-11-14"what do you use for" ([job] OR [job]) ?("anyone using" OR "anyone tried") "[category]" min_replies:2"recommend" "[category]" "budget" -filter:links lang:en"best [category]" ("for a startup" OR "for small teams") -filter:links
People leaving a competitor
"alternative to [Competitor]" OR "[Competitor] alternative" -from:[CompetitorHandle]"switching from [Competitor]" OR "moving off [Competitor]" OR "migrating from [Competitor]""[Competitor]" ("too expensive" OR "price increase" OR "raised prices") -from:[CompetitorHandle]"[Competitor]" ("frustrated" OR "giving up on" OR "fed up") lang:ento:[CompetitorHandle] (cancel OR refund OR "doesn't work" OR "still broken")"[Competitor] is down" OR "[Competitor] outage" since:2026-11-14@[CompetitorHandle] ("alternative" OR "competitor" OR "switch")
Pain without a product name
"how do you handle" [problem] -filter:links lang:en"spent hours" [task] (manually OR spreadsheet) -filter:links"is it just me" [problem] ?
Research and validation (not live leads)
"[category]" min_faves:50 -filter:links lang:en, for the posts in your space people actually engage withurl:[competitordomain_com] -from:[CompetitorHandle], for people sharing a competitor's site (swap-in the domain for_)list:[YourListID] ("looking for" OR "recommend" OR "anyone know"), which runs a buyer-intent search over only the accounts in a public List you built
The self-promo filter (append to any string above)
-filter:links -"check out" -"sign up" -"DM me" -giveaway -"we built" -"I built" -"link in bio"
-filter:links alone removes a lot of noise for me, since promotional posts tend to carry a link. It also removes some real questions that include a screenshot, since the filter counts media as links. If a search feels thin, drop it and see what comes back.
How to save searches and build Lists
Saved searches. X's saving searches page documents the mobile flow: search from the Explore tab, tap the overflow icon at the top of the results, then tap Save. Next time you tap the search box, your saved searches appear. To remove one, tap the X next to it under Saved.
On desktop I don't rely on the save button. Run the search, click Latest, and bookmark the page. The URL keeps the full query, operators included, so a bookmark folder called "X leads" with eight entries becomes a two-minute morning routine.
Lists. X Lists show "a stream of posts from only the accounts on that List." X's default is public ("anyone can follow the List"), so switch on Private when you create one; nobody needs to see your "competitors" or "prospects" List. Names max out at 25 characters and can't start with a number. Three Lists worth having:
- Competitors: their official accounts and founders. You see launches, outages and pricing changes the day they happen.
- Ideal customers: people who match your buyer and post about their work. Run string 21 against it.
- Peers: founders in adjacent categories. Their replies often hold the "has anyone tried" questions.
How to triage what you find
X moves fast, so triage has to be quick. I run each saved search once a day and sort every post into one of three buckets in under ten seconds:
| Bucket | What it looks like | What to do |
|---|---|---|
| Reply | A direct question your product answers, recent, the asker is a real person in your market | Reply today (see below) |
| Learn | A complaint, a comparison thread, a "how do you handle" with no tool request | Note the wording; don't pitch |
| Skip | Engagement bait, a competitor's own post, a reseller, anything older than a few days | Ignore |
Three checks decide most of it: Is the person asking, or announcing? Does the thread already have a good answer? Would you be comfortable if the poster saw your reply and your profile side by side? If not, skip.
The Learn bucket matters more than it looks. The exact phrases people use in complaints are your next search strings, and often your next landing page headline.
How to reply on X without being spammy
X's rules are specific here, and they apply to people as well as bots. From the authenticity policy and automation rules, checked Nov 21, 2026:
- No keyword-triggered automation. "Sending automated replies to posts based on keyword searches alone is not permitted." AI reply bots need "prior written and explicit approval" from X.
- No copy-paste. Repeatedly posting identical or nearly identical posts ("Copypasta") is listed as content spam.
- Stay on topic. "Promoting content by replying with content that is irrelevant to the topic of the original post" is banned.
- No volume. "Bulk, aggressive, high-volume unsolicited replies, mentions, or direct messages" are banned, and enforcement includes excluding posts from search, downranking in replies and suspension.
Within those rules, here's what works for me:
- Answer the question in the reply itself. If they asked for a CRM for a two-person team, name two or three options, including ones that aren't yours, and say who each suits.
- Disclose in the same sentence. "I work on [Product], so I'm biased, but..." The FTC's guidance says employees promoting their company's products "should disclose your relationship to the company," and a bio mention isn't enough (FTC).
- Hold the link until asked. Your name is enough for them to find you. If they ask, send it.
- One reply per thread, and no DM unless invited. Following up in DMs uninvited is how a helpful reply turns into an unsolicited message.
- Write each one fresh. Templates help you think. Posting the same words twice is what X calls spam.
The community reply templates guide has starting structures, and I've collected every platform's rules on AI and automated replies in AI reply bots: what the rules actually say.
Can you automate this with the X API?
You can automate the finding part. Posting is where X's rules bite (above). As of Nov 21, 2026, X's API pricing page lists pay-per-usage pricing with no subscriptions or minimum spend:
| Action | Price |
|---|---|
| Post read | $0.005 per post |
| Owned reads (your own posts, followers, bookmarks) | $0.001 per resource |
| Post create | $0.015 per request |
| Post create with a URL | $0.20 per request |
You buy credits upfront in the Developer Console, reads are deduplicated within a 24-hour UTC window, and pay-per-usage is capped at 3 million post reads per monthly billing cycle, above which X points you to Enterprise. The page also says "Prices are subject to change."
So reading 10,000 posts a month costs about $50 at list price. Two syntax differences catch people out: the API uses min_likes:, min_replies: and min_reposts: instead of min_faves:, and has:links and -is:retweet instead of the filter: operators. Self-serve recent search queries are limited to 512 characters (X docs).
If you'd rather not build it, social listening tools and lead tools cover X too. Needle includes X in Auto Search on every plan, with manual X searches on the Scale plan (pricing, and the X page shows what it pulls). For a few saved searches a day, though, a bookmark folder and ten minutes is enough.
A 10-minute daily routine
- Open your bookmark folder of 5 to 8 saved searches, each on the Latest tab.
- Skim each, sort posts into Reply / Learn / Skip.
- Write one or two replies by hand, with disclosure.
- Check your Competitors List for anything that changed.
- Copy any new buyer phrases from the Learn bucket into a note, and turn the best one into a new search on Friday.
Do it for two weeks before you judge it. Some categories get asked about on X every day; others barely at all, and then Bluesky or other networks may be a better use of the time.
Evidence notes
All pages opened on November 21, 2026.
- X advanced search help page: https://help.x.com/en/using-x/x-advanced-search
- X search help page (Top / Latest tabs): https://help.x.com/en/using-x/x-search
- X saving searches: https://help.x.com/en/using-x/saving-searches
- X Lists: https://help.x.com/en/using-x/x-lists
- X API search operators (incl. note naming
min_faves:/min_retweets:as web search operators): https://docs.x.com/x-api/posts/search/integrate/operators - X API query building and length limits: https://docs.x.com/x-api/posts/search/integrate/build-a-query
- X API pricing (pay-per-usage): https://docs.x.com/x-api/getting-started/pricing
- X automation rules (updated April 2026): https://help.x.com/en/rules-and-policies/x-automation
- X authenticity policy (spam and platform manipulation): https://help.x.com/en/rules-and-policies/authenticity
- Community operator reference, Igor Brigadir, twitter-advanced-search (operator "last checked" dates 2022 to Jan 2024): https://github.com/igorbrigadir/twitter-advanced-search
- FTC Endorsement Guides Q&A: https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking
I couldn't run these searches logged in, so treat the community-known operators as "worked when last tested." If one stops working, the advanced search form (Search filters, then Advanced search) still builds the documented ones for you.