AllTrails Scraper — Trails, Reviews & GPS Data

Extract structured hiking trail data from AllTrails.com at scale. Get trail names, difficulty, distance, elevation, GPS coordinates, ratings, reviews, photos, activity tags, and features — all as clean, structured JSON.

What It Does

The AllTrails Scraper searches AllTrails by keyword, national park, city, country, or direct URL, and returns detailed trail records with:

• Trail name, description, and URL
• Difficulty (easy, moderate, hard, expert)
• Route type (loop, out-and-back, point-to-point)
• Distance (miles + kilometers)
• Elevation gain (feet + meters)
• GPS coordinates (latitude + longitude)
• Average rating and review count
• Photo count, recording count, and popularity score
• Estimated duration
• Activities (hiking, backpacking, trail running, etc.)
• Features (views, waterfalls, lakes, dog-friendly, etc.)
• Visitor traffic level
• Cover image URL
• Closure and alert status
• Up to 5 recent reviews with author, rating, and text
• Rating breakdown (1-5 star distribution)

Input Options

Direct URLs (startUrls)

Paste any AllTrails URL — trail pages, park/area pages, city pages, or explore URLs.

{
    "startUrls": [
        { "url": "https://www.alltrails.com/trail/us/california/half-dome-trail" },
        { "url": "https://www.alltrails.com/parks/us/california/yosemite-national-park" }
    ],
    "maxItems": 50
}

Keyword Search (mode: search)

Search AllTrails by keyword via the Algolia search index.

{
    "mode": "search",
    "searchQuery": "coastal hike california",
    "maxItems": 30
}

By National Park (mode: byPark)

{
    "mode": "byPark",
    "park": "yosemite-national-park",
    "state": "california",
    "maxItems": 100
}

By City (mode: byCity)

{
    "mode": "byCity",
    "city": "denver",
    "maxItems": 50
}

By Country (mode: byCountry)

{
    "mode": "byCountry",
    "country": "us",
    "maxItems": 200
}

Filters

All modes support filters:

Filter	Type	Description
difficulty	string	easy, moderate, hard, expert
routeType	string	loop, out-and-back, point-to-point
activity	string	hiking, trail-running, backpacking, etc.
minRating	number	Minimum star rating (0-5)
minLengthKm	number	Minimum trail length in km
maxLengthKm	number	Maximum trail length in km

Full Trail Details

Set fetchTrailDetails: true (default) to fetch the full trail detail page for each result, giving you descriptions, reviews, and ratings breakdown. Set to false for faster, lighter results.

Output

Each trail record contains:

Field	Type	Example
trailId	string	"1001"
name	string	"Half Dome Trail"
url	string	"https://www.alltrails.com/trail/..."
description	string	"A classic trail to the iconic Half Dome..."
difficulty	string	"hard"
routeType	string	"out-and-back"
lengthMiles	number	14.2
lengthKm	number	22.9
elevationGainFt	number	5300
elevationGainMeters	number	1615
avgRating	number	4.8
numReviews	number	4521
numPhotos	number	120
numRecordings	number	8900
popularity	number	95
latitude	number	37.745
longitude	number	-119.536
city	string	"Yosemite Valley"
state	string	"California"
country	string	"United States"
areaName	string	"Yosemite National Park"
activities	string[]	["hiking","backpacking"]
features	string[]	["views","waterfall","forest"]
visitorUsage	string	"heavy"
estimatedDurationMinutes	number	480
imageUrl	string	"https://cdn2.alltrails.com/..."
isClosed	boolean	false
hasAlerts	boolean	false
recentReviews	array	[{authorName, rating, text, createdAt}]
ratingsBreakdown	object	{"1":0,"2":5,"3":20,"4":100,"5":4396}
scrapedAt	string	"2026-07-08T10:00:00.000Z"
sourceUrl	string	"https://www.alltrails.com/..."

Pricing

This actor uses Pay-Per-Event pricing:

Event	Price	Description
Actor Start	$0.00005	Charged once when the run starts
Trail Item	$0.006	Charged per trail record returned

Example: Scrape 100 trails = $0.00005 + (100 × $0.006) = $0.60

Use Cases

• Trip planning apps: Power a hike-finder feature with current trail metrics
• Tourism boards: Benchmark trail density and difficulty mix across regions
• GIS research: Build geospatial datasets using GPS coordinates
• Outdoor gear retail: Identify high-rated, high-traffic trails for marketing
• Travel content: Generate data-backed trail roundups and listicles
• AI/ML: Feed structured trail data into recommendation models

Technical Approach

• HTTP-first: Uses AllTrails' public Algolia search index + JSON trail detail pages — no browser rendering needed, making it fast and reliable
• Auto-proxy escalation: Starts without a proxy, automatically falls back to residential on blocks
• Session pool: 20 sessions with 10 requests per session to avoid rate limits
• 3-layer extraction: Algolia JSON → Next.js __NEXT_DATA__ → LD+JSON fallback

Proxy Support

AllTrails works without a proxy in most cases. If you experience IP blocks:

1. Enable useProxy: true to route through Apify datacenter proxies
2. Set proxyGroups: ["RESIDENTIAL"] for residential proxies if datacenter is blocked

---

Export scraped data, run the scraper via API, schedule and monitor runs, or integrate with other tools. Built for reliability and scale.

What is AllTrails Scraper?

AllTrails Scraper turns the target data into structured, reusable results on Apify. Use it when you need repeatable collection for analysts, developers, agencies, researchers, and AI-agent workflows without maintaining a custom scraper or one-off integration. Run it manually, schedule recurring jobs, call it through the Apify API, or connect it to an AI agent through the Apify MCP server.

The Actor stores results in an Apify dataset, where they can be previewed and exported as JSON, CSV, Excel, XML, or RSS. Availability and completeness depend on the source, supplied inputs, public visibility, authentication requirements, and upstream rate limits.

Use cases for AllTrails Scraper

• Build structured datasets for research, reporting, enrichment, or monitoring.
• Automate repetitive collection with schedules, webhooks, and API calls.
• Feed clean records into spreadsheets, databases, CRMs, BI tools, AI agents, or RAG pipelines.
• Track changes over time by running the same validated input on a schedule.
• Replace fragile manual copy-and-paste work with a reproducible Apify workflow.

How to use AllTrails Scraper

1. Open the Actor input page and choose a focused, valid target.
2. Set a conservative result limit for the first run.
3. Start the Actor and inspect the dataset for coverage and field availability.
4. Export the results or connect the dataset to your downstream system.
5. Scale gradually and use scheduling, pagination, or proxies when supported.

Important input options

• startUrls — Paste AllTrails URLs directly. Supports trail pages, park/area pages, city pages, or explore URLs. Use this field when the user provides specific URLs. Use searchQuery or mode instead when t
• mode — How to discover trails when not pasting URLs. byUrl: scrape provided URLs. search: free-text search via Algolia. byPark: browse a national park. byCity: browse trails in a city. byCountry: t
• searchQuery — Free-text search query for trails (e.g. 'yosemite', 'coastal hike california'). Used when mode is 'search'. Do NOT use this when the user provides URLs — use startUrls instead.
• country — Country slug for AllTrails URLs and search index. 'us' is default. Examples: us, canada, united-kingdom, france, germany, australia.
• state — State or region slug (e.g. 'california', 'new-york'). Used with byPark, byCity, and byTrail modes.
• city — City slug (e.g. 'san-francisco', 'denver'). Used when mode is 'byCity'.
• park — Park slug (e.g. 'yosemite-national-park', 'zion-national-park'). Used when mode is 'byPark'.
• trailSlug — The trail slug — the part of the AllTrails URL after the state. Used when mode is 'byTrail'.

API and automation example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/alltrails-scraper').call({
  // Add the same input fields you use in the Apify Console.
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Related Apify Actors

Use these dedicated tools when a neighboring data source or workflow is a better match:

• Leads Finder Pro - B2B Leads with Emails [Apollo Alternative]
• Yellow Pages US Scraper — Business Leads & Reviews
• Yellow Pages Australia Scraper — Business Leads & Reviews
• OpenTable Restaurants, Ratings & Reviews Scraper
• YouTube Thumbnail Downloader
• Google Play Reviews Scraper
• GitHub Repo Search — Stars, Language & Topics
• Rate My Professors & Schools Scraper
• California CSLB Contractor License Scraper
• Instagram Followers & Following Scraper — With Cookies

Frequently asked questions

How many results can I scrape with AllTrails Scraper?

The practical total depends on the source, input limits, pagination, available records, run timeout, and upstream restrictions. Start with a small run, verify the output, and increase the limit gradually.

Can I integrate AllTrails Scraper with other apps?

Yes. Use Apify integrations, webhooks, schedules, dataset exports, Make, Zapier, Google Sheets, cloud storage, or your own application.

Can I use AllTrails Scraper with the Apify API?

Yes. Start runs with the Apify REST API or an official Apify client, then retrieve records from the run's default dataset. Keep your API token in a secret or environment variable.

Can I use AllTrails Scraper through an MCP Server?

Yes. The Apify MCP server can expose the Actor to compatible AI clients and agents. Review the input and expected cost before allowing an autonomous workflow to run it at scale.

Do I need proxies?

It depends on the source and volume. Use the default configuration first. For larger or geographically sensitive jobs, select an appropriate proxy configuration only when the Actor supports it.

Is it legal to scrape this data?

Scraping rules vary by source, jurisdiction, data type, and intended use. Collect only data you are authorized to access, respect applicable terms and privacy laws, and avoid restricted or personal data misuse. This documentation is not legal advice.

Your feedback

If a field is missing, a source layout has changed, or you need a supported use case documented, open an issue on the Actor page with a reproducible input and run ID.