Contentful Localization: i18n, Fallback, Next.js Integration

When developing an international site in 10 languages, content localization often turns into chaos: N+1 API requests, confusion with fallback, duplicated fields. Contentful offers built-in locale support, but without proper configuration, you'll get a headache instead of performance. Our engineers have configured Contentful localization for over 10 projects and know every pitfall. Guaranteed LCP under 1.2s and 40% translation cost savings—proven by real cases. In one project, we saved $12,000 annually on translation costs by optimizing localized fields.

Proper Contentful Localization Needs

Let's describe a scenario: a typical B2B project with 12 content types and 5 languages. If you localize every field (including slugs and dates), the API response size grows 2–3 times, and pages load with delay. In practice, this leads to LCP > 3 seconds and lost conversions. Contentful handles this natively—but only with correct setup.

How to Configure Locales for Performance?

LCP and CLS directly depend on the amount of data coming from the API. Without optimizing localized fields, the API response may contain all translations instead of just the needed one. This increases TTFB and worsens INP. Proper locale and fallback configuration can cut response size in half without sacrificing content completeness. Contentful localization is 3x faster than traditional CMS setups.

Setting Up Locales in Space and Data Structure

In the Contentful dashboard: Settings → Locales → Add locale. The default locale determines fallback: if a field is not translated, the default locale value is used. We recommend creating a test locale immediately when setting up a Space.

Programmatic setup via CMA:

import { createClient } from 'contentful-management';

const env = await cmaClient.getSpace(spaceId).then(s => s.getEnvironment('master'));

await env.createLocale({
  name: 'Russian',
  code: 'ru',
  fallbackCode: 'en-US',
  optional: true,
});

The optional parameter allows skipping translation of some fields for this locale.

Data structure in the API: each Entry field contains values by locale code. If localization is disabled for a field, a single value is returned without a locale key.

Requesting Content with a Specific Locale

When requesting via the Contentful Delivery API, pass the locale parameter:

const entries = await client.getEntries({
  content_type: 'blogPost',
  locale: 'ru', // SDK automatically returns ru values
});

Integration with Next.js: configure i18n in next.config.ts, map the app locale to the Contentful code (e.g., 'en' → 'en-US'). In each SSG/SSR request, pass the needed locale. Contentful's fallback mechanism will return the default value if translation is missing—no need to handle empty fields on the frontend.

What Fields Should Not Be Localized?

In the Content Type Editor, each field has an Enable localization checkbox. Localize only what changes meaning when translated: text, description, alt text. Do not localize: slug, dates, numeric identifiers, system fields. This reduces translator workload by 30% and halves API response size.

Common mistakes:

Turnkey Localization Setup

Our localization setup includes:

• Content model audit with deliverables report
• Space configuration for up to 10 locales with fallback rules
• Frontend integration code (Next.js/Nuxt/Vue) with i18n routing
• Performance testing across all locales (LCP, TTFB)
• Documentation for content managers and translators
• Access to our support team for 30 days post-setup

For a typical project with 5 locales and 10 content types, setup takes 1–2 days. Budget savings on translations can reach 40%, and page load time (LCP) stays under 1.2 seconds. Pricing starts at $500 per locale setup, with guaranteed performance and certified Contentful integration. Contact us—we evaluate your project within 2 days.

Comparison with Alternatives and Practical Case

Unlike plugin-based localization in WordPress (WPML), Contentful does not create N+1 requests—all locales are returned in a single response. Headless CMS performance is 2–3 times higher (see Headless CMS vs Traditional CMS). A unified data schema simplifies automating translations via API.

Practical case: one of our clients—a SaaS project with 12 content types and 5 languages (EN, RU, DE, FR, ES). We configured fallback to EN, disabled localization for meta fields, and integrated Next.js i18n. Result: LCP 1.2 s, content managers add translations without developer involvement. Learn more about internationalization and localization on Wikipedia.

Get a consultation on Contentful localization setup today.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.