[Workers] Align Preview URL and Version URL terminology outside Previews docs

korinne · korinne · commit 6e5931436793 · 2026-04-20T11:55:15.000-07:00
diff --git a/src/content/docs/workers/ci-cd/builds/build-branches.mdx b/src/content/docs/workers/ci-cd/builds/build-branches.mdx
@@ -6,7 +6,7 @@ sidebar:
   order: 6
 ---
 
-When you connect a git repository to Workers, commits made on the production git branch will produce a Workers Build. If you want to take advantage of [preview URLs](/workers/previews/) and [pull request comments](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment), you can additionally enable "non-production branch builds" in order to trigger a build on all branches of your repository.
+When you connect a git repository to Workers, commits made on the production git branch will produce a Workers Build. If you want to take advantage of [Preview URLs](/workers/previews/) and [pull request comments](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment), you can additionally enable "non-production branch builds" in order to trigger a build on all branches of your repository.
 
 ## Change production branch
 
diff --git a/src/content/docs/workers/ci-cd/builds/configuration.mdx b/src/content/docs/workers/ci-cd/builds/configuration.mdx
@@ -51,14 +51,14 @@ Examples of other deploy commands you can set include:
 
 The non-production branch deploy command is only applicable when you have enabled [non-production branch builds](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds).
 
-It defaults to `npx wrangler versions upload`, producing a [preview URL](/workers/previews/). Like the build and deploy commands, it can be customized to instead run anything.
+It defaults to `npx wrangler preview`, producing a [Preview URL](/workers/previews/). Like the build and deploy commands, it can be customized to instead run anything.
 
 Examples of other non-production branch deploy commands you can set include:
 
-| Example Command                              | Description                                                                                                                                                                                                                                                                                           |
-| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `yarn exec wrangler versions upload`         | You can customize the package manager used to run Wrangler.                                                                                                                                                                                                                                           |
-| `npx wrangler versions upload --env staging` | If you have a [Wrangler environment](/workers/ci-cd/builds/advanced-setups/#wrangler-environments) Worker, you should set your non-production branch deploy command with the environment flag. For more details, see [Advanced Setups](/workers/ci-cd/builds/advanced-setups/#wrangler-environments). |
+| Example Command                      | Description                                                                                                                                                                                                                                                                                           |
+| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `yarn exec wrangler preview`         | You can customize the package manager used to run Wrangler.                                                                                                                                                                                                                                           |
+| `npx wrangler preview --env staging` | If you have a [Wrangler environment](/workers/ci-cd/builds/advanced-setups/#wrangler-environments) Worker, you should set your non-production branch deploy command with the environment flag. For more details, see [Advanced Setups](/workers/ci-cd/builds/advanced-setups/#wrangler-environments). |
 
 ### API token
 
diff --git a/src/content/docs/workers/ci-cd/builds/git-integration/github-integration.mdx b/src/content/docs/workers/ci-cd/builds/git-integration/github-integration.mdx
@@ -18,7 +18,7 @@ If a commit is on a pull request, Cloudflare will automatically post a comment o
 
 ![GitHub pull request comment](~/assets/images/workers/platform/ci-cd/github-pull-request-comment.png)
 
-A [preview URL](/workers/previews/) will be provided for any builds which perform `wrangler versions upload`. This is particularly useful when reviewing your pull request, as it allows you to compare the code changes alongside an updated version of your Worker.
+A [Preview URL](/workers/previews/) will be provided for any builds which perform `wrangler preview`. This is particularly useful when reviewing your pull request, as it allows you to compare the code changes against an isolated copy of your Worker.
 
 Comment history reveals any builds completed earlier while the PR was open.
 
diff --git a/src/content/docs/workers/ci-cd/builds/git-integration/gitlab-integration.mdx b/src/content/docs/workers/ci-cd/builds/git-integration/gitlab-integration.mdx
@@ -18,7 +18,7 @@ If a commit is on a merge request, Cloudflare will automatically post a comment
 
 ![GitLab merge request comment](~/assets/images/workers/platform/ci-cd/gitlab-pull-request-comment.png)
 
-A [preview URL](/workers/previews/) will be provided for any builds which perform `wrangler versions upload`. This is particularly useful when reviewing your pull request, as it allows you to compare the code changes alongside an updated version of your Worker.
+A [Preview URL](/workers/previews/) will be provided for any builds which perform `wrangler preview`. This is particularly useful when reviewing your pull request, as it allows you to compare the code changes against an isolated copy of your Worker.
 
 :::note[Enabling GitLab Merge Request events for existing connections]
 New GitLab connections are automatically configured to receive merge request events, which enable commenting functionality. For existing connections, you'll need to manually enable `Merge request events` in the Webhooks tab of your project's settings. You can follow GitLab's documentation for guidance on [managing webhooks](https://docs.gitlab.com/user/project/integrations/webhooks/#manage-webhooks).
diff --git a/src/content/docs/workers/ci-cd/builds/index.mdx b/src/content/docs/workers/ci-cd/builds/index.mdx
@@ -43,15 +43,18 @@ When connecting a repository to a Workers project, the Worker name in the Cloudf
 
 :::
 
-## View build and preview URL
+## View build output
 
 You can monitor a build's status and its build logs by navigating to **View build history** at the bottom of the **Deployments** tab of your Worker.
 
-If the build is successful, you can view the build details by selecting **View build** in the associated new [version](/workers/configuration/versions-and-deployments/) created under Version History. There you will also find the [preview URL](/workers/previews/) generated by the version under Version ID.
+A successful build produces different output depending on the branch:
 
-:::note[Builds, versions, deployments]
+- **Production branch builds** create a new [version](/workers/configuration/versions-and-deployments/) under Version History. You can view the build details by selecting **View build** on that version, along with its Version URL.
+- **Non-production branch builds** create a new [Preview](/workers/previews/) or deployment under an existing Preview. The [Preview URL](/workers/previews/) is posted as a comment on the associated pull request and can also be found in the **Previews** section of your Worker.
 
-If a build succeeds, it is uploaded as a version. If the build is configured to deploy (for example, with `wrangler deploy` set as the deploy command), the uploaded version will be automatically promoted to the Active Deployment.
+:::note[Builds, versions, deployments, Previews]
+
+A build on your production branch uploads a new version. If the build is configured to deploy (for example, with `wrangler deploy` set as the deploy command), that version is automatically promoted to the Active Deployment. A build on a non-production branch creates a Preview instead — Previews do not produce versions or active deployments.
 
 :::
 
diff --git a/src/content/docs/workers/configuration/routing/workers-dev.mdx b/src/content/docs/workers/configuration/routing/workers-dev.mdx
@@ -23,7 +23,7 @@ All Workers are assigned a `workers.dev` route when they are created or renamed
 
 ## Manage access to `workers.dev`
 
-When enabled, your `workers.dev` URL is available publicly. You can use [Cloudflare Access](/cloudflare-one/access-controls/policies/) to require visitors to authenticate before accessing preview URLs. You can limit access to yourself, your teammates, your organization, or anyone else you specify in your [access policy](/cloudflare-one/access-controls/policies/).
+When enabled, your `workers.dev` URL is available publicly. You can use [Cloudflare Access](/cloudflare-one/access-controls/policies/) to require visitors to authenticate before accessing [Preview URLs](/workers/previews/) and Version URLs. You can limit access to yourself, your teammates, your organization, or anyone else you specify in your [access policy](/cloudflare-one/access-controls/policies/).
 
 To limit your `workers.dev` URL to authorized emails only:
 
@@ -66,7 +66,7 @@ To disable the `workers.dev` route for a Worker, include the following in your W
 
 </WranglerConfig>
 
-When you redeploy your Worker with this change, the `workers.dev` route will be disabled. Disabling your `workers.dev` route does not disable Preview URLs. Learn how to [disable Preview URLs](/workers/previews/#enable-or-disable-preview-urls).
+When you redeploy your Worker with this change, the `workers.dev` route will be disabled. Disabling your `workers.dev` route does not disable [Preview URLs](/workers/previews/) or Version URLs.
 
 If you do not specify `workers_dev = false` but add a [`routes` component](/workers/wrangler/configuration/#routes) to your [Wrangler configuration file](/workers/wrangler/configuration/), the value of `workers_dev` will be inferred as `false` on the next deploy.
 
diff --git a/src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx b/src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx
@@ -321,7 +321,7 @@ Pages automatically creates a preview environment for each project, and can be i
 
 To get a similar experience in Workers, you must:
 
-1. Ensure [preview URLs](/workers/previews/) are enabled (they are on by default).
+1. Ensure [Preview URLs](/workers/previews/) are enabled (they are on by default).
 
    <WranglerConfig>
 
@@ -341,7 +341,7 @@ To get a similar experience in Workers, you must:
 
 1. [Enable non-production branch builds](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) in Workers Builds.
 
-Optionally, you can also [protect these preview URLs with Cloudflare Access](/workers/previews/#manage-access-to-preview-urls).
+Optionally, you can also [protect these Preview URLs with Cloudflare Access](/workers/previews/).
 
 :::note
 
diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx
@@ -171,7 +171,7 @@ The `main` key is optional for assets-only Workers.
   - Enables use of `*.workers.dev` subdomain to deploy your Worker. If you have a Worker that is only for `scheduled` events, you can set this to `false`. Defaults to `true`. Refer to [types of routes](#types-of-routes).
 
 - `preview_urls` <Type text="boolean" /> <MetaInfo text="optional" />
-  - Enables use of Preview URLs to test your Worker. Defaults to value of `workers_dev`. Refer to [Preview URLs](/workers/previews/).
+  - Enables use of [Preview URLs](/workers/previews/) and Version URLs to test your Worker. Defaults to value of `workers_dev`.
 
 - `route` <Type text="Route" /> <MetaInfo text="optional" />
   - A route that your Worker should be deployed to. Only one of `routes` or `route` is required. Refer to [types of routes](#types-of-routes).
