Kliao/browser rendering terminology rename (#29670)

* Rename REST API -> Quick Actions, dissolve Workers Bindings, update terminology

- Rename 'REST API' to 'Quick Actions' across all current BR docs
- Move workers-bindings content to how-to/ and features/
- Delete workers-bindings/index.mdx navigation page
- Update URL paths /rest-api/ -> /quick-actions/ everywhere
- Use 'Browser Sessions' as billing category for Puppeteer/Playwright/CDP
- Keep 'browser automation' as descriptive term in natural prose
- Update pricing/limits to clarify Quick Actions vs Browser Sessions billing
- Historical changelogs/release notes: URL paths only, preserve display text
- Fix chained redirects to point directly to final destinations
- Add redirects for all old /rest-api/ and /workers-bindings/ paths

* Reframe integration methods with Quick Actions vs Browser Sessions overview

* Rewrite reuse-sessions intro: explain feature, scope to Browser Sessions, clarify disconnect vs DO approaches

* Update automatic-request-headers.mdx

nitpick - since puppeteer + playwright use CDP

* Fix broken internal links to deleted workers-bindings page

- Replace /browser-rendering/workers-bindings/ with /browser-rendering/#integration-methods in release notes, changelogs
- Update link in workers websocket changelog to point to /browser-rendering/
- Fixes starlight-links-validator CI failure

* Add CDP instructions to custom fonts, rename section to Browser sessions

- Rename 'Puppeteer and Playwright' section to 'Browser sessions' to cover all browser session methods
- Update intro bullets to include CDP alongside Puppeteer and Playwright
- Add explanatory note that examples use Workers Bindings but CDP works the same way
- Add CDP connection example subsection showing puppeteer.connect() with WebSocket endpoint

* Fix broken link: update /rest-api/ to /quick-actions/ in workers-ai markdown-conversion page

* Switch dynamic redirects for single files into static redirects

* Create new paragraph (add new line)

* Add space

* Reorganize imports

* Switch to relative URL path in release note

* Small update

* Small fixes and updates

* Update src/content/docs/browser-rendering/features/custom-fonts.mdx

Co-authored-by: Pedro Sousa <680496+pedrosousa@users.noreply.github.com>

* Update src/content/docs/browser-rendering/how-to/pdf-generation.mdx

Co-authored-by: Pedro Sousa <680496+pedrosousa@users.noreply.github.com>

---------

Co-authored-by: Pedro Sousa <680496+pedrosousa@users.noreply.github.com>

Author: kathayl

public/__redirects

@@ -280,13 +280,14 @@
 /bots/concepts/bot/verified-bots/web-bot-auth/ /bots/reference/bot-verification/web-bot-auth/ 301
 /bots/concepts/bot/verified-bots/overview/ /bots/concepts/bot/verified-bots/ 301
 /bots/frequently-asked-questions/ /bots/ 301
-/browser-rendering/get-started/browser-rendering-with-DO/ /browser-rendering/workers-bindings/browser-rendering-with-do/ 301
-/browser-rendering/get-started/reuse-sessions/ /browser-rendering/workers-bindings/reuse-sessions/ 301
-/browser-rendering/get-started/screenshots/ /browser-rendering/workers-bindings/screenshots/ 301
-/browser-rendering/workers-binding-api/ /browser-rendering/workers-bindings/ 301
-/browser-rendering/workers-binding-api/screenshots/ /browser-rendering/workers-bindings/screenshots/ 301
-/browser-rendering/workers-binding-api/browser-rendering-with-do/ /browser-rendering/workers-bindings/browser-rendering-with-do/ 301
-/browser-rendering/workers-binding-api/reuse-sessions/ /browser-rendering/workers-bindings/reuse-sessions/ 301
+
+/browser-rendering/get-started/browser-rendering-with-DO/ /browser-rendering/how-to/browser-rendering-with-do/ 301
+/browser-rendering/get-started/reuse-sessions/ /browser-rendering/features/reuse-sessions/ 301
+/browser-rendering/get-started/screenshots/ /browser-rendering/how-to/deploy-worker/ 301
+/browser-rendering/workers-binding-api/ /browser-rendering/get-started/#browser-sessions 301
+/browser-rendering/workers-binding-api/screenshots/ /browser-rendering/how-to/deploy-worker/ 301
+/browser-rendering/workers-binding-api/browser-rendering-with-do/ /browser-rendering/how-to/browser-rendering-with-do/ 301
+/browser-rendering/workers-binding-api/reuse-sessions/ /browser-rendering/features/reuse-sessions/ 301
 /browser-rendering/platform/ /browser-rendering/ 301
 /browser-rendering/platform/puppeteer/ /browser-rendering/puppeteer/ 301
 /browser-rendering/platform/playwright/ /browser-rendering/playwright/ 301
@@ -296,6 +297,10 @@
 /browser-rendering/platform/pricing/ /browser-rendering/pricing/ 301
 /browser-rendering/platform/browser-close-reasons/ /browser-rendering/reference/browser-close-reasons/ 301
 /browser-rendering/platform/stagehand/ /browser-rendering/stagehand/ 301
+/browser-rendering/workers-bindings/reuse-sessions/ /browser-rendering/features/reuse-sessions/ 301
+/browser-rendering/workers-bindings/browser-rendering-with-do/ /browser-rendering/how-to/browser-rendering-with-do/ 301
+/browser-rendering/workers-bindings/screenshots/ /browser-rendering/how-to/deploy-worker/ 301
+/browser-rendering/workers-bindings/ /browser-rendering/get-started/#browser-sessions 301
 
 # byoip
 /byoip/about/dynamic-advertisement/ /byoip/concepts/dynamic-advertisement/ 301
@@ -2459,7 +2464,8 @@
 /*/index.html.md /:splat/index.md 301
 /1.1.1.1/other-ways-to-use-1.1.1.1/* /1.1.1.1/additional-options/:splat 301
 /changelog-next/* /changelog/post/:splat 301
-/browser-rendering/quick-actions-rest-api/* /browser-rendering/rest-api/:splat 301
+/browser-rendering/rest-api/* /browser-rendering/quick-actions/:splat 301
+/browser-rendering/quick-actions-rest-api/* /browser-rendering/quick-actions/:splat 301
 /*/sitemap.xml /sitemap-index.xml 301
 /api-security/* /api-shield/:splat 301
 /api-shield/products/* /api-shield/security/:splat 301

src/content/changelog/browser-rendering/2025-02-27-br-rest-api-beta.mdx

@@ -32,4 +32,4 @@ curl -X POST 'https://api.cloudflare.com/client/v4/accounts/<accountId>/browser-
   --output "screenshot.webp"
 ```
 
-Learn more in our [documentation](/browser-rendering/rest-api/).
+Learn more in our [documentation](/browser-rendering/quick-actions/).

src/content/changelog/browser-rendering/2025-04-07-br-free-ga-playwright.mdx

@@ -8,7 +8,7 @@ date: 2025-04-07
 
 We’re excited to announce Browser Rendering is now available on the [Workers Free plan](https://www.cloudflare.com/plans/developer-platform/), making it even easier to prototype and experiment with web search and headless browser use-cases when building applications on Workers.
 
-The Browser Rendering **[REST API](/browser-rendering/rest-api/) is now Generally Available**, allowing you to control browser instances from outside of Workers applications. We've added three new endpoints to help automate more browser tasks:
+The Browser Rendering **[REST API](/browser-rendering/quick-actions/) is now Generally Available**, allowing you to control browser instances from outside of Workers applications. We've added three new endpoints to help automate more browser tasks:
 
 - **Extract structured data** – Use `/json` to retrieve structured data from a webpage.
 - **Retrieve links** – Use `/links` to pull all links from a webpage.
@@ -26,7 +26,7 @@ curl -X 'POST' 'https://api.cloudflare.com/client/v4/accounts/<accountId>/browse
 
 ```
 
-For the full list of endpoints, check out our [REST API documentation](/browser-rendering/rest-api/). You can also interact with Browser Rendering via the [Cloudflare TypeScript SDK](https://github.com/cloudflare/cloudflare-typescript).
+For the full list of endpoints, check out our [REST API documentation](/browser-rendering/quick-actions/). You can also interact with Browser Rendering via the [Cloudflare TypeScript SDK](https://github.com/cloudflare/cloudflare-typescript).
 
 We also recently landed support for [Playwright](/browser-rendering/playwright/) in Browser Rendering for browser automation from Cloudflare [Workers](/workers/), in addition to [Puppeteer](/browser-rendering/puppeteer/), giving you more flexibility to test across different browser environments.
 

src/content/changelog/browser-rendering/2025-07-22-br-local-dev.mdx

@@ -8,4 +8,4 @@ date: 2025-07-22T11:00:00Z
 
 You can now run your Browser Rendering locally using `npx wrangler dev`, which spins up a browser directly on your machine before deploying to Cloudflare's global network. By running tests locally, you can quickly develop, debug, and test changes without needing to deploy or worry about usage costs.
 
-Get started with this [example guide](/browser-rendering/workers-bindings/screenshots/) that shows how to use Cloudflare's [fork of Puppeteer](/browser-rendering/puppeteer/) (you can also use [Playwright](/browser-rendering/playwright/)) to take screenshots of webpages and store the results in [Workers KV](/kv/).
+Get started with this [example guide](/browser-rendering/how-to/deploy-worker/) that shows how to use Cloudflare's [fork of Puppeteer](/browser-rendering/puppeteer/) (you can also use [Playwright](/browser-rendering/playwright/)) to take screenshots of webpages and store the results in [Workers KV](/kv/).

src/content/changelog/browser-rendering/2025-07-28-br-pricing.mdx

@@ -9,8 +9,8 @@ date: 2025-07-28T12:00:00Z
 We’ve launched pricing for [Browser Rendering](/browser-rendering/), including a free tier and a pay-as-you-go model that scales with your needs. Starting **August 20, 2025**, Cloudflare will begin billing for Browser Rendering.
 
 There are two ways to use Browser Rendering. Depending on the method you use, here’s how billing will work:
-- [**REST API**](/browser-rendering/rest-api/): Charged for **Duration** only ($/browser hour)
-- [**Workers Bindings**](/browser-rendering/workers-bindings/): Charged for both **Duration** and **Concurrency** ($/browser hour and # of concurrent browsers)
+- [**REST API**](/browser-rendering/quick-actions/): Charged for **Duration** only ($/browser hour)
+- [**Browser Sessions**](/browser-rendering/#integration-methods): Charged for both **Duration** and **Concurrency** ($/browser hour and # of concurrent browsers)
 
 Included usage and pricing by plan
 

src/content/changelog/browser-rendering/2025-09-25-br-playwright-ga-stagehand-limits.mdx

@@ -9,7 +9,7 @@ date: 2025-09-25T12:00:00Z
 We’re shipping three updates to Browser Rendering:
 - Playwright support is now Generally Available and synced with [Playwright v1.55](https://playwright.dev/docs/release-notes#version-155), giving you a stable foundation for critical automation and AI-agent workflows.
 - We’re also adding [Stagehand support (Beta)](/browser-rendering/stagehand/) so you can combine code with natural language instructions to build more resilient automations.
-- Finally, we’ve tripled [limits](/browser-rendering/limits/#workers-paid) for paid plans across both the [REST API](/browser-rendering/rest-api/) and [Workers Bindings](/browser-rendering/workers-bindings/) to help you scale.
+- Finally, we’ve tripled [limits](/browser-rendering/limits/#workers-paid) for paid plans across both the [REST API](/browser-rendering/quick-actions/) and [Browser Sessions](/browser-rendering/#integration-methods) to help you scale.
 
 To get started with Stagehand, refer to the [Stagehand](/browser-rendering/stagehand/) example that uses Stagehand and [Workers AI](/workers-ai/) to search for a movie on this [example movie directory](https://demo.playwright.dev/movies), extract its details using natural language (title, year, rating, duration, and genre), and return the information along with a screenshot of the webpage.
 

src/content/changelog/browser-rendering/2026-03-04-br-rest-api-limit-increase.mdx

@@ -10,17 +10,17 @@ date: 2026-03-04
 
 ![Browser Rendering REST API rate limit increased from 3 to 10 requests per second](~/assets/images/changelog/browser-rendering/rest-api-limit-increase.png)
 
-The [REST API](/browser-rendering/rest-api/) lets you perform common browser tasks with a single API call, and you can now do it at a higher rate.
+The [REST API](/browser-rendering/quick-actions/) lets you perform common browser tasks with a single API call, and you can now do it at a higher rate.
 
-- [/content - Fetch HTML](/browser-rendering/rest-api/content-endpoint/)
-- [/screenshot - Capture screenshot](/browser-rendering/rest-api/screenshot-endpoint/)
-- [/pdf - Render PDF](/browser-rendering/rest-api/pdf-endpoint/)
-- [/markdown - Extract Markdown from a webpage](/browser-rendering/rest-api/markdown-endpoint/)
-- [/snapshot - Take a webpage snapshot](/browser-rendering/rest-api/snapshot/)
-- [/scrape - Scrape HTML elements](/browser-rendering/rest-api/scrape-endpoint/)
-- [/json - Capture structured data using AI](/browser-rendering/rest-api/json-endpoint/)
-- [/links - Retrieve links from a webpage](/browser-rendering/rest-api/links-endpoint/)
+- [/content - Fetch HTML](/browser-rendering/quick-actions/content-endpoint/)
+- [/screenshot - Capture screenshot](/browser-rendering/quick-actions/screenshot-endpoint/)
+- [/pdf - Render PDF](/browser-rendering/quick-actions/pdf-endpoint/)
+- [/markdown - Extract Markdown from a webpage](/browser-rendering/quick-actions/markdown-endpoint/)
+- [/snapshot - Take a webpage snapshot](/browser-rendering/quick-actions/snapshot/)
+- [/scrape - Scrape HTML elements](/browser-rendering/quick-actions/scrape-endpoint/)
+- [/json - Capture structured data using AI](/browser-rendering/quick-actions/json-endpoint/)
+- [/links - Retrieve links from a webpage](/browser-rendering/quick-actions/links-endpoint/)
 
-If you use the [Workers Bindings](/browser-rendering/workers-bindings/) method, increases to concurrent browser and new browser limits are coming soon. Stay tuned.
+If you use the [Browser Sessions](/browser-rendering/#integration-methods) method, increases to concurrent browser and new browser limits are coming soon. Stay tuned.
 
 For full details, refer to the [Browser Rendering limits page](/browser-rendering/limits/).

src/content/changelog/browser-rendering/2026-03-10-br-crawl-endpoint.mdx

@@ -8,7 +8,7 @@ date: 2026-03-10
 
 _Edit: this post has been edited to clarify crawling behavior with respect to site guidance._
 
-You can now crawl an entire website with a single API call using [Browser Rendering](/browser-rendering/)'s new [`/crawl` endpoint](/browser-rendering/rest-api/crawl-endpoint/), available in open beta. Submit a starting URL, and pages are automatically discovered, rendered in a headless browser, and returned in multiple formats, including HTML, Markdown, and structured JSON. The endpoint is a [signed-agent](https://developers.cloudflare.com/bots/concepts/bot/signed-agents/) that respects robots.txt and [AI Crawl Control](https://www.cloudflare.com/ai-crawl-control/) by default, making it easy for developers to comply with website rules, and making it less likely for crawlers to ignore web-owner guidance. This is great for training models, building RAG pipelines, and researching or monitoring content across a site.
+You can now crawl an entire website with a single API call using [Browser Rendering](/browser-rendering/)'s new [`/crawl` endpoint](/browser-rendering/quick-actions/crawl-endpoint/), available in open beta. Submit a starting URL, and pages are automatically discovered, rendered in a headless browser, and returned in multiple formats, including HTML, Markdown, and structured JSON. The endpoint is a [signed-agent](https://developers.cloudflare.com/bots/concepts/bot/signed-agents/) that respects robots.txt and [AI Crawl Control](https://www.cloudflare.com/ai-crawl-control/) by default, making it easy for developers to comply with website rules, and making it less likely for crawlers to ignore web-owner guidance. This is great for training models, building RAG pipelines, and researching or monitoring content across a site.
 
 Crawl jobs run asynchronously. You submit a URL, receive a job ID, and check back for results as pages are processed.
 
@@ -39,5 +39,5 @@ Available on both the Workers Free and Paid plans.
 
 **Note**: the /crawl endpoint cannot bypass Cloudflare bot detection or captchas, and self-identifies as a bot.
 
-To get started, refer to the [crawl endpoint documentation](/browser-rendering/rest-api/crawl-endpoint/). 
+To get started, refer to the [crawl endpoint documentation](/browser-rendering/quick-actions/crawl-endpoint/). 
 If you are setting up your own site to be crawled, review the [robots.txt and sitemaps best practices](/browser-rendering/reference/robots-txt/).

src/content/changelog/workers/2025-10-31-increased-websocket-message-size-limit.mdx

@@ -8,7 +8,7 @@ products:
 date: 2025-10-31
 ---
 
-Workers, including those using [Durable Objects](/durable-objects/) and [Browser Rendering](/browser-rendering/workers-bindings/), may now process WebSocket messages up to 32 MiB in size. Previously, this limit was 1 MiB.
+Workers, including those using [Durable Objects](/durable-objects/) and [Browser Rendering](/browser-rendering/), may now process WebSocket messages up to 32 MiB in size. Previously, this limit was 1 MiB.
 
 This change allows Workers to handle use cases requiring large message sizes, such as processing Chrome Devtools Protocol messages.
 

src/content/docs/browser-rendering/examples.mdx

@@ -7,81 +7,81 @@ sidebar:
 
 import { CardGrid, LinkCard } from "~/components"
 
-## REST API examples
+## Quick Actions examples
 
-Use these [REST API](/browser-rendering/rest-api/) examples to perform quick, common tasks.
+Use these [Quick Actions](/browser-rendering/quick-actions/) examples to perform common tasks with a single HTTP request.
 
 <CardGrid>
     <LinkCard
         title="Fetch rendered HTML from a URL"
         description="Capture fully rendered HTML from a webpage after JavaScript execution."
-        href="/browser-rendering/rest-api/content-endpoint/#fetch-rendered-html-from-a-url"
+        href="/browser-rendering/quick-actions/content-endpoint/#fetch-rendered-html-from-a-url"
     />
     <LinkCard
         title="Take a screenshot of the visible viewport"
         description="Capture a screenshot of a fully rendered webpage from a URL or custom HTML."
-        href="/browser-rendering/rest-api/screenshot-endpoint/#basic-usage"
+        href="/browser-rendering/quick-actions/screenshot-endpoint/#basic-usage"
     />
     <LinkCard
         title="Take a screenshot of the full page"
         description="Capture a screenshot of an entire scrollable webpage, not just the visible viewport."
-        href="/browser-rendering/rest-api/screenshot-endpoint/#navigate-and-capture-a-full-page-screenshot"
+        href="/browser-rendering/quick-actions/screenshot-endpoint/#navigate-and-capture-a-full-page-screenshot"
     />
     <LinkCard
         title="Take a screenshot of an authenticated page"
         description="Capture a screenshot of a webpage that requires login using cookies, HTTP Basic Auth, or custom headers."
-        href="/browser-rendering/rest-api/screenshot-endpoint/#capture-a-screenshot-of-an-authenticated-page"
+        href="/browser-rendering/quick-actions/screenshot-endpoint/#capture-a-screenshot-of-an-authenticated-page"
     />
     <LinkCard
         title="Generate a PDF"
         description="Generate a PDF from a URL or custom HTML and CSS."
-        href="/browser-rendering/rest-api/pdf-endpoint/#basic-usage"
+        href="/browser-rendering/quick-actions/pdf-endpoint/#basic-usage"
     />
     <LinkCard
         title="Extract Markdown from a URL"
         description="Convert a webpage's content into Markdown format."
-        href="/browser-rendering/rest-api/markdown-endpoint/#convert-a-url-to-markdown"
+        href="/browser-rendering/quick-actions/markdown-endpoint/#convert-a-url-to-markdown"
     />
     <LinkCard
         title="Capture a snapshot from a URL"
         description="Capture both the rendered HTML and a screenshot from a webpage in a single request."
-        href="/browser-rendering/rest-api/snapshot/#capture-a-snapshot-from-a-url"
+        href="/browser-rendering/quick-actions/snapshot/#capture-a-snapshot-from-a-url"
     />
     <LinkCard
         title="Scrape headings and links from a URL"
         description="Extract structured data from specific elements on a webpage using CSS selectors."
-        href="/browser-rendering/rest-api/scrape-endpoint/#extract-headings-and-links-from-a-url"
+        href="/browser-rendering/quick-actions/scrape-endpoint/#extract-headings-and-links-from-a-url"
     />
     <LinkCard
         title="Capture structured data with an AI prompt and JSON schema"
         description="Extract structured data from a webpage using AI using a prompt or JSON schema."
-        href="/browser-rendering/rest-api/json-endpoint/#with-a-prompt-and-json-schema"
+        href="/browser-rendering/quick-actions/json-endpoint/#with-a-prompt-and-json-schema"
     />
     <LinkCard
         title="Retrieve links from a URL"
         description="Retrieve all links from a webpage, including hidden ones."
-        href="/browser-rendering/rest-api/links-endpoint/#get-all-links-on-a-page"
+        href="/browser-rendering/quick-actions/links-endpoint/#get-all-links-on-a-page"
     />
     <LinkCard
         title="Crawl a documentation site"
         description="Crawl documentation pages with include/exclude patterns to build a knowledge base."
-        href="/browser-rendering/rest-api/crawl-endpoint/#documentation-site-crawl"
+        href="/browser-rendering/quick-actions/crawl-endpoint/#documentation-site-crawl"
     />
     <LinkCard
         title="Extract structured product data with AI"
         description="Crawl a product catalog and extract structured JSON data using AI."
-        href="/browser-rendering/rest-api/crawl-endpoint/#product-catalog-extraction-with-ai"
+        href="/browser-rendering/quick-actions/crawl-endpoint/#product-catalog-extraction-with-ai"
     />
     <LinkCard
         title="Fast static content fetch"
         description="Crawl static sites without JavaScript rendering for faster results."
-        href="/browser-rendering/rest-api/crawl-endpoint/#fast-static-content-fetch"
+        href="/browser-rendering/quick-actions/crawl-endpoint/#fast-static-content-fetch"
     />
 </CardGrid>
 
-## Workers Bindings examples
+## Browser automation examples
 
-Use [Workers Bindings](/browser-rendering/workers-bindings/) for dynamic, multi-step browser automation with [Puppeteer](/browser-rendering/puppeteer/), [Playwright](/browser-rendering/playwright/), or [Stagehand](/browser-rendering/stagehand/).
+Use [Puppeteer](/browser-rendering/puppeteer/), [Playwright](/browser-rendering/playwright/), or [Stagehand](/browser-rendering/stagehand/) for dynamic, multi-step browser automation within Cloudflare Workers.
 
 <CardGrid>
     <LinkCard
@@ -107,12 +107,12 @@ Use [Workers Bindings](/browser-rendering/workers-bindings/) for dynamic, multi-
     <LinkCard
         title="Reuse browser sessions"
         description="Improve performance by reusing browser sessions across requests."
-        href="/browser-rendering/workers-bindings/reuse-sessions/"
+        href="/browser-rendering/features/reuse-sessions/"
     />
     <LinkCard
         title="Persist sessions with Durable Objects"
         description="Use Durable Objects to maintain long-running browser sessions."
-        href="/browser-rendering/workers-bindings/browser-rendering-with-do/"
+        href="/browser-rendering/how-to/browser-rendering-with-do/"
     />
     <LinkCard
         title="AI-powered browser automation with Stagehand"