Wikivoyage Travel Guide Scraper
Pricing
from $0.50 / 1,000 results
Wikivoyage Travel Guide Scraper
$0.5/1K π₯ Wikivoyage scraper! Travel guides with summaries, coordinates & sections. No key. JSON, CSV, Excel or API in seconds. Build travel apps & destination content β‘
Pricing
from $0.50 / 1,000 results
Rating
0.0
(0)
Developer
ninhothedev
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Scrape Wikivoyage travel guides at scale β destination summaries, GPS coordinates, full section outlines, hero images and canonical URLs β from any of the 25+ Wikivoyage language editions. No API key, no login, no proxy required.
Wikivoyage is the free, community-written travel guide (a sister project of Wikipedia) covering tens of thousands of cities, regions, parks and itineraries. This Actor turns those guides into clean, structured JSON/CSV/Excel rows you can drop straight into a travel app, a content pipeline or an LLM/RAG index.
What it does
| Mode | Input | Output |
|---|---|---|
| search | Keywords such as Berlin, Tokyo, hiking Norway | Every matching destination page with intro summary, coordinates, thumbnail and word count |
| pages | Exact page titles such as Paris, Berlin/Mitte | The full detail record for each title (redirects followed automatically) |
Each result is one dataset item β one row per travel guide.
Features
- Destination search β up to 50 Wikivoyage pages per query, deduplicated across queries.
- Geo-ready β latitude/longitude straight from the article's primary coordinates, perfect for maps and radius search.
- Section outlines β the complete table of contents (
Get in,See,Do,Eat,Drink,Sleep,Stay safe, β¦) plus asection_count, so you can judge guide depth at a glance. - Plain-text summaries β clean intro extracts (capped at 5,000 characters), no wiki markup, no HTML.
- 25+ languages β
en,de,fr,es,it,nl,pt,ru,pl,sv,zh,jaand more, via a singlelanguageinput. - Hero images β a 600px thumbnail URL for every guide that has a page image.
- Datacenter-clean β runs on the free/basic Apify infrastructure without residential proxies.
Input
{"mode": "search","queries": ["Berlin", "Tokyo"],"language": "en","includeSections": true,"maxItems": 100}
| Field | Type | Default | Description |
|---|---|---|---|
mode | select | search | search = find destinations by keyword, pages = fetch exact titles |
queries | array | ["Berlin","Tokyo"] | Search keywords (mode search) |
titles | array | β | Exact page titles, e.g. ["Paris"] (mode pages) |
language | string | en | Wikivoyage language edition code |
includeSections | boolean | true | Fetch the full table of contents per guide |
maxItems | integer | 100 | Hard cap on dataset items (max 1000) |
Output
{"page_id": 3512,"title": "Berlin","language": "en","summary": "Berlin is Germany's capital and largest city. Within the city limits, Berlin in 2022 had a population of 3.7 million...","latitude": 52.51794,"longitude": 13.38873,"thumbnail": "https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/Siegessaeule_Aussicht_10-13_img4_Tiergarten.jpg/960px-...","word_count": 22432,"sections": ["Districts", "Understand", "History", "Get in", "Get around", "See", "Do", "Eat", "Drink", "Sleep"],"section_count": 88,"url": "https://en.wikivoyage.org/wiki/Berlin","source": "wikivoyage","scraped_at": "2026-07-28T12:35:00+00:00"}
All fields are nullable β a page without coordinates simply returns null for latitude/longitude.
Use cases
- Travel apps β seed a destination database with names, coordinates and human-written summaries in minutes.
- Destination content β power city guides, landing pages and newsletters with editorial-quality descriptions and section structure.
- LLM / RAG corpora β build a clean, attributable travel knowledge base for chatbots and AI travel assistants.
- Itinerary tools β use coordinates plus section outlines (
See,Do,Eat) to auto-assemble day plans and route suggestions.
Pricing
Roughly $0.5 per 1,000 travel guides on typical runs, plus Apify platform usage. Turning includeSections off removes one request per page and makes runs noticeably cheaper and faster.
Speed & limits
- Requests are batched (up to 20 pages per API call) and sent with a descriptive User-Agent, in line with the Wikimedia API etiquette.
maxItemscaps at 1,000 guides per run; chain runs or split queries for larger crawls.- Search only covers the main namespace (actual travel articles, not talk or user pages).
Related Actors
- Wikipedia Scraper β articles, summaries and metadata from Wikipedia
- Geocoding Scraper β turn addresses into coordinates and back
- CityBikes Scraper β live bike-sharing stations worldwide
- OpenStreetMap Notes Scraper β community map notes and reports
Legal & attribution
Wikivoyage content is published under CC BY-SA 4.0. When you republish text from this Actor, credit Wikivoyage and its contributors and keep the share-alike licence. This Actor reads only the public MediaWiki API and collects no personal data.