Reorganize browser rendering navigation structure (#26162)

* Reorganize browser rendering navigation structure

* Add redirects and update links for browser-rendering navigation reorganization

* Added missing redirects and updated missing root links

* Apply suggestions from code review

---------

Co-authored-by: ToriLindsay <[email protected]>

Author: 2 people

public/__redirects

@@ -304,6 +304,15 @@
 /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/platform/ /browser-rendering/ 301
+/browser-rendering/platform/puppeteer/ /browser-rendering/puppeteer/ 301
+/browser-rendering/platform/playwright/ /browser-rendering/playwright/ 301
+/browser-rendering/platform/playwright-mcp/ /browser-rendering/playwright/playwright-mcp/ 301
+/browser-rendering/platform/wrangler/ /browser-rendering/reference/wrangler/ 301
+/browser-rendering/platform/limits/ /browser-rendering/limits/ 301
+/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
 
 # byoip
 /byoip/about/dynamic-advertisement/ /byoip/concepts/dynamic-advertisement/ 301

src/content/changelog/browser-rendering/2025-04-04-playwright-beta.mdx

@@ -8,7 +8,7 @@ date: 2025-04-04
 
 We're excited to share that you can now use Playwright's browser automation [capabilities](https://playwright.dev/docs/api/class-playwright) from Cloudflare [Workers](/workers/).
 
-[Playwright](https://playwright.dev/) is an open-source package developed by Microsoft that can do browser automation tasks; it's commonly used to write software tests, debug applications, create screenshots, and crawl pages. Like [Puppeteer](/browser-rendering/platform/puppeteer/), we [forked](https://github.com/cloudflare/playwright) Playwright and modified it to be compatible with Cloudflare Workers and [Browser Rendering](https://developers.cloudflare.com/browser-rendering/).
+[Playwright](https://playwright.dev/) is an open-source package developed by Microsoft that can do browser automation tasks; it's commonly used to write software tests, debug applications, create screenshots, and crawl pages. Like [Puppeteer](/browser-rendering/puppeteer/), we [forked](https://github.com/cloudflare/playwright) Playwright and modified it to be compatible with Cloudflare Workers and [Browser Rendering](https://developers.cloudflare.com/browser-rendering/).
 
 Below is an example of how to use Playwright with Browser Rendering to test a TODO application using assertions:
 
@@ -52,4 +52,4 @@ export default {
 
 Playwright is available as an npm package at [`@cloudflare/playwright`](https://www.npmjs.com/package/@cloudflare/playwright) and the code is at [GitHub](https://github.com/cloudflare/playwright).
 
-Learn more in our [documentation](/browser-rendering/platform/playwright/).
+Learn more in our [documentation](/browser-rendering/playwright/).

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

@@ -28,6 +28,6 @@ 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).
 
-We also recently landed support for [Playwright](/browser-rendering/platform/playwright/) in Browser Rendering for browser automation from Cloudflare [Workers](/workers/), in addition to [Puppeteer](/browser-rendering/platform/puppeteer/), giving you more flexibility to test across different browser environments.
+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.
 
 Visit the [Browser Rendering docs](/browser-rendering/) to learn more about how to use headless browsers in your applications.

src/content/changelog/browser-rendering/2025-05-28-playwright-mcp.mdx

@@ -10,7 +10,7 @@ import { PackageManagers } from "~/components";
 
 We're excited to share that you can now use the [Playwright MCP](https://github.com/cloudflare/playwright-mcp) server with Browser Rendering.
 
-Once you [deploy the server](/browser-rendering/platform/playwright-mcp/#deploying), you can use any MCP client with it to interact with Browser Rendering. This allows you to run AI models that can automate browser tasks, such as taking screenshots, filling out forms, or scraping data.
+Once you [deploy the server](/browser-rendering/playwright/playwright-mcp/#deploying), you can use any MCP client with it to interact with Browser Rendering. This allows you to run AI models that can automate browser tasks, such as taking screenshots, filling out forms, or scraping data.
 
 ![Access Analytics](~/assets/images/browser-rendering/playground-ai-screenshot.png)
 
@@ -30,4 +30,4 @@ export default PlaywrightMCP.mount("/sse");
 
 Check out the full code at [GitHub](https://github.com/cloudflare/playwright-mcp).
 
-Learn more about Playwright MCP in our [documentation](/browser-rendering/platform/playwright-mcp/).
+Learn more about Playwright MCP in our [documentation](/browser-rendering/playwright/playwright-mcp/).

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

@@ -6,8 +6,8 @@ products:
 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. 
+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.
 
 ![Local Dev video](~/assets/images/browser-rendering//localshorterbrowserrendering.gif)
 
-Get started with this [example guide](/browser-rendering/workers-bindings/screenshots/) that shows how to use Cloudflare's [fork of Puppeteer](/browser-rendering/platform/puppeteer/) (you can also use [Playwright](/browser-rendering/platform/playwright/)) to take screenshots of webpages and store the results in [Workers KV](/kv/).
+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/).

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

@@ -24,8 +24,8 @@ What you need to know:
 - **Workers Free Plan:** 10 minutes of browser usage per day with 3 concurrent browsers at no charge.
 - **Workers Paid Plan:** 10 hours of browser usage per month with 10 concurrent browsers (averaged monthly) at no charge. Additional usage is charged as shown above.
 
-You can monitor usage via the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers/browser-rendering). Go to **Compute (Workers)** > **Browser Rendering**. 
+You can monitor usage via the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers/browser-rendering). Go to **Compute (Workers)** > **Browser Rendering**.
 
 ![Browser Rendering dashboard](~/assets/images/browser-rendering/dashboard.png)
 
-If you've been using Browser Rendering and do not wish to incur charges, ensure your usage stays within your plan's [included usage](/browser-rendering/platform/pricing/). To estimate costs, take a look at these [example pricing scenarios](/browser-rendering/platform/pricing/#examples-of-workers-paid-pricing). 
+If you've been using Browser Rendering and do not wish to incur charges, ensure your usage stays within your plan's [included usage](/browser-rendering/pricing/). To estimate costs, take a look at these [example pricing scenarios](/browser-rendering/pricing/#examples-of-workers-paid-pricing).

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

@@ -8,10 +8,10 @@ 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/platform/stagehand/) so you can combine code with natural language instructions to build more resilient automations.
-- Finally, we’ve tripled [limits](/browser-rendering/platform/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.
+- 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.
 
-To get started with Stagehand, refer to the [Stagehand](/browser-rendering/platform/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.
+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.
 
 ```ts title="Stagehand example"
 const stagehand = new Stagehand({

src/content/docs/ai-search/configuration/data-source/website.mdx

@@ -51,7 +51,7 @@ If you have Security rules configured to block bot activity, you can add a rule
 You can choose how pages are parsed during crawling:
 
 - **Static sites**: Downloads the raw HTML for each page.
-- **Rendered sites**: Loads pages with a headless browser and downloads the fully rendered version, including dynamic JavaScript content. Note that the [Browser Rendering](/browser-rendering/platform/pricing/) limits and billing apply.
+- **Rendered sites**: Loads pages with a headless browser and downloads the fully rendered version, including dynamic JavaScript content. Note that the [Browser Rendering](/browser-rendering/pricing/) limits and billing apply.
 
 ## Storage
 During setup, AI Search creates a dedicated R2 bucket in your account to store the pages that have been crawled and downloaded as HTML files. This bucket is automatically managed and is used only for content discovered by the crawler. Any files or objects that you add directly to this bucket will not be indexed.

src/content/docs/ai-search/platform/limits-pricing.mdx

@@ -15,7 +15,7 @@ During the open beta, AI Search is **free to enable**. When you create an AI Sea
 | [**Vectorize**](/vectorize/platform/pricing/)    | Stores vector embeddings and powers semantic search                                       |
 | [**Workers AI**](/workers-ai/platform/pricing/)  | Handles image-to-Markdown conversion, embedding, query rewriting, and response generation |
 | [**AI Gateway**](/ai-gateway/reference/pricing/) | Monitors and controls model usage                                                         |
-| [**Browser Rendering**](/browser-rendering/platform/pricing/)     | Loads dynamic JavaScript content during [website](/ai-search/configuration/data-source/website/) crawling with the Render option                            |
+| [**Browser Rendering**](/browser-rendering/pricing/)     | Loads dynamic JavaScript content during [website](/ai-search/configuration/data-source/website/) crawling with the Render option                            |
 
 For more information about how each resource is used within AI Search, reference [How AI Search works](/ai-search/concepts/how-ai-search-works/).
 

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

@@ -4,7 +4,7 @@ title: Changelog
 release_notes_file_name:
   - browser-rendering
 sidebar:
-  order: 9
+  order: 14
 head: []
 description: Review recent changes to Worker Browser Rendering.
 ---