--- title: "FAQs generate in the wrong language" url: https://hostmy.blog/docs/rankready/faq-wrong-language-fix/ date: 2026-08-24 modified: 2026-08-25 lang: en author: "Aditya Sharma" description: "Get FAQ output in your site's language by controlling the inputs the generator reads, and know what to do on multilingual sites." word_count: 837 --- # FAQs generate in the wrong language This page gets FAQ output back into the language you want. The fix is about the inputs you hand the generator, so start by understanding what those inputs are. ## What you are seeing Your site is in German, Spanish, French or another non-English language. You run the FAQ Generator on a post and the questions come back in English, or in a mix of languages. Sometimes the questions are in one language and the answers in another. ## Why it happens The FAQ Generator works from what you give it, and two of those inputs carry language: - **The focus keyword you enter.** This is the string used to look up real [People Also Ask](https://hostmy.blog/docs/rankready/generate-faq-people-also-ask/) questions through DataForSEO, when that option is enabled. DataForSEO receives the focus keyword only, never your article text. An English keyword returns English questions, and those English questions then shape the output. - **The article itself.** The [AI provider](https://hostmy.blog/docs/rankready/choose-ai-provider-cost/) reads the post to write answers. A post written in your language pulls the output towards that language, and a post with mixed language content produces mixed output. There is no magic here. If the strongest signal reaching the generator is English, English is what comes back. ![RankReady FAQ Generator settings under the AI Content tab](https://hostmy.blog/wp-content/uploads/2026/08/rr-faq-settings-v2-scaled.png)The FAQ Generator sits under AI Content, subtab faq. ## 1. Write the focus keyword in the target language Open **RankReady > AI Content** and select the **FAQ** subtab (`tab=content&sub=faq`). Enter the focus keyword exactly as a reader in that language would type it into a search box, not as an English translation of your topic. This is the single highest-impact change. It affects both the People Also Ask lookup and the phrasing of what the model produces afterwards. ## 2. Decide whether you want the People Also Ask data at all The DataForSEO lookup is optional. It exists to ground the FAQs in questions people actually search for. If the keyword lookup keeps returning English results for your market, you have two choices: - Keep it on, and put more effort into the local-language keyword until the returned questions look right. - Switch it off, and let the generator work from your article alone. You lose the real search data, but you remove the strongest English signal in the pipeline. Try it both ways on one post and compare. It takes two minutes and it will tell you which path suits your site. ## 3. Check the post content itself Look at the post the generator is reading. Common problems: - Long English quotations, code comments or product names dominating a short post. - A translated post where only the visible body was translated and headings or captions were left in the source language. - A very short post, where the focus keyword becomes proportionally more influential than the body text. Fix the content first, then regenerate. Feeding the generator cleaner input is more reliable than trying to correct the output afterwards. ## 4. Regenerate and check the whole set Regenerate the FAQs for that post and read every entry, not just the first one. Language drift often shows up part-way down a list. If some entries are right and others are not, that usually means the inputs are mixed rather than that the generator failed. Clear your page cache before checking the front end, or you will be reading the previous version. ## 5. Edit what remains The FAQs are stored on the post as normal WordPress meta and can be edited. For anyone inspecting the data directly, the FAQ meta key is `_rnrd_faq` and it holds a flat array of objects shaped as `[{"question":"...","answer":"..."}]`. For comparison, the summary meta key is `_rnrd_summary` and holds `{"bullets":[...]}`. Editing a handful of entries by hand is often faster than regenerating repeatedly, particularly for the last stubborn item in an otherwise correct set. Generation is unlimited, so regeneration costs you nothing beyond your own provider usage, but your time is worth something too. ## Multilingual sites If you run WPML, Polylang or a similar setup, treat each translation as its own job. Generate FAQs on the translated post, with a focus keyword in that translation's language, rather than generating once and expecting the output to follow the translation. Be aware of one current limit so you do not plan around something that is not there: per-language `/llms.txt` generation is listed as coming soon, not shipping. Plan your multilingual AI visibility with that in mind. ## Provider choice RankReady supports OpenAI, Anthropic Claude, Google Gemini and DeepSeek, and you bring your own key. If one provider consistently drifts to English on your content while another holds the target language, switching provider in **Settings** is a legitimate fix. Test the same post with the same focus keyword on two providers before you decide, so you are comparing like with like. ## What to check before asking for help Note the exact focus keyword you used, whether the DataForSEO lookup was on or off, which provider was selected, and the language of the post body. Those four facts explain nearly every wrong-language result, and they are the first four things anyone helping you will ask for.