PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A successful deploy means the platform built and created a deployment; it does not guarantee that the deployment is serving your public domain or that the page visitors need works. First identify whether the URL is a preview, branch or build-specific link, or production URL. Then check the production branch, domain assignment, promotion status, and exact route.
Why a successful deploy can land at an unexpected URL
Hosting platforms can give a deployment several URLs, each with a different purpose. A preview URL is for review; a branch URL can follow deployments from a particular branch; a commit-specific or deploy permalink identifies one build; and a production URL is the address intended for ordinary visitors. The first URL shown after deployment is not necessarily your site’s public address.
For example, Vercel generates URLs for branch and commit deployments, while Netlify distinguishes Deploy Previews, branch deploys, deploy permalinks, and the production URL. The precise labels and behavior vary by platform. Vercel’s generated URL documentation and Netlify’s Deploy Previews documentation describe their respective conventions.
A surprising Vercel-generated hostname alone does not prove the deployment went to the wrong project: Vercel may shorten generated names to fit DNS-label limits or to reduce phishing risk when a project name resembles a domain. Check the deployment details and project before drawing that conclusion.
Identify which URL you have
- Copy the exact URL shown in the command output or deployment dashboard. Open that deployment’s details rather than relying on a notification or a remembered link.
- Look for its environment or type. Determine whether the dashboard calls it a preview, branch deployment, deploy permalink, or production deployment. A build-specific URL is useful for checking one version, but it may not be the address assigned to the public site.
- Note the branch and commit. Confirm what code was deployed and compare that branch with the project’s configured production branch.
- Find the production domain separately. In the project’s domain or site settings, identify the address visitors are meant to use and which deployment or branch currently serves it.
Netlify’s deploy overview explains the difference between changing preview or production URLs and an immutable deploy permalink: the permalink continues to identify that deploy, while preview and production URLs can point to newer deploys. Choose based on whether someone needs the current site or one specific build. See Netlify’s deploy overview.
Check whether the deployment is production-ready for your domain
A platform’s “Success” or “Ready” status is about the deployment process, not proof that the intended public URL or page works. Vercel puts the distinction plainly: “A Ready status confirms the build succeeded and the deployment exists. It does not confirm that routing works.” Vercel’s 404 guidance, dated July 23, 2026, recommends comparing the generated .vercel.app URL with the custom domain to help distinguish deployment or routing problems from domain configuration or DNS issues.
Confirm the production branch
Check the branch your project treats as production, then verify that the successful deployment came from that branch. On Netlify, the production branch supplies the site’s main URL. On Vercel, pushes to the configured production branch trigger deployment to an assigned custom domain. If the Vercel domain is assigned to a different branch, that branch needs a deployment for the domain to resolve as intended. See Vercel’s domain deployment documentation.
Use the appropriate production action
Some deployment commands create previews unless you explicitly request production. For an existing Vercel project, vercel deploy creates a preview; vercel deploy --prod deploys to production. Vercel documents a first-deployment exception: the initial deployment of a new project is production even without --prod. Check the command and project context before running it again. Vercel’s CLI deployment guide describes this flow.
If you need to make an existing preview the production deployment, Vercel supports promotion. Consider the environment-variable difference first: promoting a preview causes a complete rebuild and uses production rather than preview environment variables. A deployment that behaved correctly in preview could therefore behave differently after promotion. Vercel also documents instant rollback, which reassigns domains to an existing deployment without a complete rebuild. These are separate actions with different effects; choose based on whether you need to publish the preview or restore a prior deployment. Details are in Vercel’s deployment promotion documentation.
Compare the generated URL with the public domain
Open both addresses, including the exact page path that visitors need—not just the homepage. This comparison is a useful triage step, particularly on Vercel, but it is not a universal diagnosis for every hosting platform.
| What you observe | Where to investigate next |
|---|---|
| The generated platform URL works, but the custom domain does not. | Check that the domain is assigned to the intended project and deployment or branch. Then inspect DNS and redirects. Vercel’s domain documentation covers assignment and branch behavior. |
| Neither URL works, or the homepage works but the requested path returns 404. | Inspect the deployment logs and build output, then check the framework preset, output directory, routing metadata, and route configuration. Vercel lists these as possible causes of 404s; other platforms may have different controls. |
| The production URL works, but a preview is missing or unavailable. | Check whether that preview deploy is complete. On Netlify, the initial Deploy Preview may not be available while its deploy is pending. |
For the distinction between domain assignment and deployment configuration, consult Vercel’s domain guide. For Vercel-specific 404 checks, see its troubleshooting guide.
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 errorsChoose the right link for the people who need it
- Public visitors: Share the production domain, once you have confirmed it serves the intended deployment and route.
- Reviewers: Share a preview or branch URL so they can inspect work without treating it as the public site.
- Someone who must revisit one particular build: Use a commit-specific URL or deploy permalink when the platform provides one. Netlify describes its deploy permalink as immutable; its preview and production URLs can change as newer commits deploy.
Access and availability can depend on platform settings and deployment state. In particular, a pending Netlify Deploy Preview may not yet be available. Avoid presenting a review URL as the permanent public address unless that is actually how the project is configured.
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.
