decent list, but a couple lines are just asserted without anything backing them. calling scrapy number one and serpapi the market leader and original platform without any numbers or share data is the same problem the article should be avoiding.
the pydoll catch is the real one though, it says best for stealth then a few paragraphs later admits stealth doesn't guarantee access, that's a legit contradiction worth pointing out.
would've liked to see apify named directly since the crawlee section is obviously pointing at some hosted platform without saying who, and the self hosted proxy story is missing entirely while the managed side gets covered fine. also this platforms should be these platforms.
from experience, check the network tab before reaching for a browser tool, half the time the js heavy page is just calling a json endpoint underneath and you didn't need playwright at all.
Furqan Ashraf
We are small team, who loves to code.
The credit-cost point in the ScrapingBee section is worth checking when comparing these tools. I work on APIFreaks (apifreaks.com/api/web-scraper), and our scraper has a similar trade-off: a static request uses 4 credits, while turning on JavaScript rendering uses 40.
For anyone testing the options here, I’d run the same few URLs in both modes and compare the fields returned alongside the credits used. Sometimes the data is already in the initial HTML, so you can save the browser rendering for pages that actually need it.