What does a Contentful integration do on a marketing site?
A Contentful integration makes Contentful the source of truth for your site's content and lets the website fetch it through Contentful's APIs. Editors write in Contentful's web app, and the site turns those entries into pages. Because content is stored as structured entries rather than page HTML, the same entries can also feed a product, an app or a help center.
- Content types: pages, posts, case studies, authors, FAQs and SEO settings defined as typed entries with validated fields.
- Delivery and Preview APIs: published content for the live site, draft content for preview, through REST or GraphQL.
- Environments: separate copies of a space so model changes can be tested before they reach production.
- Rich text: stored as structured JSON, so it renders through your own design components.
- Assets: images and files served from Contentful's CDN, with resizing and format options in the URL.
- Webhooks and apps: publish events that trigger site updates, and an app framework for custom editor tools.
Contentful is common at companies where marketing, product and docs share content, or where a larger editorial team needs roles and workflows. If the idea of a headless CMS is new to you, our headless CMS explainer for non-developers covers the basics, and best headless CMS for marketing teams puts Contentful next to the alternatives.
How does Contentful work with Next.js, Framer and Webflow?
Contentful fits a coded Next.js site best, and it's rarely the right choice for a Framer or Webflow site. Both visual builders have their own CMS inside the editor, so using Contentful with them means copying entries into that native CMS, with content living in two places.
Next.js | Framer | Webflow | |
|---|---|---|---|
How Contentful connects | Queried directly at build time or on request | Synced into Framer's CMS by a marketplace sync plugin, where one is available | Synced into Webflow's CMS through its API or an automation tool |
Draft preview | Yes, with Draft Mode and the Preview API | No, editors check the page in Framer after a sync | No, editors check the page in Webflow after a sync |
Live preview in Contentful | Yes, with Contentful's Live Preview SDK | Not available | Not available |
Content in one place | Yes | No, two systems | No, two systems |
Our recommendation | Strong fit | Use Framer's CMS unless content must stay in Contentful | Use Webflow's CMS unless content must stay in Contentful |
The exception is a company whose product or docs already run on Contentful and wants a Framer or Webflow marketing site to show some of that content. A sync plugin from Framer's marketplace can copy Contentful entries into Framer collections, but listings come and go, so check that a current plugin supports what you need before you rely on it. For a broader view of this trade-off, read keeping Framer design and moving content to a headless CMS and when the Webflow CMS isn't enough.
How do we set up Contentful with Next.js?
We set up Contentful as part of the website build, starting from what your editors change most and ending with a handover they can run without us.
Audit the content
We list every page type, repeated block and setting your team edits, and what is shared with other channels.
Model the content types
Content types and fields are named around content (use case, customer story, author), with validation and help text, not around one design.
Set up environments and roles
A production environment plus a sandbox for model changes, and roles so editors can't change the model by accident.
Build the front end
Next.js pages fetch entries with typed queries, and rich text renders through the same components as the rest of the design.
Wire preview and publishing
Draft Mode and the Preview API show unpublished changes, and a publish webhook revalidates the right pages so updates appear without a full rebuild.
Train and hand over
A walkthrough with your editors plus short written notes on adding pages, posts and images.
Our guides to live preview in headless CMS setups and roles and permissions in a CMS go deeper on the two steps teams skip most often.
Is Contentful the right CMS for your site?
Contentful is a good choice when content is shared across channels, several teams edit it, and you want a hosted platform with mature governance. It's often more than a startup marketing site needs, and its plan limits and pricing are worth reading before you commit.
Pros
- Hosted, so there's no CMS server or database for your team to run
- Environments let you test model changes before they reach production
- Roles, workflows and an app framework that suit larger editorial teams
- One content source for the website, product and other channels
Cons
- Plans set limits on content types, locales and users, so check the current plan page
- The editing app is form-based; visual page building needs extra setup
- Content sits on a third-party platform rather than in your own database
- For a small site with two editors, the built-in CMS of Framer or Webflow is simpler
If you're weighing it against other options, our comparison of Contentful vs Sanity vs Payload and our breakdown of Contentful pricing set out the trade-offs. Plan details change, so confirm them on Contentful's site before you sign.
What are the common Contentful integration mistakes?
Most Contentful problems appear months after launch, when the people editing the site aren't the people who built it. These are the ones we design out from the start.
- Modeling layouts instead of content: fields like 'homepage hero subtitle 2' break at the next redesign.
- Too many content types: a new type for every section burns through plan limits and confuses editors.
- Deeply nested references: five levels of linked entries make queries slow and editing hard to follow.
- No preview: editors publish to check their work, so mistakes go live.
- Stale pages: caching without webhook revalidation, so published changes don't appear.
- Missing SEO fields: no place for titles, descriptions, social images or canonical URLs.
What does a Contentful website cost with us?
A Next.js site on Contentful is part of our website package: $8,000 fixed for up to six pages, then $500 per extra page. That covers copy, custom design, the content model, Contentful setup, the Next.js build and animation. Your Contentful subscription is billed by Contentful, separately.
Moving content into or out of Contentful is separate work. Migration is scoped on the intro call, and we include redirects and SEO checks in any migration we take on. Our guides to Contentful to Sanity and Contentful to Payload show what a move involves, and our headless CMS development page covers CMS builds more broadly. The next step is a free 30-minute call.
















