When Perplexity answers product questions in German or Spanish, it describes our equipment differently than the English version—sometimes omitting our key specs. How do we fix this across languages?

Perplexity and similar engines train on multilingual web content, so inconsistent or missing translations of your product pages will show up as gaps in non-English answers. The engine isn't deliberately changing your story; it's working with whatever data exists in each language corpus.

Start by auditing what Perplexity actually sees. Search for your core product queries in German and Spanish directly in Perplexity, screenshot the answers, and note which specs or claims appear or disappear. Then check whether your website has full, native translations of those product pages—not machine translation, but human-reviewed content that includes your technical specifications, certifications, and differentiators in each language.

If translations exist but Perplexity still misses them, ensure each language version has proper hreflang tags pointing back to the English original, and that your robots.txt allows crawling of all language variants. Perplexity respects these signals.

If you don't have translations yet, prioritize the languages where you sell or want to sell. Create dedicated translated product pages with the same depth as your English pages—include specs, use cases, and any third-party certifications. Use schema.org markup (Product schema with multilingual name and description fields) on each version.

Give it two to three weeks for Perplexity's index to refresh, then re-run those same queries in each language. You should see your specs and claims appear more consistently.