Lessons from misread domain names

The most avoidable loss in this market is not overpaying. It is buying a name that says something other than what the buyer thought, discovering it after launch, and having to choose between explaining it forever and starting again.

Four patterns, all preventable.

1. The tone-mark collision

Specific to Vietnamese and the most common. The unaccented string maps to several words, and the market picks a different one from the buyer.

Sometimes the alternative is merely different, which costs explanation. Sometimes it is unfortunate, which costs the name. The buyer never finds out from a dictionary, because the dictionary confirms their intended word exists.

Fix: three native speakers read the bare string cold, before purchase. Their first answer, written down before you say anything.

2. The unfortunate substring

Two innocent words joined, and the junction produces a third word nobody intended. This happens in every language and is the classic reason for reading a compound as a continuous string rather than as its parts.

It is invisible to the person who chose it because they read the components, not the string. It is immediately visible to everyone else.

Fix: read the name aloud as a single continuous word, and have someone unfamiliar with it do the same.

3. The false friend across languages

A word that is fine in one language and means something else in another. Relevant to any business whose name will be read in more than one place, which is most of them eventually.

Fix: check the string in the languages of every market you plan to enter, not just the one you launch in. A speaker, not a translation tool — tools give the dictionary sense and miss the colloquial one, which is the one that causes problems.

4. The wrong register

Less dramatic and more common than the other three. The name is correct and unambiguous, and it is in the wrong register: formal where customers are casual, or slang where the audience expects gravity.

A clinic named in the register of a street-food stall, a children's brand named in bureaucratic vocabulary. The name works; it just signals the wrong thing, permanently and quietly.

Fix: ask native speakers not only what it means but what kind of business it sounds like. The second answer is often more informative than the first.

Why competent people keep making these

Because the testing is done backwards. The team writes the name properly, with marks and spaces and capitals, and asks whether it works. It does. What launches is the bare lower-case string with no marks, and nobody tested that.

And because by the time anyone thinks to test, the logo exists, the deck has been shown, and the name has become a decision rather than a candidate.

The afternoon that prevents all four

Take every candidate as a bare lower-case string. Give it to three native speakers separately, with no context. Ask: what does this say, is it a thing people say, and what kind of business does it sound like? Write the answers verbatim.

Then check the string in every other language you will operate in. Then read it aloud as one continuous word.

An afternoon, at the stage where changing course costs nothing. Every pattern above is caught by it, and the businesses that skip it are the ones telling these stories later.