X (Twitter) Trends by Location Scraper

Fetch live X/Twitter trending topics for any city, country, or worldwide — no API key required. Supports 100+ cities and 46 countries. Returns ranked trend list with tweet volume (when available), trend type classification, and direct X search links. MCP-ready, cookieless, no login.

What you get

Field	Example
locationName	London
locationType	city
locationCountry	United Kingdom
locationCountryCode	GB
position	1
trendName	#WorldCup
trendType	hashtag
tweetVolume	125000
xSearchUrl	https://x.com/search?q=%23WorldCup&src=trend_click
dataSource	trends24
snapshotAt	2026-08-19T12:34:56.000Z

How it works

• City-level trends: scraped from trends24.in — 100+ cities worldwide
• Country + Worldwide trends: scraped from GetDayTrends — 46 countries + global
• Cookieless, no login, no API key needed
• Automatic fallback: if city trends page fails, falls back to GetDayTrends country page

Supported locations (120+)

Enter any of:

• City name: London, New York, Tokyo, Dubai, Lagos, São Paulo, Berlin
• Country name: Japan, Brazil, United States, India, Nigeria
• "Worldwide" for the global aggregate
• Aliases: US, UK, UAE, NYC, LA, SF

Sample cities available

New York, Los Angeles, Chicago, Houston, Dallas, Miami, Atlanta, Seattle, Denver, Boston, Las Vegas, San Francisco, San Diego, Portland, Detroit, Minneapolis, Philadelphia, Phoenix, San Antonio, Kansas City (US) — London, Manchester, Birmingham, Leeds, Glasgow (UK) — Tokyo, Osaka, Sapporo (Japan) — Sydney, Melbourne (Australia) — São Paulo, Rio de Janeiro (Brazil) — Toronto, Vancouver, Montreal (Canada) — Paris, Berlin, Madrid, Barcelona, Rome, Milan, Amsterdam, Brussels, Vienna, Zurich, Stockholm, Copenhagen, Oslo, Helsinki, Warsaw, Istanbul, Moscow — Dubai, Riyadh, Jeddah, Cairo — Seoul, Mumbai, Delhi, Bangalore, Bangkok, Kuala Lumpur, Jakarta, Manila, Karachi — Lagos, Nairobi, Johannesburg, Accra — Buenos Aires, Bogota, Lima, Santiago, Caracas, Mexico City, and more.

Quick start

{
  "locations": ["Worldwide", "United States", "London", "Tokyo"],
  "maxTrendsPerLocation": 10
}

No API key needed. Just run.

API example (Apify REST)

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~x-trends-by-location-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "locations": ["New York", "London", "Tokyo"],
    "maxTrendsPerLocation": 10
  }'

Pricing

Event	Price
Actor start	$0.00005
Trend row saved	$0.003

Example: 5 locations × 10 trends = 50 rows × $0.003 = $0.15 + platform usage (compute, typically <$0.01).

Input reference

Field	Type	Required	Default	Description
locations	string[]	No	["Worldwide","United States","United Kingdom"]	City or country names, or "Worldwide"
maxTrendsPerLocation	integer	No	10	1–50 trends per location
dedupeTrends	boolean	No	true	Skip duplicate trend names across locations

Use cases

• Brand monitoring — track when your brand or campaign hashtag trends in target cities
• Content strategy — surface what's trending locally before creating posts
• News monitoring — catch breaking topics in specific markets before they go mainstream
• Social intelligence — feed live trend data to AI agents for summarization or alerting
• Competitive analysis — monitor competitor campaign hashtag velocity by city

MCP / AI agent usage

Tool: apify--x-trends-by-location-scraper
Input: { "locations": ["New York", "London"], "maxTrendsPerLocation": 5 }
Returns: ranked trend rows with trendName, tweetVolume, xSearchUrl, locationType, dataSource
Cost: $0.003/trend + $0.00005/start

Limitations

• Tweet volume is null for many trends — source pages do not always expose volume
• X/Twitter trends update roughly every 5 minutes at the source; scrape freshness depends on run timing
• Historical trends are not available — this actor returns current live trends only
• City-level trends depend on trends24.in coverage; cities not in the supported set fall back to their country page
• Do not use this actor for X posts, profiles, or search results — see x-tweet-scraper or twitter-profile-followers-scraper

Related actors

• x-tweet-scraper — scrape tweets by keyword, hashtag, or user
• x-twitter-trends-scraper — original country-level only trends scraper
• twitter-profile-followers-scraper — X profile data and follower lists
• google-trends-scraper — Google Trends data by keyword and region
• tiktok-trending-hashtags-scraper — trending on TikTok by region

Builder's note

The official X/Twitter Trends API (GET /2/trends/by/woeid/{woeid}) requires a $5,000/month Pro subscription. Third-party providers (ScrapeCreators, SociaVault) do not currently expose a Twitter trends endpoint in their route catalog. This actor uses trends24.in for city-level data and GetDayTrends for country/worldwide data — both are real-time public pages that aggregate official X trend data without requiring a key. The fallback chain (city → country) handles page unavailability gracefully.

Legal

Public trend data is used for informational purposes. Use responsibly and in accordance with X's terms of service and your local laws.