Language Override is a Settings → APIs option that lets you force a specific analysis language instead of the one RankGear would otherwise select automatically for supported components.
| Term | Language Override |
|---|---|
| Category | APIs, Reliability and Publishing |
| Also known as | Analysis Language Override |
| Where it appears | Settings → APIs |
What it means in RankGear
By default, RankGear infers the language for a supported analysis component from the run’s context—the keyword, the localization settings, and what the provider returns. Language Override, found under Settings → APIs, replaces that inferred value with a language you choose. Once set, supported components stop guessing and use your explicit choice, which is useful when automatic detection lands on the wrong language or when you want every run in a project to be analyzed consistently regardless of how individual keywords read.
How to interpret it
Treat the override as a deliberate constraint rather than a setting to leave on by accident. When it is off, RankGear follows the language it detects for each run; when it is on, the language you selected applies uniformly to the components that support it. Set it when you know the intended audience language and want detection out of the loop—for example, when a market’s queries mix scripts or when short keywords give the detector too little to work with. Leave it off when you are analyzing across languages and want each run handled on its own terms.
Example
A team analyzing a Swiss campaign finds that a handful of short, brand-heavy keywords are being detected as English, which skews the text handling for those runs. Rather than fixing each run individually, they open Settings → APIs and set Language Override to German so every supported component in the project analyzes German text. Detection is now bypassed, and the mixed-signal keywords are processed the same way as the rest of the set.
Important considerations
- The override only affects components that support a language parameter; anything without one is unchanged, so it is not a project-wide language switch.
- Forcing the wrong language is as disruptive as leaving detection wrong—an override set to German applied to genuinely English pages will misread that text, so scope it to projects where you are sure of the audience language.
- Language governs how text is interpreted; it does not change which pages a provider returns for a query, and it does not make any page rank. The factor relationships RankGear reports remain correlations across the analyzed pages, not Google’s scoring and not causes.
- Because this lives under Settings → APIs alongside provider credentials and publishing targets, review it when you change providers or hand a project to another operator, so the forced language still matches the work.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.