Firecrawl Reviews & Product Details

Firecrawl is the first tool every engagement touches. One crawl of a practice's site gives us clean, main-content markdown for every page, which becomes the source material our agent writers to rebuild from, and the map call tells us what the sitemap forgot to mention. We lean on it hardest in two places: inventorying a client's existing copy before a migration or rebuild, and scraping the top-ranking competitor pages so our research stage knows the structure and depth it has to beat. The markdown output is clean enough that it goes straight into our review pipeline without hand cleanup, which is the part that saves us the most time. Review collected by and hosted on G2.com.

Our only recurring friction are the sites behind Cloudflare challenges, where we drop to a fallback fetcher, and credit exhaustion mid-crawl, which we now check for before launching. Review collected by and hosted on G2.com.

It turns any web page into clean text an AI agent can read, and it does web search in the same tool. We used it from Claude to research about a dozen competitor websites in Spain: features, prices and policy pages. It handled sites that plain HTTP requests struggled with, and it took almost no setup. Review collected by and hosted on G2.com.

Credits run out quickly during a research session, and when they do, every request stops at once, with no warning beforehand. It isn't always clear how many credits a call will use before running it. Review collected by and hosted on G2.com.

What I like best about Firecrawl is its ability to turn event information from many different association websites into structured, usable data. Mosaic monitors associations that all organize their calendars differently, so Firecrawl gives us one reliable way to access those pages without building a separate solution for every website. It has made it possible for Mosaic to keep growing its event coverage while saving significant development time. Review collected by and hosted on G2.com.

What I dislike most is that credit usage can add up quickly when monitoring many association calendars, especially when pages must be revisited or followed to individual event details. It can also be difficult to understand exactly why a particular scrape consumed a certain number of credits or why usage shown in the dashboard is sometimes delayed. More transparent, real-time usage reporting and clearer controls for avoiding unnecessary repeat scrapes would make budgeting and optimization much easier. Review collected by and hosted on G2.com.

What I like best is how much real web data I get for very little. I run a B2B supplier-matching platform that searches the live web and reads each company’s own pages. Firecrawl handles both the search and the page reading through one simple API, so I didn’t have to build and maintain my own crawling setup. A typical refresh for an existing brief costs me about 28 credits, roughly $0.11 on the $19 plan, which is very affordable for what it does.

I also like that the usage is easy to follow. I can see how many credits went to searches and how many to scrapes, which helped me understand exactly what each run costs. And when my balance ran out, the API returned a clear “insufficient credits” error, which was easy to catch and handle in my code instead of failing silently. Review collected by and hosted on G2.com.

I found out my balance was empty the hard way: a run failed with an “insufficient credits” error partway through, and I only realised the cause afterwards. A clearer warning before the balance runs low would have saved me a failed run and some debugging time. Review collected by and hosted on G2.com.

The markdown output is clean and consistent enough to feed straight into an LLM without extra parsing, and it handles JavaScript-rendered pages that plain HTTP fetchers miss. Having scrape, search, crawl and structured JSON extraction behind one API — plus the MCP server — makes it easy to drop into an agent workflow without gluing several tools together. Review collected by and hosted on G2.com.

Credits are consumed even when a run returns nothing useful, for example on pages that hit anti-bot walls or render errors, so you have to babysit usage on larger crawls. Latency on JS-heavy pages can also be noticeable, and results occasionally come from cache rather than a live fetch, which matters when the data changes often. Review collected by and hosted on G2.com.

What I like most is how Firecrawl turns website content into structured, usable data without a complicated scraping workflow. I've used it to collect and organize information about museums and cultural attractions for travel research. It made the research process much more efficient and helped prepare information for AI-assisted workflows. The ability to extract useful content from multiple pages is particularly valuable. Review collected by and hosted on G2.com.

I haven't encountered any major problems with Firecrawl. For larger research projects, keeping track of usage credits and estimating how many pages to process takes some planning. More transparent usage forecasting would be helpful. Review collected by and hosted on G2.com.

It turns any page into clean, usable data in seconds. I used it to check domain availability while naming my company, to confirm my new website was live after deployment, and to pull market data for research. No scraper setup, no code to maintain. The output is clean enough to use straight away, and it handles pages that normal fetch tools fail on. Review collected by and hosted on G2.com.

Rate limits kick in quickly when you run several lookups back to back, so bulk checks need to be paced or batched. It would help to see remaining credits and limits more clearly before starting a larger job. Review collected by and hosted on G2.com.

I used almost 1,000 credits in one day researching cars. At some point, “I’m just looking at a few vehicles” became a data acquisition project. Firecrawl enabled this behavior instead of staging an intervention.

I also had a genuinely good support experience. A billing-plan change put me on an extra 5,000-credit buy-up I didn’t want. I contacted support, and they put me back on Hobby 5K and refunded the difference the same day.

Apparently, you can just fix a customer’s problem. Other subscription companies may want to write that down. Review collected by and hosted on G2.com.

The billing transition could have been clearer. I wanted my regular plan, not the extended director’s cut with bonus credits and additional financial consequences. Extra purchases should be something I deliberately choose.

Support fixed it promptly, which I appreciate, but I’d rather not need a support ticket to get back to what I intended to pay for.

Also, keep an eye on your credit usage. “One more page” is how I ended up doing automotive research with the resource consumption of a small intelligence agency. Review collected by and hosted on G2.com.

It is a set and forget tool, you don't ever have to worry about it failing, it just does what it needs to without issues. Review collected by and hosted on G2.com.

It is expensive. I would say it is actually overly expensive, more expensive than most others. Sad but true. Review collected by and hosted on G2.com.

It has an ease of use that isn't found on all similar sites. It integrates well with Claude and my agents. Once it’s connected, the scraped content flows straight into the work I’m doing without a lot of manual handling. Review collected by and hosted on G2.com.

I have yet to find anything about it that I dislike, frankly. I’ve only been using it for about a month, so I’m still learning where it fits best. Nothing is a major problem yet, but I’d like more clarity on usage limits as my volume grows. Review collected by and hosted on G2.com.