Worker Previews docs

public/__redirects

@@ -2130,6 +2130,7 @@
 /workers/tutorials/hello-world-rust/ /workers/tutorials/ 301
 /workers/tutorials/introduction-to-cloudflare-workers/ https://www.youtube.com/watch?v=H7Qe96fqg1M 301
 /workers/configuration/bindings/about-service-bindings/ /workers/runtime-apis/bindings/service-bindings/ 301
+/workers/configuration/previews/ /workers/previews/ 301
 /workers/tutorials/localize-a-website/ /pages/tutorials/localize-a-website/ 301
 /workers/tutorials/manage-projects-with-lerna/ /pages/configuration/monorepos/#monorepo-management-tools 301
 /workers/tutorials/create-sitemap-from-sanity-cms/ /resources/ 301

src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx

@@ -14,7 +14,7 @@ The Deploy to Cloudflare button:
 1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing. 
 2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment. 
 3. **Configures Workers Builds (CI/CD)**: Every new push to your production branch on your newly created repository will automatically build and deploy courtesy of [Workers Builds](/workers/ci-cd/builds/).
-4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).   
+4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).   
 
 ![Import repo or choose template](~/assets/images/workers/dtw-user-flow.png)
 

src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx

@@ -6,7 +6,7 @@ tags:
 date: 2025-08-14T01:00:00Z
 ---
 
-We've updated [preview URLs](/workers/configuration/previews/) for Cloudflare Workers to support long branch names.
+We've updated [preview URLs](/workers/previews/) for Cloudflare Workers to support long branch names.
 
 Previously, branch and Worker names exceeding the 63-character DNS limit would cause alias generation to fail, leaving pull requests without aliased preview URLs. This particularly impacted teams relying on descriptive branch naming.
 

src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx

@@ -5,7 +5,7 @@ date: 2025-09-17
 ---
 import { WranglerConfig, Aside } from "~/components";
 
-To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. 
+To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. 
 
 ## One-Time Update for Workers with workers.dev Disabled
 We performed a one-time update to disable preview URLs for existing Workers where the [workers.dev subdomain](/workers/configuration/routing/workers-dev/) was also disabled.
@@ -16,7 +16,7 @@ If your Worker was affected, its preview URL (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAI
 
 **How to Re-enable Your Preview URL**
 
-If your preview URL was disabled, you can re-enable it [via the Cloudflare dashboard](/workers/configuration/previews/#toggle-preview-urls-enable-or-disable) by navigating to your Worker's Settings page and toggling on the Preview URL.
+If your preview URL was disabled, you can re-enable it [via the Cloudflare dashboard](/workers/previews/#enable-or-disable-preview-urls) by navigating to your Worker's Settings page and toggling on the Preview URL.
 
 Alternatively, you can use Wrangler by adding the `preview_urls = true` setting to your Wrangler file and redeploying the Worker.
 

src/content/changelog/workers/2025-10-03-one-click-access-for-workers.mdx

@@ -8,7 +8,7 @@ date: 2025-10-03
 
 import { DashButton } from "~/components";
 
-You can now enable [Cloudflare Access](/cloudflare-one/access-controls/policies/) for your [`workers.dev`](/workers/configuration/routing/workers-dev/) and [Preview URLs](/workers/configuration/previews/) in a single click.
+You can now enable [Cloudflare Access](/cloudflare-one/access-controls/policies/) for your [`workers.dev`](/workers/configuration/routing/workers-dev/) and [Preview URLs](/workers/previews/) in a single click.
 
 ![Screenshot of the Enable/Disable Cloudflare Access button on the workers.dev route settings page](~/assets/images/workers/changelog/workers-access.png)