Auto Trader UK Dealer Profile Scraper
Pricing
Pay per usage
Auto Trader UK Dealer Profile Scraper
Scrapes Auto Trader UK dealer profile pages and returns structured JSON with dealer name, contact details, stock counts, services, awards, reviews, and location data. Designed for Clay enrichment workflows.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Sabat Ali
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
What does Auto Trader UK Dealer Profile Scraper do?
Auto Trader UK Dealer Profile Scraper is an Apify Actor that extracts structured dealer data from Auto Trader UK dealer profile pages. For each dealer it returns name, address, contact details, opening hours, manufacturer approval status, brand badges, stock counts, services, awards, reviews, about text, coordinates, and more.
Run it on Apify for scheduling, API access, proxy rotation, and integrations — or locally with apify run.
Full documentation: ./DOCUMENTATION.md — input/output reference, architecture, field logic, API, troubleshooting, and Clay mapping.
Why use this Actor?
- Clay-ready fields — Maps to LAYER1 columns (
at_dealer_profile_url,at_manufacturer_approved, stock counts, services, awards, reviews, etc.) - Two input modes — Direct profile URLs (fast) or root domains (auto-find AT profile)
- Efficient — Parses embedded
AT_APOLLO_STATEJSON; no browser per profile - Franchised + independent — Tested on dealers such as Citygate Kia Slough and Professional Motors Limited
How to use
- Create an Apify account.
- Open the Actor → Input tab.
- Add Dealer Profile URLs and/or Root Domains.
- Start the run → download results from Dataset (JSON, CSV, Excel).
Local run
pip install -r requirements.txtplaywright install chromiumapify run
Input (summary)
| Field | Description |
|---|---|
dealer_urls | AT dealer profile URLs |
root_domains | Website domains (Actor finds AT profile) |
max_items | Limit dealers (0 = unlimited) |
max_concurrency | Parallel requests (default 10) |
proxyConfiguration | Optional Apify Proxy |
See ./DOCUMENTATION.md#7-input-reference for full details.
Output (summary)
One JSON object per dealer. Example (franchised):
{"dealer_name": "Citygate Kia Slough","at_dealer_profile_url": "https://www.autotrader.co.uk/dealers/citygate-kia-slough-10008283?channel=cars","manufacturer_approved": true,"brand_badges": ["KIA"],"used_stock_count": 46,"new_stock_count": 10,"website": "http://www.citygate.co.uk/","review_score": 4.7,"review_count": 114,"dealer_type": "franchised"}
All 25 fields are documented in ./DOCUMENTATION.md#8-output-reference.
Data table
| Field | Description |
|---|---|
dealer_name | Trading name |
at_dealer_profile_url | Profile URL |
address / postcode | Location |
phone / website / email | Contact |
opening_hours | Opening times |
manufacturer_approved | Approved badge |
brand_badges | Franchise brands |
used_stock_count / new_stock_count | Stock |
services / awards | Lists |
review_score / review_count | Reviews |
about_text / family_owned / years_established | About |
lat / long | Coordinates |
dealer_type | franchised or independent |
scraped_at | UTC timestamp |
Pricing / cost
- URL input: Low compute (~target $0.005/profile on Apify).
- Root domain input: Higher (Playwright search + profile matching).
- Enable Apify Proxy only if you see 403 errors.
Tips
- Prefer
dealer_urlswhen you already have Auto Trader links. - Use
max_itemsfor test runs. - See ./DOCUMENTATION.md#20-troubleshooting for errors.
FAQ
Public Auto Trader dealer pages only — no listings, no login. You are responsible for ToS compliance.
Issues? Apify Console → Actor → Issues tab, or see full ./DOCUMENTATION.md.