You type a name into a checker. Green lights everywhere: .com is free, GitHub is open, the npm package doesn’t exist. You register everything and start building.
Six months later, you discover that nobody can find your product on Google because the word means something else entirely. The name was available. It was not ready.
What a Name Availability Check Actually Tells You
Most name availability checks answer one question: is this taken? The better tools go further — showing results across dozens of TLDs, flagging social handle conflicts, and some even surface basic linguistic signals like pronunciation hints or language warnings. That’s genuinely useful work, and finding a name that’s actually open across the surfaces you need is a hard problem on its own.
But even the most thorough availability check stops short of a different question: is this name fit for purpose?
A name that passes availability can still fail on dimensions that no registry lookup covers.
Consider well-known developer tool names. Run them through an availability checker today and you’d see unavailable across the board — every logical domain parked, every handle occupied. By pure availability, they look terrible. But they work for reasons that no availability check measures: phonetic clarity, spelling simplicity, search distinctiveness, global neutrality. Their quality has almost nothing to do with current availability.
Availability tells you whether a name is open. It doesn’t tell you whether it’s good.
Five Dimensions Beyond Name Availability
Once you have a candidate that passes availability — and that’s already an achievement — these are dimensions worth evaluating before committing. They aren’t exhaustive, but they cover the friction points that surface most often in practice.
1 Sound
How does the name feel when spoken aloud? Research in phonosemantics suggests that names with strong onset consonants tend to feel decisive, while names with soft openings tend to feel more approachable. Names where the stress pattern is ambiguous can create hesitation.
Your name will be said in meetings, on podcasts, in conference talks. If people pause before saying it, that’s a signal worth noticing.
2 Spelling
Can someone hear the name and type it correctly on the first try? Some names have only one plausible spelling — no ambiguity. But names with ambiguous vowels, silent letters, or unusual letter combinations create spelling friction: the gap between hearing a name and successfully typing it into a browser.
3 Search Distinctiveness
Google your name candidate. What comes up?
- Invented words: the search results page is yours to claim. Low competition, but you need to build all the context from zero.
- Common words: you’re competing with a dictionary definition and every other use of that word. Some companies have made this work — but it typically takes years of traction and SEO investment that most teams can’t replicate.
- Modified or uncommon words: low ambiguity. A standalone search is more likely to resolve to your product.
The question isn’t just “is the .com free?” — it’s “can you realistically own this word in search results?”
4 Cultural Surface
A name that works in English might create friction elsewhere. “Mist” means garbage in German. “Latte” means simply “milk” in Italian, not the coffee drink English speakers expect. Even purely invented names can accidentally echo existing words in other languages.
This doesn’t mean every name needs to be globally perfect. But for a product that will reach international users, it helps to know what you’re shipping before you ship it.
5 Name Consistency Across Surfaces
This dimension is different from availability. Availability asks: is the name open? Consistency asks: can you use the same name everywhere, or will you end up with fragments?
| Surface | Ideal | Compromise |
|---|---|---|
| Domain | name.com | getname.com, name.dev |
| GitHub | github.com/name | github.com/name-hq |
| npm | name | @name/core |
| Twitter/X | @name | @name_hq |
| CLI | name (in PATH) | name-cli |
A name might be available on each surface individually — but as a different variant each time. One or two compromises are normal. Five means the name fragments across its digital surfaces, and that creates naming debt that compounds over time.
What Else Matters
Two areas sit outside this framework but deserve serious attention:
Trademark risk. A name can pass all five dimensions and still trigger a cease-and-desist. Trademark search is a legal question, not a naming one — but ignoring it is arguably the most expensive naming mistake a team can make. If the name will represent a commercial product, a basic trademark search in your target jurisdictions is worth the effort.
Renaming is possible, but gets harder with time. Plenty of projects have renamed successfully, especially early on. But the cost grows non-linearly with adoption: every user, integration, backlink, and package reference makes the change harder. The five dimensions help you reduce the chance of discovering a problem after the name has already hardened into your infrastructure.
The Takeaway
Name availability checks solve a real problem — they save you from registering a name that’s already taken. That’s valuable, and finding an available name is often the hardest step.
But a name that passes availability is a starting point, not a conclusion.
Before you commit:
- Say it out loud ten times. Does it flow, or do you hesitate?
- Have someone else spell it from hearing alone. Any confusion?
- Google it. What do you compete with on the first page?
- Check it in three languages your users speak.
- List every surface where the name will appear. Run
whois, search npm and PyPI, check GitHub. Can you use it consistently?
Naming problems found before git init are cheap to fix. Naming problems found after launch are significantly harder.
In a product, a name is not an ornament. It is an interface, an asset, and a potential source of debt.