Starting a personal blog or small project often begins with choosing a name that reflects your core topic. This guide helps you generate concise, memorable candidates based on your key themes and shows you how to check if they are available for registration.
Brainstorming Keywords for Your Project Identity
Imagine a hypothetical author planning a small personal blog about repairing old mechanical keyboards, someone with a notebook of parts lists, a folder of photos, and a draft about stabilizer rattle. Her working list starts with what the project actually contains rather than with suffixes: repair, bench, switch, keycap, solder, desk, clack, rebuild. She groups these into nouns she wants searched for (keyboard, switch, solder), words that describe her angle (repair, bench, patient), and sound words that are memorable but vague (clack, tick). The vague group goes to the bottom of the list, because a reader who hears the name once should be able to guess the topic.
For a test entry, suppose she drafts three candidate names in her notebook: fixclack, benchswitch, and solderdesk. Each is two short words joined without a hyphen, easy to say aloud, and short enough to fit a masthead. She is not claiming any of these are available or registered; they are simply examples she writes down to compare shapes. Her own spelling notes say she prefers the “clack” family for a playful tone and the “bench” family for a quieter, workshop tone. That is a stated preference, not a verdict about which name performs better.
Then she turns the list into a small table she can fill in, with columns she can actually use: Candidate, Core keyword, Tone, Syllables, Spoken once. Two invented rows show how it works. The first row reads benchswitch, keyword switch, tone calm, two syllables, spoken once as “bench switch.” The second reads fixclack, keyword clack, tone playful, two syllables, spoken once as “fix clack.” If she later adds a form field for spelling back what a friend heard, she would record the result there rather than guessing it now.
The decision she makes from this table is a single tradeoff: she keeps benchswitch and drops fixclack, because “bench” matches the workbench photos already filling her drafts, while “clack” could describe any noisy object. The rejected name stays in the notebook as a fallback for a different, sound-focused section. Nothing here shows that a name is free to register or that readers will remember it; these are her own examples for taming a keyword list into a few testable candidates before any availability check.
Generating Short and Memorable Name Candidates
You can take your existing keyword notes and turn them into a short list of memorable name candidates without committing to any name yet. This step is only generation, so you might let yourself write more options than you expect to keep.
A simple method is to collect the words you already use for your project. For the mechanical keyboard blog example, those notes might include "switch," "keys," "bench," and "repair." You can write each core word on its own line, then combine pairs. Some candidates are transparent compounds such as "switchbench" or "keyrepair." Others are shorter blends such as "swibench" or "keyfix." Neither approach is inherently better at this stage; you can generate both kinds and choose later.
You might also use a small set of optional patterns to widen the list. One pattern is keyword plus a plain noun: "benchnotes" or "switchlog." Another is a verb-like first part with a concrete second part: "fixkeys" or "patchbench." A third is a slight shortening that remains easy to say: "keybench" instead of "keyboardbench." You can pick two or three patterns that fit your topic and leave the rest out, rather than trying to use every pattern. A personal notes blog may benefit from a quieter word such as "notes" or "log," while a small project page might prefer a more active word such as "build" or "launch."
Once you have perhaps ten or fifteen candidates, you can make a short comparison table in your own notes. Useful fields are Candidate, Core keyword, Spoken once, Sounds like two common words, and Short enough for a social handle. For example, a row might read: "benchswitch," "switch," "easy," "yes," "yes." A second row might read: "fixclack," "repair," "easy," "no," "yes." These are illustrative values, not test results, so you can write your own impressions and reconsider them after a day.
You can then choose a shortlist of three or four names. One useful test is whether a name still makes sense to you after you say it aloud without context, and whether you can spell it after hearing it once. You might discard a name that needs a spoken explanation or that sounds like an unrelated common word. As you compare, keep in mind whether you would be comfortable using the name for a small site over time, and whether the same keyword still matters if the blog or project expands. You can also note which candidates would be easier to pair with a simple site title, but the final choice remains yours.
When the shortlist is ready, stop generating new names for the moment. Keep the table and the shortlist together, because the next step is to compare those few candidates and decide which ones you want to check further. That way, the brainstorming stays a deliberate choice rather than a search for a perfect name.
Selecting the Right Top-Level Domain Suffix
To check availability of a short, memorable name for your blog or small project, go to the NamesLink homepage and enter the name in the search box, then review the registration status shown for each suffix. Prepare 2–3 backup name options and confirm the suffix type by comparing the general, country-code, and new top-level domains listed in the results; if a preferred name is registered, check whether the system suggests similar available names. For a manual double-check, review the status shown for each suffix in the results before deciding to register.1
Checking Availability Through Registrar Search Tools
According to the cited official guide, the first step is to open the provider's homepage and enter the desired domain name, such as "mybrand," in the search box. The system then displays the registration status for each suffix under that name, showing either that a name is available for registration or that it is already registered by someone else. The guide also suggests preparing two to three backup candidates in advance, along with the desired suffix type, and states that some country-code domains may carry special registration requirements that should be reviewed on the query page.1
For the three or four names on your shortlist, you can turn to a registrar search box and enter one candidate at a time, without hyphens or spaces, just as you would say it aloud. Keep your notebook table beside you so you can record what the search returns for each candidate: exact match, a near variant only, or nothing close. A name that appears only as a longer variant, such as an added word or a different spelling, is a different choice than an exact match, so you might note which one you actually saw rather than a general "seems fine."
If your shortlist came from the mechanical keyboard example, you might keep benchswitch and solderdesk in the table and add two columns: exact match seen, and closest variant seen. For benchswitch the entry might read exact match seen: yes; closest variant: benchswitchblog. For solderdesk it might read exact match seen: no; closest variant: solderingdesk. Those filled values are only a record of what the search page displayed, not a decision. You can leave a candidate in the running even when only a variant appears, as long as you note that you are choosing the variant spelling rather than the original.
You can also decide in advance what you will do with the results before you start searching, so the moment does not push you toward a rushed choice. One option is to keep names with exact matches and variants together on a second shortlist, then reread them aloud before narrowing further. Another is to set aside any candidate that shows only an unrelated match, so the next step focuses on names where a reasonable path exists. Both are yours to choose, and you can change the rule after the first search if it no longer fits what you see.
Interpreting Registration Status Results
After the search, the cited official guide says the system displays the registration status for that name across suffixes. It defines two results: “可注册” (registrable) means the domain has not been registered and can be purchased immediately, while “已注册” (registered) means it is held by someone else, and you can view Whois information or try to contact the holder about buying it.1
Each status applies only to the specific name and suffix shown in those results, so read the outcome per candidate rather than treating one result as covering the whole shortlist. The guide also notes that when the preferred domain is already registered, the service recommends similar registrable domains to choose from. Treat those suggestions as separate names requiring their own status check.1
For each shortlisted candidate, you can note the result in plain words before moving on: available, taken with a similar variant, or held for a different purpose. Keep the note beside the name itself rather than in a separate list, so your earlier table stays the single record of what you generated and what you found.
A small status record might use fields like Candidate, Result seen, Closest variant, and What I would use it for. For benchswitch, an example entry could read: Result seen — taken; Closest variant — benchswitchlog; Intended use — main blog name. For solderdesk, a different entry might read: Result seen — available at first look; Closest variant — none needed; Intended use — reserve as a backup. You can fill these values with your own observations, and the choice of how much to write in each cell remains yours.
It helps to distinguish between a result that rules a name out for the address and a result that merely makes it less attractive. A taken exact match may still leave a variant that sounds like your project, while an available name that is hard to say may fail the spoken test you applied earlier. You might mark each shortlisted name as keep, replace, or hold, and write one short reason in your own words.
When you revisit the table, compare the marked names against your original tone notes. If a variant has drifted away from the core keyword you started with, you can either accept the drift deliberately or return to your generated list for a closer option. Recording that decision in the same table keeps the next comparison grounded in what you actually saw, rather than in a name you have grown attached to.
Preparing Alternative Names When First Choices Are Taken
Take your shortlist of three or four saved candidates and prepare a second, smaller page in the same notebook for fallback versions. For each original name, you can write two or three intended variants before you search for any of them: one with a different ending, one built from a different core keyword in your notes, and one shorter spoken form. For the keyboard example, benchswitch might yield benchswitchlog, keyswitchbench, and just bench. The point is only to have these written down in advance, so a taken result does not push you into inventing something on the spot.
You can label each variant with the reason you would accept it. Useful fields are Original candidate, Variant, Which keyword it keeps, and Why I would settle for it. A filled example might read: Original candidate benchswitch; Variant keyswitchbench; Keyword kept switch; Reason keeps the repair focus but reorders the words, still easy to say. Another might read: Original candidate solderdesk; Variant solderbench; Keyword kept solder; Reason closer to the workbench photos, though less tied to a desk. You might fill four or five of these rows and leave the rest blank until you need them.
When you return to your stored comparison table, mark which fallbacks you would genuinely be willing to use as the main name, and which you would only keep as a spare written option. Consider whether a variant still matches the tone note you wrote earlier, and whether it has drifted toward a word you did not originally care about. If a fallback no longer reflects your core keyword, you can cross it out rather than carry it forward.
It also helps to note, beside each fallback, what you would do if it too turns out to be taken. You might decide in advance that you will move to the next core keyword in your notes rather than keep adding endings to the same word. That way the fallback page stays short and readable instead of growing into another long list.
Frequently asked questions
What should I do with the project-related words I have already been collecting?
A simple method is to collect the words you already use for your project. For the mechanical keyboard blog example, those notes might include "switch," "keys," "bench," and "repair."
After I have ten or fifteen candidates, what comparison table can I make in my own notes?
Once you have perhaps ten or fifteen candidates, you can make a short comparison table in your own notes. Useful fields are Candidate, Core keyword, Spoken once, Sounds like two common words, and Short enough for a social handle.
What can I write beside each fallback to decide in advance what I will do if it is also taken?
It also helps to note, beside each fallback, what you would do if it too turns out to be taken. You might decide in advance that you will move to the next core keyword in your notes rather than keep adding endings to the same word.
域名注册入门指南 | NamesLink . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎ ↩︎