Skip to content

How to Find X Posts From a Location (and Why near: Finds So Little)

X still lists near: and within: in its help, but few posts carry a location, because location sharing is off by default. Here is what works today for finding posts from a city or area, and what doesn't.

By AyeWatch Team4 min read

Short answer: X's help still lists near:city and within:radius, as in flood near:austin within:15km, plus a Places field in Advanced search and a Near you filter. They only match posts that carry a location, and location sharing is off by default, so results are thin. Searching the place name as a keyword finds far more.

What X offers for location today

We read X's help pages on 21 November 2026. Three location tools are still described:

  • Operators. X's help page on X Pro features lists near:city and within:radius, with the example fire near:san-francisco within:10km. The radius takes km or mi.
  • Advanced search. The Places section finds "posts sent from a geographic location" that you pick from a dropdown.
  • Search filters. After a search, the filter menu offers Everywhere or Near you.

Search on X requires an account, so we couldn't test how many results each returns today. What we can explain is why they return few.

Why location searches come back thin

X's help page on post location settings says adding a location to posts is off by default. People who turn it on choose a label, such as a city or a neighbourhood, for each post. Precise coordinates are attached only to photos or videos taken with X's in-app camera while precise location is switched on, and X notes that those coordinates can be found through the API. Business and landmark place names come from Foursquare.

So a location search only sees the share of posts whose authors opted in and picked a place. X doesn't publish that share, but anyone who has tried near: on a breaking local story knows the list is short and skews toward a few habitual taggers. Treat location operators as a bonus, not a filter you can trust to be complete.

geocode:, which some guides recommend, takes latitude, longitude and a radius. It came from X's older developer API and isn't on X's help pages for web search. We couldn't confirm it works in the search box today. The current API has place:, place_country:, point_radius:, bounding_box: and has:geo, but those run on X's paid API, not in the app, and they also depend on posts carrying location data.

What works better: search the place, not the coordinates

People name places in what they write. "Power's out on the east side of Austin" carries no location tag, but it says Austin. A keyword search finds it.

  • Place names and nicknames. (austin OR atx OR "travis county") ("power out" OR outage OR flooding)
  • Local hashtags. (#atxwx OR #austinweather) -giveaway. Look up which tags locals actually use before you rely on one.
  • Local accounts. from:city_utility_handle OR from:local_news_handle, with the placeholders swapped for the real utility and news accounts in your city.
  • A business near a place. "maple & rye" (austin OR "south congress") for a made-up bakery with several branches.
  • Belt and braces. (flood OR flooding) near:austin within:25km as a second search, to catch the few tagged posts that don't name the city.

Add lang: for a non-English city (it is in X's Advanced search form as Language), and switch to the Latest tab so recent posts come first. The free X advanced search builder writes these queries with the brackets in place.

Keep a local search running

An AyeWatch X Search monitor runs the query on each check and sends new posts. It passes your words to X's search, so near: returns as little there as on x.com. Build the monitor on place names, and let the AI filter decide whether each post is really local. It costs 2 credits a check, 3 with the filter.

Sample setup. Query: (austin OR atx) ("power out" OR outage OR "boil notice" OR flooding). Only alert me about: "posts reporting a current outage, boil notice or flooding in the Austin, Texas area; skip jokes, old news and posts about other cities named Austin".

Sample alert. "@eastside_neighbor_lu: 'Boil water notice just went out for 78702, the city text came through five times.'" The account is made up.

For a whole region with many town names, run one monitor per area so each query stays specific and under the 500-character limit.

When AyeWatch is the wrong tool

AyeWatch can't draw a radius on a map or read a post's coordinates, and it doesn't use account profile locations. For public safety work where a missed post matters, rely on official alerts first. If you need true geofenced posts, that is X's paid API with point_radius:, and it still only sees posts that carry location.

Cost and effort

A local X Search monitor checked every three hours uses about 480 credits a month, 720 with the AI filter, which needs Pro+. Checked daily, it is about 90 with the filter. AyeWatch Pro is $9/mo with 50 topics and hourly checks; Pro+ is $19/mo with 200 topics and ASAP mode. Every plan starts with a 7-day free trial.

MethodStatus on 21 Nov 2026How much it finds
near:city + within:On X's help pageOnly posts with a location; few
Advanced search PlacesOn X's help pageSame pool of located posts
Near you filterOn X's help pageSame pool, around your location
geocode:lat,long,radiusNot on X's help pages; untestedUnknown
API point_radius:, place:In X's API docs (paid)Located posts only
Place names as keywordsWorks as plain text searchMost; needs filtering for other places with the same name

Start a monitor in under a minute

Describe a topic or paste a URL. Cancel before the trial ends and you pay nothing.

Try it free for 7 days

The bottom line

Use near: as a second search, not the main one. Build your local query from place names, nicknames and local tags, test it on the Latest tab, and run it as an X Search monitor with an AI filter that knows which Austin you mean.

FAQ

Does near: still work on X?

It is still on X's help page. It only matches posts that carry a location, and X turns location sharing off by default, so expect few results.

Can I search X with geocode:?

We couldn't confirm it. geocode: came from X's older developer API and isn't on X's help pages for web search.

Why does a location search on X miss most local posts?

Most people never add a location to posts. A keyword search for the place name finds the posts that mention it.

Can I get alerts for X posts from a city?

An AyeWatch X Search monitor on place names plus an AI filter for local relevance sends new matching posts, for 2 credits a check plus 1 for the filter.

find x posts from a locationtwitter search by locationx near operatortwitter geocode searchsearch tweets near me

Related articles