firecrawl-build-crawl
Firecrawl Build Crawl
Use this when the product needs many pages from the same site, not just one.
Use This When
- the feature targets a docs section, blog, or help center
- you need bulk extraction with path or depth boundaries
- the product should ingest or refresh a site section at once
Guidance
- Keep crawl scope narrow with path, depth, or page-count constraints.
- Prefer
/crawlover many manual/scrapecalls when the site structure is stable. - Treat this as secondary to
/scrape,/search, and/interactunless the feature is clearly site-wide.
When Not To Use It
- If you only need one known URL, use firecrawl-build-scrape.
More from firecrawl/skills
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
21.6Kfirecrawl-build-scrape
Integrate Firecrawl `/scrape` into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level.
21.6Kfirecrawl-build-interact
Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.
21.6Kfirecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
21.6Kfirecrawl-build-map
Integrate Firecrawl `/map` into product code for URL discovery on a known site. Use when a feature needs to find pages before scraping or crawling, especially on large docs sites, blogs, or help centers where the exact target URLs are not known yet.
554notion-spec-to-implementation
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
15