Skip to content

docs: align English copy with current product names and positioning - #1562

Closed
erikengervall wants to merge 1 commit into
mainfrom
capy/align-english-copy-with
Closed

erikengervall wants to merge 1 commit into
mainfrom
capy/align-english-copy-with

Conversation

@erikengervall

Copy link
Copy Markdown
Contributor

Updates English pages and shared snippets where the copy still uses retired names, old package names, or dated taglines. Localized copies are left to the translation pipeline.

Package names and links

  • Python installs now use pip install firecrawl (quickstarts, advanced scraping guide, capabilities page, and the shared v2 install and proxy-retry snippets that feed the SDK and feature pages). firecrawl-py keeps working as an alias.
  • JS imports in the Search page, the web-scale monitoring page, and the v2 Monitor snippets now import from firecrawl instead of @mendable/firecrawl-js.
  • The v2 crawl WebSocket sample crawls https://firecrawl.dev instead of https://mendable.ai, and the v2 search sample output uses the firecrawl/firecrawl repo title.

Retired names

  • Agent page: Agent is described as replacing the legacy /extract endpoint, and the comparison table is labelled accordingly.
  • Search page: drops the FIRE-1 mention from the scrape-options note (v2 scrape options have no agent option).
  • Billing: the FIRE-1 row is renamed to the v1 scrape agent option it actually bills.
  • Product lists that named "extract" as a capability now name Agent where the surface has it (CLI on AI onboarding and OpenClaw, Composio, the Stripe Projects endpoint list), and the Hermes card says scrape. The Lovable table describes structured data as Scrape's JSON format, since the Lovable connector has no extract action.

Taglines and descriptions

  • Introduction, LLM SDK guides (Claude, Gemini, LangChain, OpenAI), SDK page descriptions, Express/NestJS/ASP.NET Core quickstarts, SourceSync, Enterprise, and a few use-case pages drop "web data API", "turn websites into markdown", and "LLM-ready data" phrasing in favour of the current wording (the context API for AI agents; search, scrape, and interact; LLM-ready context).
  • Scrape and Parse descriptions and sample outputs updated to match.
  • The "Ready to build?" sidebar card now reads "Search, scrape, and interact with the web for free".
  • Observability use case points to Monitor for scheduled change detection before describing the do-it-yourself scrape pipeline.
  • ADK guide: FIRECRAWL_API_KEY is documented as optional with the cloud API, matching the MCP server's keyless mode for scrape and search.
  • Brand casing fix in one Learn tutorial comment.

Left as is on purpose

  • LangChain, LlamaIndex, and CrewAI install lines keep @mendable/firecrawl-js / firecrawl-py, because those packages declare the alias as their dependency.
  • Zapier, Make, Pipedream, LangChain, and LlamaIndex pages keep "extract" where it is the third-party action or mode name.
  • Webhook event types, Lockdown availability, SIEM event sources, the Ask job list, and the key-restrictions v0 note still mention extract or v0, because those endpoints still answer and the text documents their behaviour.
  • Keyless wording on the MCP, rate-limits, Developer, and AI onboarding pages already matches the API's per-day keyless tier, so it is unchanged.

Needs a human look

  • Sidebar CTA wording (ready-to-build-cta.js) shows on every page.
  • Billing row label "v1 scrape agent option".
  • Composio row swapped from Extract to Agent, and Lovable row relabelled "Structured data".
  • Sample outputs (search titles, scrape ogDescription, company_mission) use current taglines, not a captured response.
  • Use-case and LLM-guide one-liners (overview, AI platforms, developers & MCP, observability, Enterprise intro, SourceSync).
  • The Observer template cards on the competitive-intelligence, investment-finance, and observability pages still point to the firecrawl-observer repo; consider swapping them for Monitor.

Checks: scripts/check-locale-api-literals-selftest.sh and scripts/check-extraction-hostile-markdown.sh pass locally.

Open in Capy

@mintlify

mintlify Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
firecrawl 🟢 Ready View Preview Oct 9, 2026, 2:30 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

@capy-ai

capy-ai Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Closing in favour of smaller PRs, one change each, all branched from main so they can merge independently. Together they carry exactly this diff:

@capy-ai capy-ai Bot closed this Oct 9, 2026

This branch was successfully deployed

1 active deployment
staging — 544640e6 Deployed Oct 9, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant