Vercel CMS options: content, previews and deployment

Choose a CMS for a Vercel-hosted retail site, separating the editor and content API from previews, builds and the public deployment.

A Vercel CMS setup pairs a content management system (CMS), such as Sanity or Contentful, with a site deployed on Vercel. Choose the CMS for the people editing your content and the workflow that gets an approved change onto your public domain. Vercel handles the deployment role.

For a retail team, the deciding test is whether an editor can review an unpublished product guide, approve it and confirm the right version reaches customers. A preview that looks correct is only one part of that process.

Assign the CMS and hosting roles

Give the CMS ownership of authored content, and give your commerce system ownership of transactions. The website combines those sources into the pages customers see.

The CMS’s editor is where staff write and approve content. Its application programming interface (API) supplies that content to the website. A headless CMS separates those editing and delivery functions from the site’s presentation.

Vercel’s framework documentation covers deployment support for frameworks including Next.js and Astro. Your framework decides how the site fetches content and renders pages. Hosting support alone does not establish how a particular CMS preview or cache refresh works.

ResponsibilityIntended ownerRetail example
Authored contentCMS and editorial teamA buying guide or delivery-policy explanation
Content retrievalCMS API and website integrationFetch the published guide in the intended language
Page renderingWebsite frameworkTurn the guide into a product-category page
Build and deliveryVercel projectBuild the site and serve its public domain
Price and saleable stockCommerce or inventory systemDecide whether the selected size can be bought
Orders and paymentsCommerce and payment systemsRecord the purchase and its payment status

Use stable product identifiers when the CMS references a product. Avoid giving an editor a second price field that can drift from checkout. If an editorial promotion states a purchase condition, assign someone to keep it consistent with the commerce rule.

Define who can edit content, who can publish it and who can change deployment settings. A retailer’s content editor often needs a preview without needing the credentials that manage hosting or payments.

Compare the actual CMS connection

Compare the CMS integration for your actual framework and rendering mode. A connector’s presence in a marketplace does not establish an approval workflow or automatic publication.

Sanity and Contentful both document content preview with Next.js. Their documented routes differ, so ask your technical team to identify which route your site will use before choosing by editor appearance alone.

Sanity with Next.js or Astro

Sanity’s Next.js App Router guide connects its Studio editing interface to draft previews and visual editing. The guide’s Live Content API setup can refresh published pages without a full deployment. Its alternative fetch setup separates draft and published content and controls revalidation explicitly.

Sanity also has an Astro integration, with guidance for static rendering and server rendering. Choose the rendering path before assuming that a preview feature from the Next.js guide applies unchanged to Astro.

Sanity is worth assessing when your developers want to configure the editing interface alongside the content model. Have an editor use the actual product-guide fields, then check that the preview reaches the intended draft. Include developer ownership of the Studio configuration in the operating plan.

Contentful with Next.js

Contentful’s Vercel integration documentation includes its Next.js preview toolkit. Its Draft Mode fetch guide requires the integration to select preview content with the correct access token. Preview fetching also needs its own caching behaviour.

Contentful’s Content Delivery API supplies published content. Its Content Preview API supplies drafts as well as published entries. That separation gives the technical team explicit sources for the public website and editorial review.

Assess Contentful when your editors want to manage structured entries with a documented Next.js preview route. Include the work to model product references and render those entries in your frontend. Installing an integration does not write the retailer’s page templates.

Choose how an approved change reaches customers

A CMS publication event must reach the website’s chosen rendering path. Select one path for each affected page and record what happens when it fails.

Publication pathHow the change reaches the pageWhat the team must verify
Static buildA CMS webhook triggers a Vercel Deploy Hook and the build fetches published contentThe correct branch builds successfully and its output reaches the production domain
Cached server pageA publication event reaches an authenticated refresh handlerThe affected page and any other cached uses of the record refresh
Sanity live contentThe configured live integration reacts to publicationThe public page receives published content while draft access stays restricted
Request-time retrievalThe page reads content when serving a requestThe published source, response cache and API failure behaviour match the store’s needs

A webhook is an event notification sent from one system to another. Vercel Deploy Hooks trigger a new deployment and rerun the build for a configured project and branch. The hook URL must stay private because possession of it allows deployment triggering.

For a Next.js App Router site using a refresh handler, revalidatePath marks a path for revalidation on its next visit. A successful webhook response alone does not prove a customer has received the updated page. Other pages using the same content can require their own invalidation.

Separate draft access from deployment access

A Vercel preview deployment is a website deployment in the Preview environment. Vercel’s environment documentation distinguishes it from Production and gives Preview its own environment variables.

A CMS draft preview is a content-reading mode. A preview deployment can still read only published content if that is how its queries are configured. Conversely, draft-reading code needs protection even when it runs on a production deployment.

Next.js Draft Mode provides a route for enabling draft rendering after a validated request. Keep draft API credentials on the server. Validate the preview request and its destination before enabling access.

Use Vercel Deployment Protection for the intended preview URLs. Its Standard Protection scope protects deployments except production domains. Test an unauthorised visitor’s access separately from an editor’s access. A hidden link or a search-indexing instruction does not enforce permission.

Include editorial access and operating cost

Price the complete arrangement for your team. The CMS subscription and Vercel charges are separate, and the chosen rendering path changes which usage grows.

Compare the editor and publisher roles available under the proposed CMS plan. Include content environments and any language requirements. Check the allowances for API requests and media delivery against the catalogue’s images and traffic.

Use the providers’ own plan pages for Sanity, Contentful and Vercel. Match the proposed plan to your commercial use and access requirements. Include ongoing developer work for schema changes and failed publication events alongside hosting costs.

For a rarely changed buying guide, a static rebuild can be straightforward to operate. Frequent content changes can make a supported live or revalidation path more useful. Keep fast-changing stock and purchase decisions with the commerce system in either arrangement.

Verify a production content change

Follow one approved content record from the CMS to the public page, including the build or cache step between them. Use the production domain as the acceptance destination, with an authorised publication.

Consider this fictional record. A retailer’s delivery-policy entry says dispatch takes two business days. An approved revision changes that to three business days, with a link from the product page to the policy. The acceptance check must find the revised wording on both pages wherever they display it.

For a Contentful-backed static site on Vercel, the intended path is an editorial draft, a protected preview, CMS publication and a production build. Contentful’s Vercel deployment example documents a publication webhook triggering a redeployment.

  1. Record the entry identifier, language and approved revision. Identify the pages that use it, including any product-page extract.
  2. Open the protected preview with the CMS’s preview source enabled. Confirm the three-business-day wording and the correct policy link.
  3. In a separate visitor session, open the public domain. Before publication, it must still show the previous published policy. Confirm that an unauthorised visitor cannot read the draft through the preview route.
  4. Publish the entry in the intended CMS environment. Confirm that the publication event reaches the Deploy Hook for the production branch.
  5. Confirm the new build fetches the published entry successfully. Check its deployment status and that the production domain points to the intended deployment.
  6. Open the public policy and product pages without draft access. Both must show the approved revision after the release. Reload them and check the served page content as well as the visible text.

For a cached Next.js site, replace the build step with the authenticated invalidation step. Visit the affected paths after the event so revalidation runs, then check their public responses. For a configured Sanity live route, confirm the publication update through that route without requiring an unrelated full build.

Diagnose where a publication stopped

Locate the first incorrect state instead of repeatedly publishing the same entry.

ObservationFirst place to inspect
CMS still shows the old published revisionApproval or publication in the intended environment
CMS is correct but no deployment or refresh startsWebhook delivery and target configuration
Build fails or retrieves the wrong entryCMS credentials, environment and content query
New deployment is correct but the public domain is oldProduction domain assignment
One public page changes while another stays oldThe other page’s content query and cache invalidation
A visitor can read an unpublished revisionDraft query selection and preview access protection

Keep the previous deployment and the previous approved content revision identifiable. Restoring website code alone can leave a live API returning the newer CMS content. Recovery must cover both owners when the content itself is wrong.

Choose the arrangement your editorial team can operate and your technical team can diagnose. Complete the decision with one successful approved revision on the public domain and a separate check that unpublished content remains restricted.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup