🔍🚙 AutoScout24 Scraper (PPR)
Pricing
$1.49 / 1,000 results
🔍🚙 AutoScout24 Scraper (PPR)
Effortlessly scrape car data from the largest pan-European online car marketplace, AutoScout24. Get access to millions of entries of cars, motorbikes, etc. across Europe. Fast, cheap & reliable. Pay-per-result version.
5.0 (1)
Pricing
$1.49 / 1,000 results
3
Total users
42
Monthly users
24
Runs succeeded
>99%
Issues response
4.8 hours
Last modified
6 days ago
Actor scrapes “ You might also like ” suggestions – results include cars outside the requested make/year/price filter
Closed
Expected behaviour When I pass a filtered URL, the actor should return only listings that satisfy the query parameters (in my case : brand VW, year 2020, price €72 000 – 74 999).
Actual behaviour After the two matching VW listings, the actor continues to scrape the “Könnte Ihnen auch gefallen[You might also like ]” section and adds completely unrelated cars (e.g. BMW, Porsche). Because those extra rows count towards resultLimitPerThread, the 400-item limit is consumed by noise and I can’t cover all relevant listings with my split-up URLs.
Minimal reproducible input
{ "startUrls": [ "https://www.autoscout24.at/lst/vw?atype=C&custtype=D&cy=A&desc=0&fregfrom=2020&fregto=2020&powertype=kw&pricefrom=72000&priceto=74999&sort=standard&source=detailsearch&ustate=N%2CU" ], "resultLimitPerThread": 400, "reviewLimit": 0, "lightningMode": false, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] } } Observed output (excerpt)
brand model year price VW Touareg 2020 72 500 VW Touareg 2020 73 900 BMW X5 2022 77 900 Porsche Cayenne 2021 89 000 …
Impact I run weekly bulk scans and rely on each split-URL staying within 400 items. The extra suggestion listings break that assumption and force me to discard large parts of every dataset.
Request
Either skip the “You might also like” container entirely, or
post-filter the results to match the original query parameters (make, year, price, etc.), or
expose an option like "excludeSuggestions": true".
Thanks a lot – with this fix I could integrate the actor into our automated pipeline.
MerialSHK
look samething : https://console.apify.com/view/runs/BFhG7tqcSVu6mDhfK
Hey,
Thanks for reporting this issue! I understand the nature of the problem. We will fix it soon and notify you via this thread once the solution is live.
Hi again,
I wanted to inform you that I've just released a fix for this issue and it should not include any indirect results. Please check it out and tell me if it works as expected or not.
This scraper was designed to not include them originally, but somehow, the URL you used (https://www.autoscout24.at/lst/vw?atype=C&custtype=D&cy=A&desc=0&fregfrom=2020&fregto=2020&powertype=kw&pricefrom=72000&priceto=74999&sort=standard&source=detailsearch&ustate=N%2CU) contained "vw" instead of "volkswagen" (it automatically translates "vw" to "volkswagen" when you open the link).
Can I ask you where did you obtain this URL? Because the standard brand keyname seems to be "volkswagen".
Have a great day, 3x1t
MerialSHK
Hi 3x1t,
Thanks for the lightning-fast fix—I honestly didn’t expect the issue to be solved within an hour. You’re amazing! 🚀
I’ve already run a handful of quick tests and everything looks good so far. Later today I’ll kick off roughly 2,000 additional runs; if anything crops up, I’ll let you know right away.
Thanks again for the great work.
By the way, the “VW” shorthand actually came straight from AutoScout’s own suggestions, but you’re right—sometimes the site silently converts it to “Volkswagen.”
Best, Merial
