## TL;DR
"Locale not available" means the help center does not serve the requested language: the locale is not enabled, or the article was never translated into it. Enable the locale, decide the fallback behavior for untranslated content (show the default language or hide), and build translation into the publishing workflow so the gap does not reopen. The error is a content-operations problem, not a platform bug.

## The query

```text
zendesk guide "locale not available" missing translation error
```

## Use this when

- Help center errors on locale not available
- Articles missing in some languages
- Users land on the wrong language version
- You are managing a multilingual help center

## Not for

- Translation quality review
- Setting up machine translation
- Help-center theme customization
- SEO for multilingual content

## Steps

### 1. Confirm the locale is enabled on the help center

A locale that was never enabled cannot serve content in any state. Check the enabled language list and enable the missing one. Enabling is a prerequisite to everything else.

Expected output: locale enabled (or confirmed already enabled).

### 2. Check the article's translation state per locale

Open the article and look at each locale: translated and published, translated but draft, or never translated. Most "locale not available" errors are articles that exist in the default language only.

Expected output: per-locale translation state for the affected articles.

### 3. Set the fallback behavior deliberately

Decide: when a translation is missing, show the default-language article with a notice, or hide the article in that locale. Showing with a notice serves users better; hiding avoids confusion. Pick one and apply it consistently.

Expected output: a documented fallback policy, applied.

### 4. Build translation into the publishing workflow

Every new or updated default-language article should create a translation task. The gap reopens within weeks if translation is an afterthought. Track translation coverage like any other content metric.

Expected output: translation tasks generated on publish, coverage tracked.

### 5. Verify the locale switcher and URL routing

Test switching locales as an end user and confirm URLs resolve. Misconfigured routing can 404 or error even when translations exist. Check the default-locale redirect behavior too.

Expected output: locale switching works end to end for a test user.

## Template: the checklist

```text
Guide locale not available:
[ ] Locale enabled on the help center
[ ] Article translation state checked per locale
[ ] Fallback policy set (show default with notice, or hide)
[ ] Translation tasks created on every publish
[ ] Locale switcher and URL routing tested as end user
```

## Variant phrasings

### zendesk guide missing translation

Steps 2 and 4. Check state, fix the workflow.

### help center wrong language

Steps 3 and 5. Fallback policy plus routing.

### enable locale zendesk guide

Step 1, then step 2 to find the content gap it reveals.

## Why it happens

Multilingual help centers have two independent dimensions: which locales the platform serves, and which articles are translated into each. Teams enable a locale (dimension one) and assume content follows (dimension two). It does not; translation is per article per locale, and the error marks the articles nobody translated.

## Edge cases

- Partial translations: an article translated six months ago is stale, not missing. Track freshness, not just existence.
- User-contributed translations: community translations need review before publishing. Unreviewed drafts error the same as missing.
- Right-to-left locales: theme and layout need testing per locale, not just content.
- Default locale changes: changing the default reshuffles every fallback. Announce it and re-verify.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_H75iXVbPVqIZY25-bhV0TQ