A successful deploy can create a preview or build-specific URL without updating the public site. To get the right result, identify what kind of deployment that URL represents, then check the production branch, domain assignment, and the exact route visitors need. A “Ready” status means the deployment exists; it does not guarantee that your domain or page works.
Why a successful deploy can land at the wrong URL
Deployment platforms can expose several URLs for one project. Depending on the platform and deployment type, the URL shown after a deploy may be for review, a branch, one specific build, or the live production site. Those URLs have different audiences and update behavior, so the first URL you see is not necessarily the one ordinary visitors should use.
As an Amazon Associate I earn from qualifying purchases.
Vercel documents URLs tied to a branch or commit, while Netlify distinguishes deploy previews, branch deploys, deploy permalinks, and the production URL. A successful build confirms that a deployment was created—not that the intended custom domain points to it or that every route works. Vercel’s Knowledge Base puts it plainly: “A Ready status confirms the build succeeded and the deployment exists. It does not confirm that routing works.” Vercel, “Why is my deployed project giving a 404?” (July 23, 2026).
First, identify what kind of URL you have
Copy the exact URL shown in the CLI output or deployment dashboard, then open that deployment’s details. Look for its type and the branch or commit it represents before sharing it or changing domain settings.
#1 Best Overall
| URL type | Best for | What to know |
|---|---|---|
| Production URL or custom domain | The public site’s ordinary visitors | It serves the production deployment selected by the platform’s configuration. Check which branch and deployment the domain is attached to. |
| Preview or branch URL | Reviewing proposed changes | It may represent a non-production branch or a preview deployment. Netlify Deploy Previews have a unique URL distinct from production; an initial preview may not be available while its deploy is pending. Netlify Deploy Previews |
| Commit-specific URL or deploy permalink | Identifying or revisiting one particular build | Vercel documents generated URLs associated with commits and branches. Netlify says a deploy permalink’s content never changes, unlike preview and production URLs, which can update as newer commits deploy. Vercel generated deployment URLs; Netlify deploy overview |
A generated URL that looks unfamiliar does not by itself prove the deployment went to the wrong project. Vercel notes that generated names can be shortened to fit DNS-label limits or to avoid names that resemble domains. Vercel’s generated URL documentation describes those cases.
Check the branch that built the deployment
Confirm the branch or commit shown in the deployment details, then compare it with the branch configured for production. If you deployed a feature branch, the platform may have correctly created a preview while leaving the public site unchanged.
Rank #2
On Vercel
Vercel uses the project’s configured production branch for production deployments. Its domain documentation says that pushes to that branch trigger deployment to the custom domain when the domain is configured. If a domain is assigned to a different branch, a deployment to that branch may be required for the domain to resolve as intended. Check the domain’s assignment and the project’s production-branch setting together. Vercel: Deploying & Redirecting Domains
On Netlify
Netlify’s production branch is the branch used for the site’s main URL. Check the site’s deploy overview to confirm which branch is serving production and whether the URL you opened belongs to a deploy preview or another deploy type. Netlify deploy overview
Make the intended deployment serve the public domain
If the deployment is only a preview, decide whether it should remain a review link or become production. The right action depends on the platform and on whether the deployment was built with production settings.
Vercel: deploy to production or promote carefully
For an existing Vercel project, the documented CLI behavior is that vercel deploy creates a preview deployment, while vercel deploy --prod deploys to production. Vercel documents an exception for a project’s first deployment: it is production even without --prod. Vercel: Deploying a project from the CLI
Vercel also supports promoting an existing preview deployment. Promotion causes a complete rebuild and uses production rather than preview environment variables. That difference matters if the preview used different credentials, API endpoints, feature flags, or other environment-specific settings. Check the deployment’s expected production configuration before promoting it. Vercel: Promoting Deployments
Free tools Windows power users keep installed
One-click scans. No signup required.
Netlify: distinguish preview from production
A Netlify Deploy Preview is intended to give a proposed change its own review URL; it is not the production URL. To update the public site, verify that the intended branch is the production branch and inspect the production deploy rather than assuming a preview link will replace it. Netlify Deploy Previews; Netlify deploy overview
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test the generated URL, custom domain, and exact page
Open both the platform-generated deployment URL and the custom domain. Test the homepage and the precise path visitors need, such as /pricing or /docs/start. On Vercel, comparing the .vercel.app URL with the custom domain is a documented way to help distinguish deployment or routing problems from domain configuration or DNS issues. This is provider-specific guidance, not a guaranteed diagnostic rule for every host. Vercel’s 404 troubleshooting guide
- Generated URL works; custom domain fails: Check that the domain is assigned to the intended project, deployment, or branch. Then inspect DNS records and redirects.
- Both URLs fail, or the page path returns a 404: Inspect the deployment logs and build output, then check framework settings, output directory, routing metadata, and route configuration. Vercel lists these as possible causes of a 404; other platforms may use different settings or terminology. Vercel’s 404 troubleshooting guide
- Homepage works but a nested route fails: Treat it as a route-specific issue rather than evidence that the whole deployment failed. Check that the route exists in the build and that the platform is configured to serve it correctly.
Choose the right link for the person who will open it
Use the production domain for general visitors, a preview URL for review, and a commit-specific URL or immutable deploy permalink when someone needs to identify one particular build. Before sharing a link, consider whether future deployments will change what it displays: Netlify says deploy permalinks keep their content, while its preview and production URLs can reflect newer commits. Vercel’s generated URLs can identify particular commits or branches. Netlify deploy overview; Vercel generated deployment URLs
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
