How I'd Pick a Domain Name for a New Project
Naming a project is fun for about ten minutes. Then you start typing ideas into a registrar's search box and discover every word in the dictionary was taken years ago, mostly by people who've never built anything on them. So here's how I'd go about it without losing a whole weekend.
Start with the radio test. Say the name out loud to someone and ask them to type it. If they hesitate over spelling, ask "is that with a K?", or put a hyphen in the wrong spot, the name is going to cost you visitors forever. Clever misspellings look great in a logo and terrible in a conversation. Same goes for numbers. Is it "four" or "4"? Nobody knows, so they guess, and half of them guess wrong.
Shorter is better, but readable beats short. A twelve-letter name made of two real words is easier to remember than a seven-letter string of consonants. If you can't get the exact word you want, adding a plain verb or noun usually works fine. "get", "use", "try" and "app" prefixes and suffixes are a bit tired, but they're tired because they work.
Then there's the extension question. A .com is still what most people assume when they hear a name, so if you can get a decent one, take it. But I don't think it's worth twisting a good name into a bad one just to land a .com. Plenty of projects live happily on .io, .dev, .app, .co or a country code that happens to spell something. A couple of things worth knowing, though:
- .dev and .app are on the browser HSTS preload list for the whole extension, so sites on them only load over HTTPS. That's a good thing, but it means you need a certificate from day one, even for a quick test page.
- Country-code extensions belong to a country, and that country sets the rules. Some require local residency, and policies can change. Read the registry's terms before you build a brand on one.
- Cheap novelty extensions can get abused by spammers, and some mail filters and corporate firewalls treat whole extensions with suspicion. Worth a quick search before you commit.
Before you buy, do a little homework. Search the name plus "trademark" and check your country's trademark database. You don't want a polite-but-firm letter after you've printed stickers. Check whether the matching handles are free on whatever social platforms you care about. And look the domain up on the Wayback Machine. A previously used domain might come with a history you'd rather not inherit, like being blacklisted for spam.
When it comes to actually registering, the registrar matters less than people think, but a few things are worth checking. Look at the renewal price, not just the first-year price. Introductory deals are common and the jump in year two can be a surprise. Make sure WHOIS privacy is included (most good registrars include it for free now). Turn on auto-renew and registrar lock, and put two-factor on the account. Losing a domain because a card expired or someone phished your registrar login is a miserable, very avoidable way to end a project.
I'd also keep domains at a registrar that's separate from your hosting. If you ever want to move hosts, or the host has a bad day, your domain isn't tangled up in it.
One last thing. If you find a name you like and it's available, just buy it. They're cheap compared to how much you'll second-guess yourself, and the good ones don't stay open long. You can always let it lapse next year if the project goes nowhere.

Comments