G2

Murat D.

CEO

Small-Business (50 or fewer emp.)

9/4/2026

"Turned blocked pages into an automated repricer"

5/5

Describe the project or task Scrapfly helped with:

Scrapfly provides a service that allows users to bypass anti-bot protections on web pages, enabling them to access and scrape data from sites that would otherwise block such activities. This service is particularly useful for businesses that rely on competitive pricing strategies, as it allows them to gather comprehensive data on competitor pricing and adjust their own prices accordingly. The service is designed to be easy to integrate into existing systems, requiring minimal setup and maintenance. Review collected by and hosted on G2.com.

What do you like best about Scrapfly?

The anti-bot bypass is the whole reason I use it. I pull competitor offers from a large retail marketplace whose product pages sit behind Kasada — plain server requests just get rejected, and the cheaper scraping APIs I tested barely get through. With Scrapfly it was a single parameter (asp=true, plus render_js=true for their client-rendered pages) and I had clean HTML back on the first attempt.

Integration-wise there's almost nothing to it: one GET request that returns the finished page. No headless browsers to babysit, no proxy pool, no infrastructure of my own. I wired it into my Python backend in an afternoon and it's been running unattended on a small server since.

On cost, pay-per-success makes the maths honest — failed attempts don't bill, so the monthly spend actually matches the data I got.

The unexpected upside was what it enabled: because I can now read the full offer list (every seller, price and shipping cost), I built an automatic repricer on top. It found listings where I was priced far below the cheapest competitor and could raise prices while still winning the buy box. That paid for the subscription many times over in the first week. Review collected by and hosted on G2.com.

What do you dislike about Scrapfly?

Reliability isn't quite 100%, and the failures are quiet. Every so often a request comes back with a 200 but the payload isn't the actual target page — an interstitial or a partial render. Nothing in the response makes that obvious, so my code initially treated those as "no data" and silently skipped listings. I had to add a retry loop (up to three attempts, then give up) before the results were dependable. A clearer signal that a returned page isn't a genuine target render would save everyone that guesswork.

I also had one call hang far longer than I expected instead of failing fast. Setting an explicit connect/read timeout on my side fixed it, but a documented or enforced upper bound would be better than each user discovering it the hard way.

On planning: it's hard to size a plan up front, because an ASP + JS-rendered call consumes noticeably more credits than a plain fetch. The free tier is gone after a few dozen of those, which is a short runway for a real evaluation. A simple "credits per call for this configuration" estimator would make choosing a tier much easier. Review collected by and hosted on G2.com.

Recommendations to others considering Scrapfly:

To improve reliability, consider implementing a more robust error detection mechanism that can identify when a returned page is not the intended target. Additionally, providing a documented timeout limit for requests could prevent unexpected delays.

For better planning, offering a clear estimator for credits consumed per call based on configuration would help users choose the appropriate plan more effectively. Review collected by and hosted on G2.com.

What problems is Scrapfly solving and how is that benefiting you?

Before, my pricing on the marketplace I sell on was effectively blind. To know what competitors charged I would have had to open each product page by hand, so in practice I didn't — prices sat untouched for weeks. I couldn't tell which listings were losing the buy box, and I had no way to automate it: my server simply couldn't read those pages because of the anti-bot protection.

Scrapfly solved exactly that one blocking piece. Now a job runs every three hours, fetches the full offer list for each active listing — every seller with their item price and shipping cost — and repositions my price automatically: undercut the cheapest competitor by one cent, match the sellers I don't want to undercut, never go below the floor I set per product.

Two concrete results. First, it surfaced listings priced far under the market: one sat at €19.99 while the cheapest competitor's total was €28.53, so I could raise it and still be the cheapest offer. Second, it caught the reverse — listings I'd silently lost the buy box on, like one at €149.99 against a competitor at €129.99.

The shipping detail matters more than I expected: a rival with a lower item price but paid shipping is often the more expensive total offer. You only see that with the complete offer list. Time spent on price checks went from "would take an hour per round" to zero, and the margin recovered on a single listing covered the monthly plan several times over. Review collected by and hosted on G2.com.