Some text is still in English

Summary#

Metric Vault ships its interface in six languages. When you switch language, the interface changes: navigation, buttons, headings, form labels, tooltips, empty states and messages. What does not change is your data and the data the tools measured, because translating a domain name, a keyword or a page title would make the result wrong. Most reports of "missing translation" are one of those two things working exactly as intended. This page tells you which is which, and what to do about the cases that genuinely are gaps.

Symptoms#

• You switched language and part of the screen is still English.
• The navigation translated but a tool result did not.
• Words such as SERP, CPC, KPI, PDF or API stayed English inside an otherwise translated sentence.
• A spinner labelled Translating… appears over a result and some of it changes in waves while other parts stay English.
• The language reverted to English on a different computer or browser.
• An email from Metric Vault arrived in English.
• The sign-in page or a legal page is in a different language from the app.

Diagnosis#

1. Confirm which language is actually selected.

The language control sits at the bottom of the tool panel in the dashboard sidebar, showing a flag and the language name. Six choices are available:

Your choice is remembered in the browser you made it in. It does not travel with your account, so a second computer, a different browser or a private window starts in English again. That is the single most common reason a customer reports "it went back to English". See Changing the language.

2. Decide which of three categories the English text belongs to.

This is the whole diagnosis. Almost every question resolves here.

Two consequences follow that surprise people:

• A tool name translates, but the acronym inside it stays English. SERP Features becomes Características SERP in Spanish, not Características de la Página de Resultados. This is intentional: the acronym is the thing practitioners search for.
• A result table can be fully translated in its headings and entirely English in its cells, because the headings are interface and the cells are data.

3. Check whether a result is still being translated.

Tool results are translated as they render, not in advance. While that happens you see a small spinner labelled Translating…, and the result changes in visible waves as each batch completes. Give it a few seconds before concluding a section did not translate.

Inside a translated sentence, domains, URLs, email addresses and numbers are lifted out before translation and put back afterwards, character for character. That is why nike.com and 1,240 survive intact in a Spanish sentence. It is protection, not a gap.

4. Rule out a stale page.

The translation dictionary is a large file that loads the first time you choose a non-English language. On a slow connection the first switch takes a moment. If a page was already open when you switched, parts of it that were rendered before the dictionary arrived can stay English until they re-render.

Resolution#

If the interface is partly English

1. Reload the page. This is the fix for a stale first load and resolves most cases.
2. Re-select the language from the sidebar control, then reload once more.
3. If a specific label is still English after a clean reload, it is a genuine coverage gap. Report it. See "If you found a real gap" below.

If a result is partly English

1. Wait for the Translating… indicator to finish.
2. Re-run the tool, or reopen the saved result, to trigger a fresh translation pass.
3. Check the English text against the three categories above. Cells, domains, keywords and provider values are data and will never change.

If the language reset itself

Select it again on that browser. To keep it consistent, use the same browser profile, and remember that clearing site data clears the choice along with everything else.

Places that behave differently on purpose

If you found a real gap

Send support the exact English text, the screen it appears on, and the language you had selected. A precise string is what makes it fixable. New features can ship a handful of strings ahead of the next translation pass, so a very new label being English is expected rather than broken. See Contacting support.

Prevention#

• Set the language once per browser you actually work in, and expect to set it again on a new device.
• Judge translation on the interface, not the data. If in doubt, ask whether a translator changing that text would make the result wrong. If yes, it is data and stays as it is.
• Reload after switching language if you had a long-running screen open.
• Do not report acronyms as bugs. SERP, CPC, API and the rest are on a deliberate keep-in-English list.
• Give the result translation time on large reports. It runs in batches and paints progressively.
• Report the exact string rather than a screenshot alone. Support can search for a string; a picture of one has to be transcribed first.