Travel demand intelligence: tracking Airbnb, search, and news signals with Apify

Travel demand intelligence: tracking Airbnb, search, and news signals with Apify

Travel demand usually becomes visible online before it appears in a quarterly tourism report.

It shows up in Airbnb prices. It shows up in new listings. It shows up in Google searches. It shows up in local news about events, airline routes, hotel openings, and visa changes.

Travel demand intelligence is the practice of combining these public signals — short-term rental supply and pricing, search intent, and local news — into a single destination-level dataset, instead of waiting for a lagging industry report. An Apify workflow can build that dataset automatically using three Actors: Airbnb Scraper, Google Search Results Scraper, and Google News Scraper.

Quick answer

Use Airbnb Scraper to collect short-term rental supply, prices, ratings, host data, coordinates, and photos. Combine it with Google Search Results Scraper for search visibility and Google News Scraper for event and market signals. Schedule runs to compare demand indicators across locations over time.

The travel signal stack

The workflow pulls from:

1. Airbnb Scraper — listings, prices, ratings, host info, coordinates, photos, and date-specific availability.
2. Google Search Results Scraper — travel-related SERP visibility and People Also Ask questions.
3. Google News Scraper — local events, tourism news, and market mentions.

The signal chain:

\
Target destinations
-> Airbnb Scraper
-> Google Search Results Scraper
-> Google News Scraper
-> travel demand snapshot
\\

Short-term rental investors, travel startups, tourism marketers, and market researchers can use the same dataset to compare destinations without waiting for lagging reports.

Key facts

• 3 Actors, 1 schedule: Airbnb Scraper, Google Search Results Scraper, Google News Scraper can all run on a recurring Apify schedule.
• Date-aware pricing: passing explicit checkIn/checkOut dates to Airbnb Scraper is what makes prices comparable across destinations — undated scraping only gives directional numbers.
• Neighborhood beats city: coordinate-level clustering surfaces local demand patterns that city-wide averages hide.
• Three signal types, one dataset: supply (Airbnb), intent (Search), and context (News) — combining all three avoids mistaking a cheap destination for a good market.

Actor configuration that matters

For Airbnb, start with a location or search URL, then keep the date window explicit. Date-aware scraping matters because travel prices move by season, weekend, and event. Set a listing cap during discovery and only expand once the location query looks right.

\json
{
"locationQueries": ["Lisbon", "Porto", "Valencia"],
"checkIn": "2026-05-15",
"checkOut": "2026-05-18",
"maxListings": 100,
"proxyConfiguration": {
"useApifyProxy": true
}
}
\\

For Google Search Results Scraper, use location-specific travel queries and country/language settings. For Google News, pair destination names with event and tourism keywords, then use a recent dateRange such as 7d or 1m.

What the output looks like

For Airbnb, the base row needs price, location, and quality signals:

\json
{
"title": "Sunny apartment near the old town",
"location": "Porto, Portugal",
"price": 142,
"currency": "EUR",
"rating": 4.86,
"reviewsCount": 128,
"hostType": "Superhost",
"coordinates": { "lat": 41.1579, "lng": -8.6291 },
"url": "https://www.airbnb.com/rooms/..."
}
\\

Search and news rows add intent and context. The same destination can have average rental prices, high search interest, and weak news coverage — seeing those signals together is what makes the workflow useful.

In a small Airbnb Scraper run for Austin with a two-night September date window, the Actor returned 18 listing rows, including id, url, name, type, price, originalPrice, priceQualifier, rating, latitude, longitude, photos, searchUrl, and scrapedAt.

Airbnb as a supply and pricing signal

The Airbnb Scraper extracts listings for a location and can include check-in and check-out dates for more accurate pricing. Useful fields include:

• property title
• nightly or trip price
• rating
• review count
• host details
• Superhost status
• coordinates
• photos
• property type

For market research, density and price distribution matter most. A neighborhood with many high-rated listings and rising prices may indicate strong demand. A location with lots of listings but weak reviews may indicate opportunity or oversupply.

Search results as an intent signal

Search data helps explain what travelers are trying to figure out. Example queries worth running:

• "best area to stay in Lisbon"
• "things to do in Medellin"
• "family hotels in Orlando"
• "Airbnb near Formula 1 Austin"

Google Search Results Scraper returns organic results, related queries, People Also Ask questions, country and language targeting, and pagination. People Also Ask data is especially useful because it shows recurring traveler concerns.

News as an event signal

News often explains demand spikes. Google News Scraper can monitor:

• festivals
• conferences
• sports events
• new flight routes
• visa policy changes
• safety issues
• hotel openings
• tourism board campaigns

If Airbnb prices rise and local news shows a major event, the story becomes clearer.

The destination scorecard

Turn the raw data into a simple destination scorecard. It isn't meant to be a perfect forecast — it's meant to rank markets for deeper investigation. The scorecard includes:

• number of Airbnb listings found
• median listed price for the selected dates
• share of listings with strong ratings
• review count distribution
• density by neighborhood or coordinate cluster
• number of recent news mentions
• major events mentioned in news
• People Also Ask questions from Google Search
• visible travel guides ranking in search

This mix helps avoid one-source thinking. A destination with high Airbnb prices but weak review volume may be thinly supplied. A destination with lots of listings and many recent event mentions may be entering a busy season. A destination with many search questions about safety or transportation may need better traveler education.

For short-term rental investors, this doesn't replace underwriting — it narrows the map. For travel marketers, it shows which questions to answer in content before the season peaks.

Example workflow

Suppose you want to compare Lisbon, Porto, and Valencia for a spring travel campaign. Run Airbnb Scraper for the same date window in each city, collect Google Search results for "where to stay" and "things to do" queries, then pull Google News results from the last 30 days.

The output shows more than average price — it shows which neighborhoods have dense listing supply, which destinations have recent event coverage, and which traveler questions appear repeatedly. If "is Porto walkable" keeps appearing in People Also Ask, that question belongs in the content plan. If Valencia has a sudden cluster of news around a festival, that belongs in the demand notes.

The workflow works because it combines supply, intent, and context — that combination keeps you from mistaking a cheap destination for a good market.

Production notes

Use dates. Travel pricing without check-in and check-out dates is directional. Date-specific scraping gives better price comparisons.

Compare neighborhoods, not only cities. City-level averages hide local patterns. Coordinates make neighborhood clustering possible.

Track review counts over time. Review growth can indicate booking activity even when occupancy isn't public.

Watch news for shocks. Weather, regulation, safety, and events can change demand quickly.

Keep raw data and derived metrics separate. Store original listing prices and calculate averages downstream.

Compare neighborhoods, not cities, from the start. An early version of this workflow compared cities too broadly — Lisbon vs. Porto looked interesting, but neighborhood-level clusters were far more useful. Travel demand is local: a city average hides the difference between a tourist center, a residential neighborhood, and an event district.

Cost comparison

Approach	Best for	Weakness
Manual travel research	One destination	Slow and subjective
STR analytics SaaS	Occupancy estimates	Can be expensive
Apify workflow	Custom location and event monitoring	Requires an analysis model

Check the current Pricing tabs for Airbnb Scraper, Google Search Results Scraper, and Google News Scraper before running at scale — date windows, listing limits, and full-text extraction settings affect run cost.

FAQ

Can Apify scrape Airbnb listings?

Yes. Airbnb Scraper (built by CrawlerBros) extracts public listing data, pricing, ratings, host info, coordinates, and photos.

Can I track travel demand with scraping?

Yes — you can track public demand proxies such as listing prices, review growth, search questions, and news events. This doesn't replace official tourism statistics, but it's available in near-real time, unlike quarterly reports.

Is this only useful for Airbnb investors?

No. Tourism marketers, travel startups, hotel analysts, and event planners can all use the same three-signal approach (supply, intent, context) for their own destination research.

What's the fastest way to try this?

Pick three destinations and one date window. Scrape Airbnb listings, run travel-related Google searches, and collect local news from the last 30 days, then put the data side by side.

Try it yourself

Pick three destinations and one date window. Scrape listings with Airbnb Scraper, run travel-related queries with Google Search Results Scraper, and pull recent coverage with Google News Scraper. Put the data side by side — the strongest market is rarely the one with the loudest travel blog posts.