Why your invented language's names don't sound like they belong together
A worldbuilder's fantasy names often feel like a random grab bag. The fix is phonotactics — a small set of syllable rules that make every coined word sound like it came from the same place.
Here's a problem every worldbuilder eventually runs into. You name your first city Aveloria and it sounds gorgeous. You name the second one Kthaxel because it sounds appropriately foreign. You name a character Bob because you were tired. Three names in, your invented culture already sounds like it was assembled from three different languages by three different people — because, in a sense, it was. The names don't share a sound, and readers feel that inconsistency even when they can't articulate it. The fix isn't a better ear or more inspiration. It's phonotactics: the small, boring, powerful set of rules that decide which sound-combinations your language allows.
What phonotactics actually means
Every real language has rules about which sounds can sit next to which, and where. English lets you start a word with "str-" (street, strong) but never "tsr-"; it lets a syllable end in "-nk" (think) but never "-nkg". You follow these rules effortlessly and unconsciously — which is exactly why a made-up name that breaks your language's rules feels wrong without you knowing why. Phonotactics is the study of those constraints, and for a conlanger or a fantasy author it's the single highest-leverage tool for making a set of names feel like they belong to one people.
The core building block is the syllable, usually described as a pattern of consonants (C) and vowels (V). "CV" is the simplest possible syllable — a consonant then a vowel, like "ka" or "to". "CVC" adds a closing consonant, like "kat" or "mor". "CVCC" allows a two-consonant cluster at the end. A language's phonotactics is largely just the list of syllable shapes it permits plus the inventory of sounds that can fill each slot. Pin those down and you've defined the sonic fingerprint of your entire language.
Two knobs: the shapes and the inventory
Consistency comes from deciding two things and then sticking to them. First, your allowed syllable patterns. A language that only permits CV and CVC will sound open and flowing — think Polynesian-flavored names like "Amana" or "Telani". Allow heavier clusters like CVCC and CCVC and it turns craggy and Slavic, all "Vradst" and "Krenth". The moment you let in a shape that isn't on your list, the illusion cracks. So the second knob is your phoneme inventory: the specific consonants and vowels that exist in this language at all. Maybe your consonants are p, t, k, m, n, s, r, l and your vowels are a, e, i, o, u — a clean, common set. Any name built only from those sounds, arranged only in your allowed syllable shapes, will automatically sound like it belongs.
This is where the earlier example falls apart. "Aveloria" is basically V-CV-CV-CV-V, all soft sounds — fine. "Kthaxel" opens with "kth", a three-consonant onset that almost certainly isn't in your allowed patterns, and uses "x", which probably isn't in your inventory. It's not that Kthaxel is a bad name in the abstract; it's that it obeys a different phonotactics than Aveloria, so the two can't credibly come from the same world. Consistency doesn't mean every name sounds identical — it means every name plays by the same rules.
Checking your work, not just trusting your ear
The trouble with doing this by feel is that the human ear is forgiving in the wrong direction. After you've been staring at your own names for an hour, the ones that break your rules stop sounding wrong — you've habituated to them. What you need is a mechanical check: define the rules once, then test every name against them and get told, without sentiment, which ones don't fit.
That's exactly what our checker does. You give it your allowed syllable patterns (say, CV and CVC), your consonant list, and your vowel list, then paste in every name you've coined. It attempts to break each word into legal syllables using your rules, and flags any word it can't — telling you the position where the illegal cluster starts. Feed it "aman, katira, mendor, kthaxel" against a CV/CVC ruleset with a p-t-k-m-n-s-r-l inventory and the first three pass while "kthaxel" gets flagged at the opening cluster. It also reports a consistency score — the percentage of your names that fit — which is a genuinely useful single number to watch as your name list grows. A culture whose names score 100% will read as unmistakably coherent; one sitting at 60% is quietly telling readers that something doesn't add up.
Generating names that already fit
Once the rules are defined, they don't just judge — they can create. Because the checker knows your syllable shapes and your sound inventory, it can assemble brand-new words that are guaranteed legal by construction: pick a random allowed pattern, fill each slot from the matching inventory, repeat for one to three syllables. The result is a stream of coinages that already sound like your language, ready to be plucked for a city, a river, or a minor character who needed a name five minutes ago. This is the fastest way past the "Bob because I was tired" failure — instead of reaching for a placeholder that breaks the world, you pull a compliant word that reinforces it.
None of this requires becoming a linguist. You need two lists and a handful of syllable shapes, and the discipline to run new names against them instead of trusting a fatigued ear. Do that, and a reader who has never heard the word "phonotactics" will still feel that your world's names come from a real, coherent place.
Our conlang syllable and phonotactics checker lets you define your allowed patterns and phoneme inventory, batch-test every name you've invented for consistency (with a score and precise flags on the ones that break the rules), and auto-generate fresh words that fit by construction. Set your rules once and every future name — city, character, or river — can be checked against the same fingerprint before it ever reaches the page.
مقالات ذات صلة
From word count to finished draft: planning a novel you will actually finish
Genre word-count targets, how manuscript words turn into print pages, and the daily-target math that makes a deadline realistic instead of aspirational.
Designing a planet readers will believe: a worldbuilder's guide to gravity
How surface gravity really works, what high- and low-g worlds do to bodies, jumps, and buildings, and how to pick numbers that keep a fictional planet physically honest.
How many blacksmiths does a fantasy town have? Building believable settlements
Why most RPG towns have far too many shops for their size, the medieval demographics that fix it, and how population alone tells you the smiths, inns, gold limit, and farmland a settlement needs.