Prepared by SwarmSystem
Firecrawl turns any public web page into clean data a person or an AI agent can use. In July 2026 it shipped its biggest upgrade yet. This playbook covers what the tool does now, where it beats the tools you already run, and the exact plays an agency can run with it. Every claim here was either tested live on August 3, 2026, or pulled from Firecrawl's own docs. Nothing is repeated from marketing.
Verification status is marked on every capability: TESTED LIVE means we ran the call and kept the response. PER DOCS means it comes from official documentation we read but did not run.
On July 22, 2026 Firecrawl rebuilt its search. The short version: search now hands you the paragraph that answers the question, not the whole page. A scoring model reads each result and returns only the parts that match your query. Full pages are still there when you want them, one setting away.
Why that matters: an AI agent doing research used to swallow entire pages to answer one question. Most of that text was menus, footers, and filler. Excerpts cut that waste roughly ten times over, so agents answer faster and cost less to run. Firecrawl's own benchmark puts agents using this search at 94.7 percent on a standard fact-checking test, the best score of any provider they tested. That number is theirs, not ours, but our live test below backs the behavior.
We searched "emergency hvac repair austin tx" with a limit of 3 results. Here is the first result, exactly as returned:
| Field | Value returned |
|---|---|
| title | Same Day Emergency HVAC services? : r/Austin |
| description | "Hello, So hopefully this gets a prompt response, but my HVAC system pretty much crapped out on me and my family. We are renting a house, and our landlord..." |
| credits used | 2 (for all 3 results) |
Note what the description field holds. That is not the page's meta description. It is the actual text from inside the thread, picked because it matched the query. That is the new excerpt behavior working.
Firecrawl's core endpoints work without a key, rate limited but real. You can test everything below before signing up for anything. An endpoint is just a web address you send a request to and get data back.
Easier still: the playground at firecrawl.dev lets you run all of these in the browser. And if you use Claude Code, one command plugs Firecrawl straight into it: claude mcp add --transport http firecrawl https://mcp.firecrawl.dev/v2/mcp-oauth (MCP is the standard that lets AI tools call outside services directly).
The 2026 product is much bigger than a scraper. Here is the full surface with our verification status on each row.
| Capability | What it does in plain words | Status |
|---|---|---|
| Search | Web search that returns the matching text from each result, with city-level targeting | Tested live |
| Scrape | One page in, clean text or structured data out | Tested live |
| Map | Full page inventory of any site in one call | Tested live |
| Extract | You define the fields you want, it fills them from the page. We pulled company name and service list on the first try | Tested live |
| Crawl | Walks a whole site page by page and returns everything | Per docs |
| Monitor | Standing watch on pages, whole sites, or search results. Checks on a schedule, judges whether a change matters, alerts by webhook or email | Per docs |
| Interact | Drives a real browser: clicks, forms, dynamic content | Per docs |
| Agent | An autonomous researcher that plans its own multi-source lookups. Preview stage, 5 free runs a day | Per docs |
| Parse | PDF, Word, and spreadsheet files converted to AI-ready text | Per docs |
| Reusable extractors | Build an extractor for a site once, reuse it on every future pull | Untested |
| PII redaction | Strips names, emails, and addresses from results automatically | Untested |
| Research index | 3 million papers plus GitHub code, searchable for grounding technical claims | Per docs |
Also shipping: webhooks for async jobs, Python and Node libraries, a CLI, and the MCP server with the full tool set (scrape, map, search, crawl, extract, agent, interact, monitor, parse, research).
Most agencies already run a scraping tool, a browser automation tool, and an SEO data platform. Firecrawl does not replace all of them. This matrix is the honest split for a stack like ours: an SEO platform (Search Atlas in our case), a local browser automation setup (Playwright), a cold outreach platform (Instantly), and now Firecrawl. Use it to stop guessing which tool to reach for.
| The job | Winner | Why, in one sentence | Cost |
|---|---|---|---|
| One-off page grab | SEO platform's scraper | It is already connected and good enough for a single page | Included in plan |
| Same data fields from many sites, repeatedly | Firecrawl | Schema extraction returns the exact fields you define, from any site, without writing a parser per site | 1 credit per page |
| Full page inventory of a site | Firecrawl | Map returns every page with titles in one call, then you cross-check the sitemap | 1 credit per page |
| Web research for agents and briefs | Firecrawl | City-level targeting plus excerpts means you finally search as your client's town, not as yourself | 2 credits per 10 results |
| Standing watch on competitors or topics | Firecrawl | Monitor is the only tool in the stack that watches, judges the change, and alerts | 1 credit per check per page |
| Clicking through JS-heavy flows | Playwright | Local browser automation is free and already installed; metered remote browsing loses on price | Free |
| Rankings, keywords, backlinks | SEO platform | That is index data Firecrawl does not have | Included in plan |
| Local map rank grids | SEO platform | Purpose-built grid tracking, nothing to replace | Included in plan |
| Contact data and outreach | Outreach platform | Contact enrichment and sending live there; Firecrawl only researches the company itself | Included in plan |
| Writing content | Your AI writer, fed by Firecrawl | Firecrawl is the research input, not the writer | Search credits only |
The rule that falls out of the matrix: Firecrawl wins wherever the job is structured data from arbitrary sites, site inventories, geo-targeted research, or standing watch. It loses wherever a purpose-built tool already owns the data. Knowing the difference is what keeps the spend clean.
Each play below names the moment you reach for it, the exact call, what comes back, where it lands, and what it costs. The verdict chip on each area is honest: some of these are strong, some are partial, and we say which.
Your SEO platform still carries the core: rankings, keywords, site audits. Firecrawl adds the site intelligence around it.
This is where it earns its keep fastest. Every discovery call gets sharper when you walk in already knowing the prospect's business.
Strong on intelligence, zero on distribution. Firecrawl gathers what you write from; your publishing systems still do the publishing.
The same plays you sell to clients, pointed at yourself. This is the area most agencies skip, which is exactly why it works.
The general-purpose area. Any time the job is "get structured facts off public pages," this is now the default tool.
We held a paid Firecrawl key for months and barely used it. Writing this playbook forced the audit. Here is what it found, because the misses teach more than the wins:
| Miss | What it cost |
|---|---|
| The paid key sat unused | The 7-credit verification run behind this playbook may be the first real work the key ever did |
| A competitor research workflow sat blocked for weeks "waiting on a connector" | The official connector existed the whole time and takes one command to add |
| Nothing in the stack watches anything | Competitor changes reach us by hand, late, or never |
| Research ran without location targeting | A local visibility agency was searching as itself instead of as its clients' cities |
| Three scraping tools, no rule for which to use | Every scrape job started with a judgment call; the matrix above ends that |
| The July release notes sat unread until August | Two major features aged two weeks before anyone looked. A monitor can watch vendor changelogs too, including this vendor's |
Adoption order matters. Wire the cheap wins first, validate the watchers before building on them.
| Phase | Action | Done when |
|---|---|---|
| Now | Matrix in force: every scrape-shaped job checks the table above first | This playbook ships |
| This week | Connect the official MCP with the one-liner, run the first competitor teardown | First competitor profile lands in the research folder |
| This month | Fact sheets before every discovery call; search grounding in every page brief | Both are habit, not effort |
| Validate, then build | Two monitor pilots: one competitor watcher, one vendor changelog watcher. Judge alert quality for a month | Alerts prove useful, then the standing watcher becomes a real build |
Credits are the currency. One credit is one page scraped, crawled, mapped, or checked by a monitor. Search runs 2 credits per 10 results. Browser sessions run 2 credits per minute.
| Plan | Credits per month | Price |
|---|---|---|
| Free | 1,000 | $0 |
| Hobby | 5,000 | $16/mo billed yearly |
| Standard | 100,000 | $83/mo billed yearly |
| Growth | 500,000 | $333/mo billed yearly |
For scale: our entire verification run behind this playbook, five live calls including a full-content search, cost 7 credits. A monthly competitor teardown across three rivals runs about 30. The free tier covers a small shop's research month with room to spare.
Spend rules worth stealing: map a site before you crawl it, so you know the page count before you pay it. Budget research tasks at 50 credits or less. Cap monitors at 200 credits a month until their alerts prove useful. Unused credits do not roll over below the top plans, so size the plan to real usage, not ambition.
Prices are Firecrawl's published rates as of August 3, 2026. Check firecrawl.dev/pricing before deciding anything on cost.