How to Choose a Domain Name: 12 Rules for Finding the Right Domain

A domain name does several jobs at once. It tells people where to find you. It appears in every link, email, business card, and ad your business ever produces. It is the first credential a visitor sees before your site loads. And for many customers, it is the brand itself: the thing they type when they want to return.

Most domain name advice focuses on rules. This article does too, twelve of them, but with an important distinction. Each rule includes an explanation of why it exists and whether the underlying reason is supported by research, grounded practical logic, or convention that has been repeated long enough to feel like fact.

Some commonly repeated domain advice is well-supported. Some is closer to the domain-industry equivalent of folk wisdom. Knowing the difference helps you make trade-offs intelligently rather than treating every rule as equally binding.

One framing point before the rules, because the rest of the article builds on it.

A domain name is not the same thing as a brand name. They often match and usually should (our guide to what makes a good brand name covers the naming side), but the domain adds constraints that pure brand naming does not. It must work as a URL: typed in an address bar, embedded in a link, read aloud on a podcast, and printed in a font so small a hyphen is nearly invisible. Those constraints are practical rather than psychological, and they shift the evaluation criteria in important ways.

1. Make It Easy to Remember#

Memorability is the most important quality a domain can have, because a domain people cannot recall is a domain they cannot return to.

The psychology of why some names are more memorable than others is reasonably well-established. Research on processing fluency, defined as the cognitive ease with which a stimulus is processed, consistently shows that easier-to-process information is evaluated more positively and tends to be better retained. Alter and Oppenheimer (2006) demonstrated that stocks with more pronounceable names showed better short-term returns shortly after listing than stocks with less pronounceable names, even after controlling for other factors. The finding suggests that fluency affects real evaluative judgments rather than just experimental ratings.

For domain names specifically, memorability is supported by several factors working together.

• Phonetic distinctiveness: A name with a unique sound pattern creates a more distinct memory trace. Generic terms disappear into the background of everything else stored under the same conceptual category.
• Associative richness: Names that connect to existing imagery, emotions, or concepts give memory more material to work with. "Amazon" creates a vivid picture. "Infosys" is harder to visualize.
• Brevity: Shorter inputs place less strain on working memory during encoding. This is not a reason to always prefer short names, but it is a real contributing factor.

What this means in practice: After shortlisting several domain candidates, imagine you have just heard each one mentioned once in a podcast ad with no spelling shown and no URL displayed. Forty-eight hours later, could you type it correctly from memory? The names that survive that scenario are your strongest candidates.

Evidence quality: Strong for processing fluency effects on evaluations generally. Moderate for direct application to domain memorability, which has received less dedicated study than brand name recall.

2. Make It Easy to Say#

A domain that is hard to pronounce is a domain that dies in conversation.

Word-of-mouth referrals, podcast mentions, and verbal recommendations are among the most valuable acquisition channels for early-stage businesses. All of them require that the person speaking can say the name without hesitation and that the person listening can reconstruct it accurately.

The research on name pronunciation effects is notable here. Laham, Koval, and Alter (2012) demonstrated that people with easier-to-pronounce personal names were evaluated more favorably across multiple contexts. The authors attribute this to fluency-based affect. One well-supported explanation is that when something is easy to process, the positive feeling that comes from that ease gets attributed to the thing being processed rather than to the ease of processing itself. This is a proposed mechanism rather than a settled conclusion, but it is consistent with a broad body of fluency research.

What "easy to say" means for domains:

• No unusual consonant clusters that require pausing or second-guessing.
• No syllables where stress placement is ambiguous.
• No sounds that collapse into each other or create unintended words when spoken quickly.
• Clear syllable boundaries that allow confident reading on first encounter.

Common failure mode: Compound names where two words share consonants, such as "SwiftTech" or "SharpPrint," create a small puzzle for speakers. Should both consonants be pronounced? The hesitation is minor but real, and it compounds across thousands of verbal mentions.

Evidence quality: Strong for pronunciation fluency effects on evaluation. Practical application to domain names requires extrapolation from the brand name literature, but the underlying mechanism is well-established.

3. Make It Easy to Spell#

Spelling difficulty is where the brand name world and the domain name world diverge most sharply.

In print, on a screen, or on packaging, a hard-to-spell brand name is an inconvenience. In a domain, spelling difficulty creates a structural leak in your traffic. Every person who hears your name and types it incorrectly either reaches a blank page, a parked domain, a competitor's site, or somewhere with content that works against you.

The spelling-pronunciation gap is a domain-specific risk. When a spoken name can be rendered in multiple plausible spellings, a consistent percentage of potential visitors will choose the wrong one. That percentage does not shrink over time and is largely unrecoverable through marketing spend.

Several categories of names create predictable spelling problems. Names with phonetic ambiguity, where the same sounds have multiple standard spellings, create confusion at scale. Deliberate misspellings, names using vowel drops, letter substitutions, or intentional nonstandard forms to solve a domain availability problem, shift the spelling burden permanently onto the audience. Silent letters and irregular patterns borrowed from other languages create the same problem. Homophone pairs, names that sound identical to other words with different spellings, create permanent routing uncertainty.

On deliberate misspellings: Using a nonstandard spelling to secure an available domain is a legitimate strategy, but it should be a conscious decision with acknowledged costs. Teaching people the correct spelling takes time and money. Whether that investment is justified depends on how important the specific name is relative to available alternatives.

Evidence quality: Spelling difficulty effects are well-supported in usability research. The specific impact on domain traffic is a practical inference from the mechanism rather than a finding from dedicated peer-reviewed domain research, but the logic is clear and the risk is real.

4. Keep It Short When Possible#

The case for short domains is partly cognitive and partly practical.

On the cognitive side, shorter names place less demand on working memory during both encoding and retrieval. The working memory literature establishes meaningful constraints on how much information people can hold in mind at once, and shorter names work within those constraints more comfortably.

On the practical side, shorter domains are easier to type correctly, fit better in constrained display contexts such as business cards, social handles, and branded URLs, and give typists fewer opportunities for error.

The important caveats:

"Short" is frequently conflated with "the shortest possible," and that conflation produces bad advice. A two-character domain that is available but meaningless, hard to pronounce, and indistinguishable from competitors provides none of the actual benefits that motivate a preference for brevity. The cognitive load argument concerns the burden of length, and that burden only becomes meaningfully problematic past a threshold that most reasonable brand names never approach.

A name with three to four syllables that flows naturally, carries phonetic distinctiveness, and creates clear memorability associations will likely outperform a two-syllable name that lacks those qualities. Some of the most recognized web properties, including YouTube, Twitter, Reddit, Shopify, and Dropbox, are two-syllable domains. That is a practical sweet spot, but it is not a hard ceiling.

Where length genuinely matters:

• Typing burden increases with each additional character.
• Long domains get truncated or awkwardly wrapped in display contexts.
• Names with awkward rhythm stumble in speech.

A reasonable target: Aim for six to fourteen characters with two to four syllables. Fewer than six characters is ideal but competes with extreme scarcity. More than fourteen characters starts imposing meaningful practical costs.

Evidence quality: Working memory rationale is sound. Specific character or syllable thresholds are not precisely defined by the literature. Professional consensus broadly supports brevity, though specific limits vary.

5. Choose a Name That Can Become a Brand#

A domain that merely describes what the business does today is rarely a strong long-term asset.

The distinction here is between generic descriptive domains such as buyshoes.com or cheapinsurance.io and brandable domains such as Nike.com, Stripe.com, or Notion.so. Generic descriptive names communicate immediately, but they also crowd poorly in competitive markets where everyone chooses the same cluster of terms. They cannot be trademarked in most jurisdictions because they describe the category. They create no distinctive memory structure since they are one of many similar-sounding names. And they limit the business's ability to evolve beyond its initial description.

Brandable names are ownable. They can be protected. They create a distinct position in memory. And they do not constrain the business to what it does on the day it launches.

Research on brand name suggestiveness (Keller, Heckler, and Houston, 1998) shows that names implying something about a category, without being generically descriptive of everything in it, tend to produce strong advertising recall. The practical sweet spot is a name with associative richness that suggests something without naming the category outright. "Amazon" is a useful example: it evokes scale and breadth without naming any specific product.

For domain selection: prefer names that could appear on a billboard without a tagline to explain the business. If the name requires a subtitle to be understood, it is probably working too hard to be descriptive.

Evidence quality: Brand name suggestiveness research is moderately well-supported. The specific application to domain selection involves reasonable extension from the brand naming literature.

6. Avoid Names That Are Too Narrow to Grow#

This rule addresses a related but different problem. While Rule 5 concerns generic names that are too broad to own, Rule 6 concerns specific names that are too narrow to grow into.

A company named BostonDogWalker.com faces three problems if the business succeeds. It cannot easily expand to other cities. It cannot expand to other pet services. And it is locked to a geographic identity that may no longer fit.

Product names create the same trap. A project management tool called SprintTracker.io may find that "sprints" as a concept falls out of fashion, or that the business evolves into something broader.

A useful test: can you imagine your business looking out of place under this name in five years? If yes, that is a meaningful signal worth taking seriously.

The exception: Deliberate specificity can be a feature for local, niche, or intentionally bounded businesses. A barbershop called The Bucktown Barber has a specific local identity that may be exactly right for its market. The question is whether the specificity is strategic or accidental.

Evidence quality: Practical guidance based on observed brand evolution patterns, not a finding from peer-reviewed research.

7. Decide Whether You Need a Keyword in the Domain#

Keyword-rich domains have a complicated history in search engine optimization.

For much of the early web, domains containing the exact keyword a user searched for received a meaningful ranking boost. A site at bestlawyersnyc.com might rank for "best lawyers nyc" disproportionately well relative to the actual quality of its content.

That advantage has shrunk considerably. Google's 2012 Exact Match Domain update significantly reduced the ranking benefit of keyword-rich domains with low-quality content. Google's Search Central documentation and public statements from Google representatives, including John Mueller in various public Q&As, have consistently indicated that the domain name itself is not a significant direct ranking factor. Content quality, links, and topical relevance matter far more. It is worth noting that these are public statements about a proprietary system whose internal workings are not fully disclosed.

Keywords in domains are not entirely without value. A keyword-containing domain can communicate immediately what the site does, which is useful for user comprehension and click-through rates in search results. It can reinforce topical relevance when combined with strong content. And it can provide context for anchor text in links from other sites.

What it cannot do is compensate for weak content, manufacture authority, or reliably outrank strong brandable domains that have earned genuine relevance through quality.

The practical guidance: If a keyword-containing domain is also genuinely memorable, appropriately short, and brandable, use it. If the keyword forces a long, generic, or clunky name, the SEO benefit is not worth the branding cost.

Evidence quality: The 2012 EMD update is a documented historical event. Google's current position is based on their public statements, which should be treated as informative but not as a complete disclosure of their algorithm. Direct peer-reviewed research on current EMD ranking effects is limited.

8. Choose the Right Domain Extension#

This is the area where domain advice is most often oversimplified.

.com is the historical default and remains the most widely recognized extension in most English-speaking markets. That recognition has real practical consequences. Users who hear a domain name without knowing the extension will typically assume .com. If someone owns the .com of your domain and you are on .io, a measurable percentage of people who hear your name will end up at the wrong destination.

But ".com is always better" is a different and weaker claim.

There is no high-quality peer-reviewed research demonstrating that .com domains produce meaningfully better business outcomes than other extensions when controlling for brand quality, marketing investment, and business fundamentals. The preference for .com is largely a cultural artifact of internet history rather than a law of consumer psychology.

What the extension actually affects is worth understanding in more detail.

• User expectations: Audiences accustomed to .com as the default will sometimes mistype or misremember a non-.com domain. This is a practical traffic-routing issue rather than necessarily a credibility problem.
• Category signals: Certain extensions have developed strong category associations. .io is widely accepted as a signal for technology and developer tools in the startup ecosystem. .org carries nonprofit associations. .gov and .edu are restricted to authorized entities and carry institutional authority signals.
• Regional extensions: Country-code TLDs such as .uk, .de, .au, and .ca can signal geographic focus and may provide modest preferential treatment in localized search results.
• Newer generic TLDs: Extensions introduced through ICANN's gTLD expansion program beginning in 2013, including .app, .dev, .studio, .tech, and .ai, have varying levels of adoption. Some have found strong category niches. Others remain obscure to non-technical audiences.

Practical guidance by context:

One more consideration: Some newer gTLDs have renewal pricing that is not always prominently disclosed at registration. Always verify both the registration price and the annual renewal price before committing.

Evidence quality: The .com preference is well-documented as a practical and cultural phenomenon. The claim that .com produces better business outcomes lacks rigorous peer-reviewed support. Extension guidance here is based on observed adoption patterns and practical logic.

9. Avoid Unnecessary Hyphens and Numbers#

Hyphens cause a specific and consistent problem: they are invisible in verbal communication. When someone hears "best-coffee.com," they hear "best coffee dot com." Some will type bestcoffee.com. Some will type best-coffee.com. Some will type best coffee.com and receive an error. The hyphen creates a permanent disambiguation burden that does not shrink over time.

The exception: hyphens are sometimes unavoidable when the unhyphenated version is taken and the hyphenated alternative is genuinely the best remaining option for a strategically important name. In that case, a deliberate choice with acknowledged costs is better than abandoning the name entirely. But the cost of teaching every user that a hyphen exists should be recognized and planned for.

Numbers create a different version of the same problem. When someone hears "7stars.com," they cannot know whether to type 7, seven, or VII. That ambiguity is permanent and unfixable. Numbers in brand names also tend to register as markers of lower brand sophistication, though this is an aesthetic judgment rather than a research-backed finding.

Legitimate uses of numbers: Brands for which the number is integral to meaning and recognition, such as a company genuinely called "7" or "37signals," can make numbers work because the number carries identity weight rather than simply occupying space.

Evidence quality: The verbal-communication argument against hyphens and numbers is grounded in clear practical logic. The aesthetic judgment about numbers reflects professional consensus rather than empirical research.

10. Check International and Cultural Interpretations#

If your business has any prospect of operating beyond its home market, this check is not optional.

Several well-documented naming failures have resulted from names carrying profane, insulting, or unintentionally comic meanings in languages the company later entered. These failures were avoidable. The only thing required was checking before launch.

The risks to screen for:

• Direct translation: Does the word mean something problematic in major languages you might enter?
• Phonetic similarity: Does the name sound like a problematic word in another language when pronounced?
• Cultural association: Does the name carry connotations in another culture that undercut your positioning?
• Script rendering: If you operate in markets using non-Latin scripts, how does the name transliterate, and is it pronounceable?

A practical approach: For any shortlisted domain, run the name by native speakers or verified translation services, not automated translation alone, for your three most likely international markets. The cost is minimal relative to the cost of a rebrand after launch.

Evidence quality: Cross-linguistic phonetic effects are documented in the linguistics literature. The practical risk is real and widely acknowledged by international branding professionals.

11. Check Availability Before Committing to the Brand#

This rule is about process rather than evaluation criteria.

Many founders make a significant process error: they build an entire brand identity, including a name, a visual language, and a product story, before checking whether the domain they need is available. By the time they check, they are so attached to the name that unavailability of the ideal domain feels like a crisis, leading to compromises made under emotional pressure.

The solution is to check availability at the beginning of the process, not the end.

Availability has several layers that are easy to conflate.

• Registration availability means the domain is not currently registered. This is what most basic availability checkers show. A domain may also be registered but inactive, meaning it is parked, held speculatively, or held by a previous owner who has let it lapse. A domain may be registered and actively used, meaning you would need to acquire it through negotiation, which may be possible at a price or may not be possible at all.
• Trademark conflict is a separate and often underestimated issue. A domain name or brand name may be protected by trademark in your jurisdiction or product category regardless of whether the specific domain is available. Registration availability does not mean legal safety. A domain registrar will sell you a domain that infringes someone else's trademark. The responsibility for avoiding infringement is yours. For any name you are seriously considering, a basic trademark search in your jurisdiction is part of a reasonable process. In the US, the USPTO's TESS database is publicly searchable. For names supporting significant investment, a trademark attorney's opinion is worth the cost.
• Social handle availability is a further layer. Your domain may be available while matching handles on Instagram, LinkedIn, X, and other relevant platforms are not. Inconsistent handles across platforms create friction that compounds over time.

Tools like axath allow you to batch-test dozens or hundreds of domain variations at once, surfacing available options across extensions and helping you identify alternatives before you have built a brand identity around an unavailable name.

Evidence quality: The trademark risk is a legal fact. The process recommendation is practical guidance based on observed patterns in founder behavior.

12. Think About the Domain Five Years From Now#

The domain you register today will appear on your email address, your contracts, your investors' materials, your press coverage, your customers' bookmarks, and your employees' business cards for years.

Switching a domain name after a business is established is significantly more disruptive than choosing carefully at the start. The costs include redirect management, SEO equity transfer, customer re-education, updated marketing materials, and an extended period where brand recognition is diluted across the old and new names simultaneously.

Questions to ask about a domain's long-term fitness:

• If the business doubles in scope, does this name still fit?
• If you pivot to an adjacent market, does this name create confusion?
• If you hire aggressively, will employees be comfortable putting this on their email signatures?
• If you raise a Series B, will this domain appear credible in investor materials?
• If you expand internationally, will this name work in new markets?
• If someone asks "what's your company called?" in a noisy room, can they reconstruct the domain?

None of these questions requires a certain answer at the founding stage. But asking them can surface a flaw that is not apparent when you are close to a name.

Evidence quality: Practical guidance based on observed patterns of brand and domain evolution. Not a finding from peer-reviewed research.

The Five-Step Domain Name Test#

When you have a shortlisted candidate, run this test with at least five people who do not already know your business.

Step 1: Say it once without spelling it. "I'm starting a company called [domain without the extension]. What would you type to find me?" Watch for: Spelling variations, hesitation, or requests to repeat the name.

Step 2: Wait 24 hours, then ask for it back. "What was the company name I mentioned yesterday?" Watch for: Complete forgetting, partial recall, or confident wrong answers.

Step 3: Ask what it suggests. "If you did not know what the company did, what would you guess from the name alone?" Watch for: Associations that are actively harmful, neutral (acceptable), or genuinely useful (ideal).

Step 4: Say it and ask them to write it down. Ask them to write what they hear. Compare spellings across your test group. Watch for: More than one version appearing across respondents.

Step 5: Show them the full domain with extension. "Does this look like a real company's website?" Watch for: Visible hesitation or negative association with the extension choice.

Scoring: No candidate should fail steps 1 through 4 entirely. Steps 2 and 4 are frequently the most revealing: names that seem obvious to the founder are often neither memorable nor consistently spellable to fresh ears. Step 5 is contextual: a .io may score lower with a consumer audience and perfectly well with a developer audience.

A Practical Domain Scoring Framework#

Use this to compare candidates systematically. Each factor is rated 1 to 3, where 1 indicates a concern, 2 indicates an acceptable result, and 3 indicates a strength. Evidence quality is noted for each factor.

Factor 1: Memorability (Research-supported) Is it memorable after a single exposure? Score 3 if yes. Score 1 if test participants frequently fail to recall it.

Factor 2: Pronounceability (Research-supported) Can it be said correctly on first encounter? Score 3 if there is one obvious pronunciation. Score 1 if stress, syllables, or sounds are genuinely ambiguous.

Factor 3: Spelling confidence (Research-supported) When people hear it, do they all spell it the same way? Score 3 if spelling is unambiguous. Score 1 if more than one spelling is plausible.

Factor 4: Length (Practical consensus) Is it appropriately short for practical digital use? Score 3 for under 12 characters. Score 2 for 12 to 16 characters. Score 1 for 17 or more characters, or if it is so short that it is cryptic.

Factor 5: Brandability (Moderate research support) Could it become a distinctive brand? Score 3 if it is genuinely ownable and distinctive. Score 1 if it is generic or descriptive of the entire category.

Factor 6: Flexibility (Practical) Will it still fit if the business evolves? Score 3 if the name can contain a broader business. Score 1 if it locks you into a specific geography, product type, or concept.

Factor 7: Sound-category fit (Moderate research support) Do the sounds of the name match what the brand should feel like? Score 3 if the phonetic qualities reinforce the brand's positioning. Score 1 if they work against it.

Factor 8: International usability (Practical) Has it been checked in your likely international markets? Score 3 if clean. Score 1 if there are known issues.

Factor 9: Extension appropriateness (Practical) Is the extension appropriate for the audience? Score 3 if .com or a well-understood category extension. Score 2 if an emerging extension with strong category fit. Score 1 if the extension creates obvious credibility or routing problems.

Factor 10: Legal and trademark risk (Practical; legal advice required for high-stakes decisions) Has a basic trademark search been done? Score 3 if clean. Score 1 if there are obvious conflicts or the search has not been completed.

Factor 11: Social handle parity (Practical) Are matching social handles available? Score 3 if the brand name is available across relevant platforms. Score 1 if there are significant conflicts.

Factor 12: Durability over time (Practical) Do you still feel confident about this name after living with it for a week? Score 3 if yes. This is a legitimate factor: a name you are already ambivalent about at launch tends to become a source of friction under pressure.

Scoring interpretation:

No domain needs to score 36. Many excellent business domains have one or two genuine weaknesses. The framework's purpose is to make those weaknesses visible before launch rather than after.

Common Domain Name Mistakes#

• Choosing the domain first, then building the brand around it. The domain is a constraint on the brand, not the brand itself. Start with what the brand should be, then find the best available domain expression of that brand. Inverting this process produces names shaped by availability markets rather than strategy.
• Registering the domain and assuming you are protected. Domain registration does not confer trademark rights. It does not mean the name is legally safe to use for commerce. If the name matters to your business, do the trademark research.
• Taking .com unavailability as a final answer. Many founders hear that their first-choice .com is taken and immediately abandon the name. Before abandoning it: check who owns it, whether it is actively used, whether it could be purchased, whether alternative expressions of the same name are available, and whether a strong alternative extension is appropriate for your market.
• Building significant brand equity before checking availability. This is the process error that causes the most pain. Check availability in the first week, not the last.
• Choosing a domain that requires explanation. "It's spelled like 'fire' but with a 'y' instead of 'ire.'" That sentence will follow you for years. Either the spelling is intuitive or it is not.
• Ignoring renewal pricing on newer extensions. Some generic TLDs, particularly .io, .ai, and various newer extensions, have registration pricing substantially below renewal pricing. A registration fee of $15 may renew at $50 or more per year. This is disclosed but frequently overlooked.
• Picking a name that is already associated with a competitor in your category. Even if the specific .com is available, using a name already connected to another brand creates confusion and potential trademark liability.

Frequently Asked Questions#

Should I always choose a .com domain?

In most consumer markets, .com remains the safest default because it matches the extension most users will assume when they hear a domain name spoken aloud. But "always" is too strong. .io is well-accepted in the developer and startup communities. Country-code extensions are appropriate for locally focused businesses. The decision should be based on audience expectations and availability rather than a universal rule.

How short should my domain be?

There is no single correct answer, but six to fourteen characters is a useful practical range. Fewer than six characters is ideal but faces severe availability constraints. More than fourteen characters starts imposing real typing and memorability burdens. The more important principle is that the domain should be as short as it can be without sacrificing pronounceability, distinctiveness, and brand fit.

Do keywords in a domain name help with SEO?

Less than they used to. Google's 2012 EMD update significantly reduced the ranking advantage of keyword-rich domains with weak content, and Google representatives have consistently stated in public forums that domain names are not significant direct ranking factors. Keywords can help communicate what a site does and may improve click-through rates in search results, but they should not drive naming decisions at the expense of brandability.

Should I use a hyphen to get the domain I want?

Rarely. Hyphens disappear in verbal communication because someone who hears the domain name will not know a hyphen is present. A portion of your potential visitors will consistently type the unhyphenated version, which may belong to someone else. Hyphens should be a genuine last resort rather than a first workaround.

What should I do if my preferred .com is taken?

First, determine whether the domain is actively used or merely parked. If parked, it may be acquirable since many domain investors will negotiate. If actively used by another business, consider an alternative extension appropriate for your market, look for a creative variation of the name, or find alternatives that serve the same brand purpose.

Do I need a trademark before I register a domain?

No. Domain registration and trademark registration are separate processes. But a basic trademark search should be done before you invest significantly in a domain and brand identity, because domain availability does not guarantee trademark safety.

Conclusion#

Choosing a domain name is a decision that will follow your business for years, appearing on every piece of communication you produce. It deserves a systematic process rather than whatever happened to be available the day someone remembered to check.

The twelve rules in this article are a framework, not a checklist where every box must be ticked. Real domain selection involves trade-offs. The .com you want may not be available. The perfectly short name may already be taken. The name that scores best on the framework may not be the one you are most excited about.

What the framework gives you is an understanding of the trade-offs you are making before you make them rather than after you launch. A name with a weak score on pronounceability will create exactly the pronunciation problems the framework flagged. A name with a weak score on flexibility will create exactly the rebrand pressure the framework identified. Better to know the risks going in.

A note on process: Check availability early, before you have built emotional investment in a particular name. Use a tool that lets you test many variations at once. axath is built for exactly this: checking dozens or hundreds of domain variations across multiple extensions, surfacing what is available, and helping you find alternatives before you have committed to something that is not.

The best domain is not the perfect domain. It is the domain you are still comfortable with when the business has grown past what you imagined on the day you registered it.

Bibliography#

• Alter, A. L., & Oppenheimer, D. M. (2006). Predicting short-term stock fluctuations by using processing fluency. Proceedings of the National Academy of Sciences, 103(24), 9369-9372.
• Keller, K. L., Heckler, S. E., & Houston, M. J. (1998). The effects of brand name suggestiveness on advertising recall. Journal of Marketing, 62(1), 48-57.
• Laham, S. M., Koval, P., & Alter, A. L. (2012). The name-pronunciation effect: Why people like Mr. Smith more than Mr. Colquhoun. Journal of Experimental Social Psychology, 48(3), 752-756.
• ICANN (Internet Corporation for Assigned Names and Numbers). New gTLD Program documentation. (Authoritative source for gTLD program history and extension policy.)
• Google Search Central. Public documentation and spokesperson statements on domain names and search ranking. (Google's public guidance on search; specific domain-related statements are distributed across documentation and public Q&As rather than a single dedicated page.)