Vercel changes not showing: check the URL, commit, and cache

Before redeploying repeatedly, identify the URL, served commit, and whether the stale part is HTML or data. A successful build does not prove that the production domain serves it.

Record the URL and commit together

In Vercel deployment management, inspect the deployment, Git commit, environment, and domain assignment. Checking a preview URL is not production verification.

Time checked:
Production URL:
Expected commit:
Assigned deployment:
A sentence that identifies the change:

Find that sentence on both production and the deployment-specific URL. If only the latter is current, inspect production assignment or promotion.

Use the observation to choose the next check

Replace example.com with your domain:

curl -i https://example.com/

Record the body marker, status, Cache-Control, and redirects. Remove cookies and authentication headers before sharing logs.

If only the browser is stale

Try a separate browser profile. For a site with a service worker, inspect whether it serves an older response. Save local work before clearing site data, which can also remove stored input and sign-in state.

If only the data is stale

Check that the upstream source returns the new value before changing application caching. Compare your Next.js version and chosen cache mechanism with the caching guide. Disabling every cache can change load and performance.

Check the rollback boundary

Rolling back a deployment does not necessarily roll back databases or external settings. Compare deployment URLs first when possible and check compatibility before restoring production.

After fixing the cause, revisit the original production URL and repeat the key operation. Preserve the URL, commit, and observed result for the next incident.