Added missing redirects and updated missing root links

Author: ToriLindsay

public/__redirects

@@ -304,11 +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-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-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/browser-rendering/index.mdx

@@ -25,7 +25,7 @@ Run headless Chrome on [Cloudflare's global network](/workers/) for browser auto
 
 <Plan type="workers-all" />
 
-Browser Rendering enables developers to programmatically control and interact with headless browser instances running on Cloudflare’s global network. 
+Browser Rendering enables developers to programmatically control and interact with headless browser instances running on Cloudflare’s global network.
 
 ## Use Cases
 
@@ -37,15 +37,15 @@ Browser Rendering supports a wide range of use cases, including:
 - Build web scrapers that target specific elements or extract all links using the [scrape endpoint](/browser-rendering/rest-api/scrape-endpoint/) and [links endpoint](/browser-rendering/rest-api/links-endpoint/)
 - Parse and structure webpage data into JSON format using the [json endpoint](/browser-rendering/rest-api/json-endpoint/)
 
-Browser Rendering is also ideal for agentic workflows. Use [Puppeteer](/browser-rendering/platform/puppeteer/), [Playwright](/browser-rendering/platform/playwright/), [Playwright MCP](/browser-rendering/platform/playwright-mcp/), or [Stagehand](/browser-rendering/platform/stagehand/) to power AI agents that interact with web pages and extract data where APIs do not exist.
+Browser Rendering is also ideal for agentic workflows. Use [Puppeteer](/browser-rendering/puppeteer/), [Playwright](/browser-rendering/playwright/), [Playwright MCP](/browser-rendering/playwright-mcp/), or [Stagehand](/browser-rendering/stagehand/) to power AI agents that interact with web pages and extract data where APIs do not exist.
 
 ## Key features
 
 - **Scale to thousands of browsers**: Instant access to a global pool of browsers with low cold-start time, ideal for high-volume screenshot generation, data extraction, or automation at scale
 - **Global by default**: Browser sessions run on Cloudflare's edge network, opening close to your users for better speed and availability worldwide
-- **Easy to integrate**: [REST APIs](/browser-rendering/rest-api/) for common actions, while [Puppeteer](/browser-rendering/platform/puppeteer/) and [Playwright](/browser-rendering/platform/playwright/) provide familiar automation libraries for complex workflows
+- **Easy to integrate**: [REST APIs](/browser-rendering/rest-api/) for common actions, while [Puppeteer](/browser-rendering/puppeteer/) and [Playwright](/browser-rendering/playwright/) provide familiar automation libraries for complex workflows
 - **Session management**: [Reuse browser sessions](/browser-rendering/workers-bindings/reuse-sessions/) across requests to improve performance and reduce cold-start overhead
-- **Flexible pricing**: Pay only for browser time used with generous free tier ([view pricing](/browser-rendering/platform/pricing/))
+- **Flexible pricing**: Pay only for browser time used with generous free tier ([view pricing](/browser-rendering/pricing/))
 
 ## Integration Methods
 
@@ -72,7 +72,7 @@ A globally distributed coordination API with strongly consistent storage. Using
 
 <RelatedProduct header="Agents" href="/agents/" product="agents">
 
-Build AI-powered agents that autonomously navigate websites and perform tasks using [Playwright MCP](/browser-rendering/platform/playwright-mcp/) or [Stagehand](/browser-rendering/platform/stagehand/).
+Build AI-powered agents that autonomously navigate websites and perform tasks using [Playwright MCP](/browser-rendering/playwright-mcp/) or [Stagehand](/browser-rendering/stagehand/).
 
 </RelatedProduct>
 
@@ -106,7 +106,7 @@ Build AI-powered agents that autonomously navigate websites and perform tasks us
 
 <LinkTitleCard
 	title="Playwright API"
-	href="/browser-rendering/platform/playwright/"
+	href="/browser-rendering/playwright/"
 	icon="pen"
 >
 	Use Cloudflare's fork of Playwright for testing and automation.

src/content/partials/browser-rendering/example-workers-binding-screenshots-from-web.mdx

@@ -24,7 +24,7 @@ Create a new Worker project named `browser-worker` by running:
 
 #### 2. Install Puppeteer
 
-In your `browser-worker` directory, install Cloudflare’s [fork of Puppeteer](/browser-rendering/platform/puppeteer/):
+In your `browser-worker` directory, install Cloudflare’s [fork of Puppeteer](/browser-rendering/puppeteer/):
 
 <PackageManagers pkg="@cloudflare/puppeteer" dev />
 

src/content/partials/browser-rendering/manage-concurrency-faq.mdx

@@ -1,6 +1,6 @@
 ### How can I manage concurrency and session isolation with Browser Rendering?
 
-If you are hitting concurrency [limits](/browser-rendering/platform/limits/#workers-paid), or want to optimize concurrent browser usage with the [Workers Binding method](/browser-rendering/workers-bindings/), here are a few tips:
+If you are hitting concurrency [limits](/browser-rendering/limits/#workers-paid), or want to optimize concurrent browser usage with the [Workers Binding method](/browser-rendering/workers-bindings/), here are a few tips:
 
 - Optimize with tabs or shared browsers: Instead of launching a new browser for each task, consider opening multiple tabs or running multiple actions within the same browser instance.
 - [Reuse sessions](/browser-rendering/workers-bindings/reuse-sessions/): You can optimize your setup and decrease startup time by reusing sessions instead of launching a new browser every time. If you are concerned about maintaining test isolation (for example, for tests that depend on a clean environment), we recommend using [incognito browser contexts](https://pptr.dev/api/puppeteer.browser.createbrowsercontext), which isolate cookies and cache with other sessions.