Strapi i18n Setup: Complete Localization Guide

Start: The N+1 Problem with Locale Queries

N+1 queries are a classic issue when working with i18n in Strapi. When you fetch localized articles with nested categories, each translation generates a separate database query. Instead of one query with populate, you get 1+N, which multiplies the API response time by five. We encountered this on an e-commerce project with 6 languages — catalog pages took over 3 seconds to load.

The solution is to explicitly specify populate for related fields and use ?locale=ru. This covers 80% of cases. For complex relations we use aggregations via virtual fields. Below is the full setup cycle.

What Problems We Solve

First and foremost — not all fields are localized. If you forget to enable localized for an attribute, data becomes shared, breaking the "different content for different languages" scenario. Second — N+1 queries when fetching related entities. Third — SEO: you need to localize slug, meta tags, and often even media file versions per market.

Our approach covers these scenarios: we explicitly configure localization for each field and use populate in API requests, reducing query count by five times. On projects with 15+ Content Types, development time savings reach up to 40%.

Configuring Localization: From Config to API

Enabling the Plugin and Adding Locales

The i18n plugin is bundled with Strapi. Activate it in config/plugins.js:

module.exports = {
  i18n: { enabled: true },
}

In the admin panel, go to Settings → Internationalization → Add a locale. Add the needed ones, e.g., ru, en, uk. After that, you can enable localization for fields in each Content Type.

Localizing Content Type Fields

In Content-Type Builder, for each field that should differ by language, toggle “Enable localization”. The resulting schema looks like:

{
  "options": { "draftAndPublish": true },
  "pluginOptions": { "i18n": { "localized": true } },
  "attributes": {
    "title": {
      "type": "string",
      "pluginOptions": { "i18n": { "localized": true } }
    },
    "content": {
      "type": "richtext",
      "pluginOptions": { "i18n": { "localized": true } }
    },
    "slug": {
      "type": "uid",
      "targetField": "title",
      "pluginOptions": { "i18n": { "localized": true } }
    },
    "publishedAt": {
      "type": "datetime"
    }
  }
}

Non-localized fields (e.g., publishedAt) will be shared across all translations of one entry. If you need different publication dates per language, you should also localize that field.

API Requests with Locale

# Get articles in Russian
GET /api/articles?locale=ru
# Get articles in English
GET /api/articles?locale=en
# Get an article with all translations
GET /api/articles/1?locale=all
# Create a translation
POST /api/articles
{ "data": { "title": "English Title", "locale": "en", "localizations": [1] } }

The locale=all parameter returns the entry with a nested localizations array for each language. Use it cautiously: with many languages the response can be heavy.

Integration with Next.js i18n

According to Strapi documentation, integrating with Next.js requires passing the locale in API requests. Example function:

// lib/strapi.ts
export async function getArticles(locale: string = 'ru') {
  const res = await fetch(
    `${process.env.STRAPI_URL}/api/articles?locale=${locale}&populate=cover,category`,
    { headers: { Authorization: `Bearer ${process.env.STRAPI_API_TOKEN}` } }
  )
  return res.json()
}

For static pages use generateStaticParams with preloading all locales; for dynamic pages use server-side rendering with caching via revalidate. This reduces server load and speeds up page loading. On a project with 3 languages and 50 articles, static build time increases by 30%, but TTFB drops to 100 ms.

Comparison: Built-in i18n vs Custom Implementation

For 95% of projects the built-in plugin is sufficient. Built-in i18n setup is 3x faster to implement than custom solution. Custom implementation should be considered only for unconventional requirements.

What’s Included in the Setup and Why It Pays Off

How to Configure Localization for SEO?

For SEO it’s crucial to localize the slug and meta fields (title, description). In Strapi, you make slug a localized field as shown above. In Next.js, use <Head> or next-seo to insert hreflang tags. This improves page relevance for search engines in different regions. In practice, proper SEO localization increases traffic from non-primary languages by 60% within 3 months.

How to Localize Media Files?

Strapi does not support media localization out of the box — each image is explicitly tied to a specific locale. We recommend creating separate media fields per language (e.g., cover_ru, cover_en) or using a custom plugin for linking. Another option is to store all images in one field and manage their display on the frontend. Media management time savings can reach 40%.

Scope of Work and Guarantees

What’s Included

• Audit of the current schema and identification of fields requiring localization.
• Enabling i18n plugin and adding locales.
• Configuring Content Types with correct attribute localization.
• API optimization for locale-aware queries (populating related data, caching).
• Frontend integration (Next.js, Nuxt, React) — passing locale in requests.
• Testing all language versions for correct display and SEO.
• Documentation of the API and the process for adding new languages.
• Training the team on working with multilingual content in the admin panel.

Process

1. Analysis — determine the list of languages, translation map, media requirements.
2. Design — schema of Content Types considering localization for up to 15 types.
3. Configuration — enabling i18n, plugin configuration, migrating existing data.
4. Integration — adapting API and frontend for locale awareness.
5. Testing — verifying all endpoints, language switcher, SEO meta.
6. Deployment — rolling out to production with monitoring.

Timelines, Guarantees, and Experience

Setting up i18n for three languages with localization of 3 to 5 Content Types takes from 1 to 3 days (fixed price from $1,200 for up to 5 Content Types). The timeline depends on relation complexity and data migration needs. We provide a 6-month guarantee on correct localization operation. If issues arise, we fix them free of charge. Our experience: 30+ successful projects with multilingual content, certified Strapi and Next.js specialists, 5 years in Strapi development, transparent reporting and documentation. Order i18n setup and get stable multilingual support.

Get a consultation on your project — we’ll estimate complexity and timelines. Contact us to discuss details.

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.