Localization settings
CIQRA separates which languages exist, how they appear in the address, what the shop’s own wording says, how complete the translation is, and what your filters are called. They are separate screens because they are separate decisions, and getting one right does not settle the others.
What is in this group
Section titled “What is in this group”| Destination | What it governs |
|---|---|
| Storefront languages | Which languages your storefront is available in. |
| URL structure | How a language appears in the address — the shape of /en/... versus /tr/... and what the default is. |
| UI strings | The storefront’s own wording: buttons, labels, messages. Not your product text — the shop’s furniture. |
| Translation coverage | How much of the translatable surface actually has a translation in each language. |
| Filter translations | The option names, values and tags that shoppers filter by, in each storefront language. |
Coverage is a measurement, not a setting
Section titled “Coverage is a measurement, not a setting”Translation coverage is the odd one out: it is a report. Each missing item has a Translate button that opens the translation workspace, and the screen also offers Translate the whole store with AI, which drafts translations for you to approve. The coverage figures themselves change nothing. That distinction matters when you are chasing a bug — if a page shows English text in a Turkish store, coverage tells you whether the string is missing (nothing was translated) or whether something else is picking the wrong language (it was translated and is not being used).
Those two have the same symptom and completely different fixes, which is exactly why the number is worth having.
URL structure changes are public
Section titled “URL structure changes are public”The language prefix is part of every public URL. Changing the structure changes the address of every localized page at once, which means existing links, bookmarks and search-engine entries point at the old shape. It is a legitimate change to make; it is not a small one, and it is worth making deliberately rather than while exploring the screen.
What this page does not say
Section titled “What this page does not say”- It does not say how automatic translation is billed or how good it is. Where machine translation is involved, its quality and cost are covered where that feature is described, not here.
- It does not cover product or blog translations. This group is the storefront’s own wording and its language routing; translating your catalog is a catalog question.