Deploying Next.js to Vercel: a launch checklist
Connect the repo, scope environment variables, pick the right plan, set the domain and region, then check redirects, robots and real-user speed.
By Sohail Hussain21 November 20266 min read
To deploy a Next.js site to Vercel, import the Git repository into a Vercel project, add your environment variables for each environment, and push to the main branch; Vercel runs next build and publishes the result. For a company site that will carry real traffic, the work around that matters more: the right plan, the custom domain and its redirect, the function region, preview protection, and checks that robots.txt, the sitemap and redirects point at the production domain.
This is the checklist we run at launch for Next.js sites, current for Next.js 16 and Vercel as of October 2026.
What should be ready before the first deploy?
- A clean local production build. Run
npm run buildandnpm run startand click through the site. A build that fails locally will fail on Vercel, with a slower feedback loop. - A list of environment variables. Every key the app reads, which environments need it, and who owns the account it belongs to. Nothing secret starts with
NEXT_PUBLIC_, because those values are written into the browser JavaScript at build time. - A committed lockfile (
package-lock.json,pnpm-lock.yamlor similar), so Vercel installs the same versions you tested. - Node.js 20.9 or later, the minimum for Next.js 16. Set the version in the project settings to match your local one.
- The redirect map from the old site, if this replaces one. Put it in
next.config.tsunderredirects(). Our redirect generator turns a two-column list of old and new URLs into rules.
Launch, including domain, email, analytics and Search Console, is part of every project in our website design and development work, and this list is the core of it.
Which Vercel plan does a company site need?
| Plan | Who it is for | Cost as of October 2026 | Notes |
|---|---|---|---|
| Hobby | Personal, non-commercial projects | Free | Not permitted for business sites under Vercel's fair use terms |
| Pro | Commercial sites and teams | $20 per team member per month, plus usage beyond the included amounts | Previews, team access, higher limits |
| Enterprise | Large organisations | Quoted | Contracts, SLAs, advanced security |
Most company sites fit comfortably within Pro's included usage. The items that can grow the bill are image optimisation on image-heavy sites, function time on pages rendered per request, and bandwidth on large downloads. Check current numbers on Vercel's pricing page before you commit, and estimate your traffic with our hosting cost calculator.
Put the project in a team owned by the business, not a freelancer's personal account. Add your developer as a member. Moving a project between accounts after launch is possible but avoidable.
How should environment variables be set?
Vercel scopes each variable to Production, Preview, Development, or any combination. Use that:
- Production gets live keys: the real CMS token, the live payment keys, the production analytics ID.
- Preview gets test or staging keys, so a branch deploy can never charge a card or send email to customers.
- Development holds what developers pull locally with
vercel env pull.
A changed variable applies only to new deployments. After editing one, redeploy. This matters most for NEXT_PUBLIC_ values, which are fixed into the JavaScript when the build runs; changing them without a rebuild does nothing.
How do you connect the custom domain?
In the project's Domains settings, add both the bare domain and the www version. Choose one as primary and set the other to redirect to it. Vercel then shows the DNS records to create at your registrar or DNS provider, typically an A record for the bare domain and a CNAME for www. Use the values Vercel shows for your project rather than ones copied from an old tutorial.
Three things to do around the switch:
- Lower the DNS TTL on the existing records to a few minutes, a day before launch, so the change spreads quickly and a rollback would too.
- Leave the MX and TXT records alone. Changing the A and CNAME records does not affect email. If you move the whole domain's nameservers to Vercel instead, recreate every MX, SPF and DKIM record first, or email stops.
- Wait for the certificate. Vercel issues the HTTPS certificate automatically once DNS resolves. Do not announce the launch until the padlock shows on both the bare and
wwwaddresses.
What should be configured after the first deploy?
Function region. Server-rendered pages, Route Handlers and Server Actions run in one region, and new projects default to one in the United States. If your database or CMS and most of your visitors are in India, set the region to Mumbai (bom1); for the Gulf, pick the nearest region your database also offers. Static pages are served from Vercel's edge network everywhere regardless.
Preview protection. Every branch gets its own preview URL. Check under Deployment Protection that previews require a login, so unreleased pages and staging data are not public. Vercel also sends a noindex header on preview deployments by default; production should not have one.
Real-user speed data. Turn on Speed Insights to collect Core Web Vitals from actual visitors, and Web Analytics if you do not run another analytics tool. Lab scores at launch do not tell you how the site performs for customers on mid-range phones; field data does. Core Web Vitals explained covers what to look for.
Production-only robots and sitemap. Make sure robots.ts and sitemap.ts use the production domain, and that any "disallow everything" rule meant for staging is gone. Sitemaps and robots.txt in Next.js shows an environment-aware robots file using Vercel's VERCEL_ENV.
What should you check on launch day?
| Check | How |
|---|---|
Bare domain and www both resolve, one redirects to the other | curl -sI on each; expect one 308 or 301 and one 200 |
| HTTPS works with no warnings | Open both in a private window |
| Old URLs redirect in one hop | curl -sI on five old URLs from the redirect map |
| robots.txt allows crawling | Open /robots.txt on the production domain |
| Sitemap lists production URLs only | Open /sitemap.xml |
No noindex on production pages | View source on the homepage and a key page |
| Forms send and arrive | Submit each form with a real address |
| Search Console verified, sitemap submitted | Search Console Sitemaps report |
Then watch the first week: Vercel's runtime logs for errors, Search Console for crawl problems, and Speed Insights once enough visits come in. The wider list for any platform is our website launch checklist.
When is Vercel the wrong host?
Vercel is the least-effort way to run Next.js, and the Next.js docs list it as a verified adapter. It is not always the cheapest or the right fit.
- Very high traffic or heavy image use can cost more on usage-based pricing than a fixed-price server or a platform priced differently.
- Data residency rules may require hosting in a country or provider Vercel does not cover.
- Long-running background jobs fit better on a server or a queue service than in request-bound functions.
Next.js runs on any Node.js server or in a Docker container with every feature supported, and Netlify, Cloudflare and others offer their own integrations. Vercel vs Netlify vs Cloudflare compares the main options, and the official Next.js deployment guide lists what each method supports. For a typical company site on Next.js, which is the setup we argue for in why we build company websites with Next.js, Vercel Pro is usually the simplest answer.
Was this guide useful?