In October 2025, Apple’s Chinese website made the news for the wrong reason. On the AirPods 4 product page, in the headline copy describing Active Noise Cancellation, the company misspelled its own flagship product name. “AirPods” became “ArPods.”
Chinese social media users noticed within hours. The error climbed Weibo’s trending list. Some joked that ArPods was “Apple’s new sub-brand.” Others teased that CEO Tim Cook was so committed to environmental sustainability he had even saved the letter “i.”
What made the incident telling was not the typo itself, but its location. Apple’s English-language website, viewed from anywhere in the world, spelled AirPods correctly. The error existed only on the localized version. And it was not the first.
In January 2025, Apple’s China site referred to “iPhone” as “iPone” in a support document about iOS 18, again, only in the Chinese version. In February, Apple’s Norwegian website introduced the then-unreleased iPhone 16e by accidentally calling it the “iPad 16e,” confusing two product lines on the same page.
Three high-profile typos in three localized markets in twelve months. From a company famous for design precision.
This is what makes Apple a useful starting point: if a brand with Apple’s resources, processes, and reputation can ship localization errors this consistently, every global company should be paying closer attention to its own. According to CSA research, 76% of online shoppers prefer to buy products in their native language, and 72% say typos on a brand’s official website would reduce their willingness to buy. Localization is not a finishing touch but the surface on which trust gets built or broken.
What follows are fifteen documented cases of translation and localization errors from global brands, governments, and platforms. Some are funny. Some are serious. A few changed lives. Together, they form a practical map of where localization actually goes wrong, and how to keep it from going wrong on your watch.
The top 15 translation errors
1. Amazon's Swedish launch: "Rape" Instead of rapeseed
When Amazon launched its dedicated Swedish marketplace in October 2020, Swedish users opened the site to a series of small disasters. The country selector showed an Argentinian flag where the Swedish flag should have been. Product listings translated automatically from English contained a now-infamous error: items labeled with “raps,” the Swedish word for rapeseed, had been rendered as “våldtäkt,” the Swedish word for rape.
Reuters and other outlets documented faulty translations across the entire product catalog. Swedish Twitter spent the day cataloging them.
The lesson? Localization QA cannot stop at the user interface. Every product feed, taxonomy, image asset, country selector, and machine-generated string is a potential failure point—and product catalogs, with millions of auto-translated SKUs, are where MT errors compound fastest.
2. The Welsh road sign that was an out-of-office reply
In 2008, Swansea Council in Wales needed a bilingual road sign for a no-entry zone. They emailed their Welsh translation team for the Welsh version, received a reply, and printed it on a metal sign that was installed near a supermarket.
The Welsh text read roughly as “I am not in the office at the moment. Please send any work to be translated.”
Snopes verified the photo and the story. The sign became internationally famous and remains one of the most widely cited public-sector localization blunders ever.
The lesson? Never route translated content directly from inbox to production. Even short, “obvious” public text needs a human verification step from someone who reads the target language.
3. Mitsubishi's Pajero
Mitsubishi named its flagship SUV after the Pampas cat (Leopardus pajeros). Unfortunately, in colloquial Spanish, “pajero” carries vulgar and derogatory meanings. Mitsubishi caught the issue early enough to rebrand the vehicle as “Montero” across North America, Spain, and most of Latin America), where it sold for decades under the safer name.
The lesson? Brand names need linguistic and slang screening across every target market before launch, not after the jokes start trending.
4. Coca-Cola in China: From "Bite the Wax Tadpole" to 可口可乐 (1920s)
When Coca-Cola first reached China in the 1920s, local shopkeepers improvised phonetic Chinese renderings of the brand name. The results were unfortunate. Some characters chosen for their similar sound translated to phrases like “female horse fastened with wax” or, most infamously, “bite the wax tadpole.“
Coca-Cola’s response is one of the great transcreation success stories.
The company eventually settled on “可口可乐” (kě kǒu kě lè), which approximates the original sound while meaning, roughly, “delicious happiness” or “tasty fun.” The Chinese name is now studied in marketing courses worldwide.
The lesson? The best localization preserves sound, meaning, memorability, and emotional fit simultaneously. This is why we call it transcreation, not translation and why the difference matters commercially.
5. Kia Provo and the Northern Ireland problem (2013)
When Kia unveiled its Provo concept car at the 2013 Geneva Motor Show, the name was linguistically harmless. But politically, that was a different story. In Ireland and Northern Ireland, “Provo” is the colloquial term for a member of the Provisional IRA.
DUP politicians demanded the name be dropped. Kia confirmed it would not sell a UK production car under the Provo name and apologized for any offense caused.
The lesson? A name can pass every linguistic test and still fail because of historical or political associations specific to a market. Cultural screening is a separate exercise from linguistic screening.
6. Mango's "slave-style" necklace (2013)
In 2013, French shoppers on Mango’s e-commerce site found jewelry listed as “collier style esclave” (“slave-style necklace”). The error appears to have originated in Spanish, where “esclava” is a common term for a particular style of bangle or chain bracelet. When the catalog text was carried over to French, “esclava” became “esclave,” which in French unambiguously means “slave.”
Public outrage was immediate. A petition circulated. Mango apologized and removed the items within days.
The lesson? Product taxonomies are full of false friends (words that look like cognates but carry different meanings, registers, or histories across languages). Literal transfer of fashion, beauty, or food terminology is one of the highest-risk areas in e-commerce localization.
7. Facebook's Arabic "Good Morning" arrest (2017)
In October 2017, a Palestinian construction worker in the West Bank posted a photo of himself leaning against a bulldozer. The caption was a single Arabic phrase: “يصبحهم” (“good morning to them”).
Facebook’s automatic translation rendered it as “attack them” in Hebrew and “hurt them” in English. Israeli police, acting on the translation without consulting an Arabic speaker, arrested the man on suspicion of incitement. He was held for several hours before officers realized the error and released him.
The lesson? Machine translation should never be the sole basis for decisions in policing, security, legal proceedings, or any context where misunderstanding has irreversible consequences. The right answer is always: route to a human qualified in the source language.
8. Meta's Kannada translation implies the Karnataka CM Died (2025)
In July 2025, Meta’s auto-translation feature processed a Kannada-language condolence post from the office of Karnataka Chief Minister Siddaramaiah, expressing grief over a fan’s death. The English auto-translation was botched in such a way that it implied the Chief Minister himself had died.
Siddaramaiah’s office publicly criticized Meta and asked that the Kannada auto-translation feature be suspended until reliability could be verified. Meta acknowledged the error and said it had been fixed.
The lesson? Lower-resource and regional-language MT remains substantially less reliable than its English-French-Spanish equivalents. For official communications, sensitive public messages, and any content where misreading the subject of a sentence changes its meaning entirely, regional-language MT needs human review as a default, not an exception.
9. Willie Ramirez and the $71 million word (1980)
In January 1980, 18-year-old Willie Ramirez was rushed to a South Florida hospital in a coma. His Spanish-speaking family told the medical team he was “intoxicado.” A Cuban Spanish term that means “poisoned” or “made sick by something ingested,” with no implication of alcohol or drug use.
Hospital staff translated it as the English false cognate “intoxicated.” Ramirez was treated for an apparent drug overdose. He had in fact suffered an intracerebellar hemorrhage that, untreated for over 36 hours, left him quadriplegic.
The case is widely reported as having resulted in a malpractice settlement of approximately $71 million. It is taught in medical interpreter training programs around the world.
The lesson? In healthcare, bilingual ability is not the same as professional medical interpreting. One false friend, accepted without challenge by clinicians who do not speak the source language, can redirect an entire diagnostic pathway.
10. Virginia tells Spanish-speakers the COVID vaccine isn't cecessary (2021)
During the COVID-19 vaccine rollout, the Virginia Department of Health used Google’s automatic translation tool to produce Spanish versions of its public health pages. The English source said the vaccine “is not required,” meaning, it was not legally mandatory.
The Spanish translation read “la vacuna no es necesaria,” meaning, the vacaccine is not necessary. The American Translators Association flagged the error publicly.
The lesson? “Not required” and “not necessary” are categorically different statements in any language and conflating them in a public-health context can affect real medical decisions. Public-sector translation needs human review by qualified professionals, not a Google Translate plugin and a hopeful click.
11. Once a day, or eleven? Spanish prescription labels (2010)
A 2010 study published in Pediatrics examined computer-generated Spanish translations of medication labels in 286 New York pharmacies. The researchers found widespread errors that could put patients at serious risk.
The most dangerous involved the English word “once” being left untranslated in Spanish text. In Spanish, “once” is a real word that means eleven. A patient reading the label would interpret “once daily” as a prescription to take eleven doses per day. Other errors included mistranslations of “dropperfuls,” “for two days,” and “with food.”
The lesson? Medication instructions are controlled language with zero tolerance for ambiguity. Automated translation deployed without pharmacist or qualified interpreter review is a patient safety failure.
12. The "reset" button that said "overload" (2009)
In March 2009, US Secretary of State Hillary Clinton met Russian Foreign Minister Sergey Lavrov in Geneva and presented him with a symbolic gift: a yellow plastic button labeled with the word “reset” in English and Russian. The gesture was meant to signal a fresh start in US-Russia relations after years of friction.
The Russian word printed on the button was “peregruzka,” which means overcharged or overload. The correct word for “reset” is “perezagruzka.” Lavrov pointed out the error to Clinton on camera. Both diplomats laughed it off, but the symbolic moment had been undermined by a missing prefix.
The lesson? Short ceremonial text often gets the least review because it seems too simple to fail. It is often the most-photographed text your organization will ever produce.
13. When "drydocking" becomes "tank washing" (2012)
A frequently cited 2012 Shanghai Maritime Court case involved a shipping contract dispute caused largely by translation errors in the Chinese version of the agreement.
Among the documented mistranslations, the term “drydocking” was rendered as “tank washing,” and the phrase “except fuel used for domestic service” was translated as “except fuel used for domestic flights,” replacing maritime fuel with aviation fuel in a shipping contract.
The errors contributed to a contract dispute that took significant time and cost to resolve.
The lesson? In legal and technical contracts, terminology errors do not just produce awkward wording. They change obligations, allocate risk differently, and create ambiguities that opposing counsel will use. Domain-qualified translators (not generalists) are non-negotiable for high-stakes documents.
14. 207 errors in the Korea–EU free trade agreement (2011)
In 2011, South Korea’s Ministry of Foreign Affairs and Trade was forced to publicly acknowledge that the Korean-language version of the Korea–EU Free Trade Agreement contained 207 translation errors and omissions. The trade minister issued a public apology and submitted a revised version.
The discovery disrupted the ratification process and became a sustained political embarrassment in the run-up to one of the largest trade deals in Korean history.
The lesson? Large-scale legal and treaty translation requires layered review, terminology management, version governance, and a dedicated quality assurance pipeline. The bigger the document, the harder it is to catch errors after the fact, and the more likely they are to surface publicly.
15. Hartford's Spanish ballot (2023)
In the 2023 Hartford, Connecticut municipal election, Spanish-speaking voters received ballots with instructions translated in a way that, by official accounts, rendered “turn the ballot over and vote on both sides” as something closer to “shift ticker above and vote twosides“. City officials confirmed the errors and corrected the ballot.
The lesson? Election translation is voting access. Errors here are not just embarrassing, they are civil-rights problems and trust problems. The same logic applies to any public-facing instructional content where comprehension determines whether a person can exercise a right or use a service.
Bonus translation mistake: The treaty that two nations still argue about
In 1840, representatives of the British Crown and over 500 Māori chiefs signed what would become the founding document of New Zealand. There were two versions: one in English, one in Māori. They are not the same text.
The English version says Māori chiefs ceded “sovereignty” to the Crown. The Māori version uses “kāwanatanga” (governance), while preserving “rangatiratanga” (chieftainship, self-determination), for the chiefs themselves.
The two concepts do not map cleanly onto each other in either direction. Official New Zealand archives now publish both versions side by side precisely because the difference cannot be resolved by translation alone.
The disagreement has shaped New Zealand law, politics, and Māori-Crown relations for nearly two centuries.
The lesson? Some translation problems are not “errors” at all. They are enduring legal and conceptual ambiguities created when source and target languages encode different worldviews. Recognizing when this is happening is itself a localization skill. The right response is not to pick one rendering and move on, but to flag the ambiguity, document it, and resolve it deliberately.