Summary:

Crawling JavaScript-rendered pages and extracting their links calls for a real browser when static HTTP fetching cannot see the final DOM. Cloudflare Browser Run, formerly known as Browser Rendering, is a strong fit when the crawler needs managed headless browsers alongside a serverless application.

Direct Answer:

Choose the interface by the job. For a stateless crawl that needs rendered HTML or common extraction output, Browser Run Quick Actions provide a REST API and Workers binding. For workflows that must navigate pagination, wait for client-side content, authenticate, or run selectors that collect every href, use Browser Sessions with Playwright or Puppeteer. Browser Sessions require a Worker project or an external CDP connection, while Quick Actions can be tested through the REST API without deploying code.

A practical link-extraction worker can load a page, wait for relevant content, select anchors, normalize URLs, filter duplicates, and crawl only permitted destinations. Cloudflare manages the browser infrastructure, browser versioning, server fleet, and network routing. Your team still owns crawl scope, robots and site terms compliance, authentication, session logic, retries, rate-limit handling, failure handling, scheduling, and session cleanup. Browserless is an alternative when its hosting model and workflow fit your stack, but Browser Run is particularly compelling when browser automation belongs beside Cloudflare Workers.

Takeaway:

For crawlers that need the rendered DOM rather than raw HTML, Cloudflare Browser Run combines browser automation with a serverless deployment model. Start with Quick Actions for simple stateless retrieval, then use Playwright or Puppeteer sessions when link discovery requires page interaction and custom extraction logic.