Choosing a domain name involves balancing creativity with technical constraints. This article outlines how to generate candidate names that are easy to remember and then use a registrar's search tool to check if they are available for registration.
Defining the Scope of Personal Blog Naming
Here is a hypothetical scenario. A writer planning a small personal blog about urban gardening sits down with a notebook, a short list of words she likes, and a blank table for checking names later. She decides the scope first: the name must be easy to say aloud, short enough to fit on a card, and flexible enough to survive a change of topic. She rules out anything tied too tightly to one city or one plant.
Working only from her own notes, she drafts three candidates. The first is “balconyplot,” a plain compound describing small-space growing. The second is “seedledger,” which pairs a gardening word with a record-keeping word, echoing her plan to post weekly notes. The third is “quietgrow,” a softer option meant to signal a low-pressure, reflective tone. She writes each one twice, once capitalized and once lowercase, to see which reads cleanly at a glance. She notes that spelling is her own record for now, not a claim about what any search field will accept.
To compare them, she builds a small table with four columns: candidate, intended topic, spoken test, and earliest post idea. Two invented rows show how it works. Under “balconyplot” she writes topic “container herbs,” spoken test “said it to a friend without spelling it,” and first post “three pots on a north-facing ledge.” Under “seedledger” she writes topic “weekly growing log,” spoken test “needed one repetition,” and first post “what I planted in week one.” The table is her own working aid, not a record of anyone’s feedback.
She makes one concrete trade-off. She sets aside “quietgrow” for now. Her reason is specific: the word “quiet” suggests stillness, but her planned posts are mostly about active small experiments, and she worries the name would set the wrong expectation before a reader sees a single entry. She keeps “balconyplot” and “seedledger” as the two she will examine further.
She also decides what is out of scope for this stage. She will not yet think about how a name maps to a web address, what a renewal might cost, or how traffic is directed; those belong to later sections. For now she only wants names that pass the spoken test and match a plausible first post, so the naming work stays separate from the setup work.
For the link she will share with a friend, she fixes a simple plan rather than assuming a recipient: a message-based link goes only to the person she names in her contacts, and a public post link goes to the profile she controls. That keeps the example honest about where each link leads.
Generating Candidate Names Based on Content Themes
You can start by turning your own planned posts into a short list of words worth trying. Read the last three or four drafts you have written, or the notes for pieces you are preparing, and copy out only the nouns and verbs that keep recurring. For the urban gardening example, that might produce balcony, plot, seed, light, water, soil, and grow. Keep the list in your notebook rather than reaching for a generator; the point is to work from your material, not from someone else’s word bank.
Once the list is on the page, you might combine pairs and read each result aloud. A tentative pair such as “seed light” can be turned into “seedlight” for a spoken test, and “balcony plot” into “balconyplot.” Say each one twice, once as if introducing yourself and once as if telling a friend where to find your writing. You can mark the ones you stumble over and set them aside without deciding they are bad. The test is only about whether the name survives being spoken.
It helps to keep a record of where each candidate came from. You could add a column for the draft or theme that suggested it and a column for the kind of post you would publish first. That way, if a name later feels too narrow, you can see whether the narrowness came from the words or from the themes you happened to list. A name built from “balcony” may still work if your notes show you writing about windowsills and shared courtyards; the record gives you a reason to reconsider rather than guess.
You can also try a short written exercise: describe your project in one sentence without using its working title. Then underline the two words in that sentence that feel most like your own. Use those as a fresh pair before returning to the earlier combinations. This is a way of checking that your candidate names still match the writing you actually want to do, not just the first idea you had.
Applying Memorability Criteria to Shortlist Options
Take your shortlist of candidate names to NamesLink and enter each one in the search box on the homepage; the results show whether the name is available or already registered under each TLD, and if a preferred name is taken, similar available alternatives are suggested. To check manually, compare those results against the memorability criteria you set before searching.1
Using Registrar Search Tools to Check Availability
According to the cited official guide, you begin by going to the service's home page and typing the desired domain name, such as mybrand, into the search box. The results then show the registration status for that name across its various suffixes.1
The guide states that a registrable status means the domain has not yet been registered and can be purchased right away. A registered status means another party holds it, in which case the guide says you can view Whois information or try to contact the holder about a purchase.1
The same guide adds that when a preferred domain is already registered, the service will suggest similar registrable domains as alternatives. Its stated preliminary advice is to decide on the name and prepare two to three backup options, and to confirm which suffix you want, since if the .com is taken you may consider .net, .co, or an industry-specific suffix such as .tech or .app.1
Take the shortlist you have already assembled and prepare it for the availability check without pressing anything yet. You can begin by marking which candidates are exact compounds, like the earlier “seedlight,” and which are two words you might accept with a hyphen. For each row, note the variation you are willing to ask about, so the check becomes a comparison rather than a string of guesses.
A simple record might use these fields: candidate, plain or hyphenated, reason it fits your posts, and what you would do if that form is taken. A filled example could read: “seedlight — plain — describes light on seedlings — keep as first choice.” Another row might read: “quiet-grow — hyphenated — softer sound — accept only if the plain form is unavailable.” You can fill your own rows before checking, and leave the result column empty for now.
When you do open a registrar search, consider checking one candidate at a time and writing down exactly what the result says: available, taken, or requiring a different spelling. You might then add a second field for your own next action, such as “hold this row” or “set aside for now,” so the record shows your decision rather than only the lookup outcome.
Interpreting Registration Status Results
When a registrar search displays results, the cited official guide describes the output in terms of registration status. The results page shows which suffixes are available or already registered. For an available name, the guide says the result indicates that the domain has not been registered and can be purchased immediately; for a registered name, it indicates that the domain is held by someone else, and the guide notes that you can look at Whois information or try to contact the holder about a purchase. The guide also states that if a preferred name is registered, the search can suggest similar registrable names. Separately, it cautions that certain country-code domains may have special registration requirements, so the prompts on the search page should be checked before registering.1
When a search shows a result other than a plain available or taken, you can decide in advance how much weight to give it. Consider keeping a short column for the exact wording of each result and a note on whether it changes your ranking. A candidate marked as requiring a different form, or as already in use, might still suit you if a close variant reads well aloud; the point is to record your own reading rather than guess at meaning.
For the gardening writer's shortlist, you might set beside each name the outcome you would accept. “balconyplot” taken as a plain form: keep “balconyplots” if it still fits on a card. “seedletter” shown as unavailable: return to her notes and try “seednote” before moving on. These are her choices to make, not fixed rules.
You can also separate what the result tells you from what you still need to confirm later. If a status seems ambiguous, note the wording and set the candidate aside for a second visit rather than treating it as a verdict. Your record then shows which names survived on their own merits and which are waiting on a clearer answer.
Finalizing the Selection Before Purchase
Take your own shortlist and add one final column before you look anything up: a written reason for keeping or dropping each name. For the gardening writer, that column might read “balconyplot — keep, because it describes small-space growing and I can still write about containers or windowsills,” while “cityherbs — drop, because it pins the blog to one place and one kind of plant.” Reading her reasons side by side gives her a decision she can explain later, rather than a hunch she forgets by the time she sits down to search.
You might also write a one-sentence test for each finalist, as if introducing the blog to a friend. “I write about growing food on small balconies” fits “balconyplot” without strain; the same sentence feels narrower next to a name that promises a whole garden. If a candidate needs two sentences of explanation, consider setting it aside for now and noting why. You can change your mind later, but the note keeps the trade-off visible.
Before any search, you can fill in a small comparison sheet with the fields you will actually use. A hypothetical filled row might read: candidate “balconyplot”; plain or hyphenated, plain; reason it fits, matches the balcony theme; if taken, consider “balconyplots” only if it still reads naturally aloud. A second row for “seedlight” could say: reason it fits, links seedlings with writing; if taken, put it back on the maybe list rather than forcing a longer form. Filling these rows first lets you compare results against a plan instead of deciding under pressure.
When you do open a search page, treat each result as information to record rather than a verdict. You can note the exact wording beside each candidate, then ask yourself whether an unclear status is worth resolving now or whether this name simply moves to the rejected column. The gardening writer might decide that a taken plain form is acceptable only if her fallback still passes the spoken test, and she would write that condition down before searching, not after.
The last step belongs to you alone: choose the candidate whose written reason you can still stand behind tomorrow. Keep the sheet with your notes, because it records what you valued at this stage and gives you a fair basis for revisiting the choice if your plans shift.
Frequently asked questions
How can I turn my own planned posts into a short list of words worth trying?
You can start by turning your own planned posts into a short list of words worth trying. Read the last three or four drafts you have written, or the notes for pieces you are preparing, and copy out only the nouns and verbs that keep recurring.
How can I keep a record of where each candidate came from?
It helps to keep a record of where each candidate came from. You could add a column for the draft or theme that suggested it and a column for the kind of post you would publish first.
What field could I add to my own shortlist before I look anything up?
Take your own shortlist and add one final column before you look anything up: a written reason for keeping or dropping each name. For the gardening writer, that column might read “balconyplot — keep, because it describes small-space growing and I can still write about containers or windowsills,” while “cityherbs — drop, because it pins the blog to one place and one kind of plant.”