Preview URLs

Understand how preview URLs work and how to share them with clients.

Every time you push to your worker branch, Vercel creates a new preview deployment with a unique URL. These previews let you test your changes in a production-like environment before they go live.

Vercel generates several URL formats for each project:

FormatExampleUpdates When
Deployment URLmy-app-abc123.vercel.appNever (permanent per deployment)
Branch URLmy-app-git-worker-fox.vercel.appEvery push to that branch
Production URLmy-app.vercel.appPush to main branch
Use Branch URLs for Sharing

When sharing with clients, use the branch URL. It always points to your latest deployment, so clients automatically see your most recent changes without needing a new link.

You can find your preview URLs in several places:

  1. Worker Dashboard

    The project details page shows the latest preview URL for your branch.

  2. GitHub Deployment Status

    GitHub shows deployment status on commits and pull requests with links to the preview.

  3. Vercel Dashboard

    The Vercel project page lists all deployments with their URLs.

  4. Vercel CLI

    Run vercel ls to list recent deployments.

Some Olive Code projects have password-protected previews to keep client work private. If a project has password protection enabled:

  • Visitors must enter a password before viewing the preview
  • The password is set in the project configuration
  • The password is displayed in the Worker Dashboard project details
  • Clients receive the password automatically when previews are shared
Vercel Authentication

Password protection is handled at the Vercel level. You don't need to implement anything in your code – it works automatically for all preview URLs.

  • Test before sharing – Always test your preview URL before sharing it with clients.
  • Share branch URLs – Use branch URLs so clients always see the latest version.
  • Check console errors – Open DevTools and check for errors before sharing.
  • Test on mobile – Many clients will view previews on their phones.
  • Include context – When sharing, note what's implemented and what's still in progress.