New site owners often struggle to find a domain name that is both descriptive enough for search visibility and short enough to be memorable. This article outlines how to prepare candidate names, verify their status, and choose the right structure before registration.

Imagine a first-time site owner, a freelance furniture restorer, sitting down with a notebook before registering anything. She jots three working identifiers: OakAndAwl, QuietGrain, and RestoreNorth. Each one is her own shorthand recorded on paper; nothing about spelling or availability has been checked in any registry. OakAndAwl leans on a craft keyword pair, QuietGrain trades search terms for a softer image, and RestoreNorth pairs an action word with a direction she associates with her workshop.

To compare them, she fills a three-row worksheet with four columns: identifier, keyword match, spoken-once test, and intended use. She scores the spoken-once test by reading each name aloud to a friend and noting whether it is typed back correctly. Her fictional entries look like this: OakAndAwl, high keyword match, misspelled once out of two attempts, planned for the main site; QuietGrain, low keyword match, spelled correctly both times, reserved for a future journal; RestoreNorth, medium match, spelled correctly once, kept as a fallback. These are her own notes, not survey results or feedback from real visitors.

The trade-off becomes concrete in her first decision. She picks OakAndAwl for the main site because a visitor searching for furniture restoration is likelier to recognize the words in a link preview, and she accepts the spelling risk by planning to say the name slowly in her introduction text. She sets QuietGrain aside precisely because it is easy to say but says little about what she does. If she later changes her mind, she writes down the reason in the same row rather than erasing the earlier note, so the record shows why the choice shifted.

The worksheet also carries two checks she can do without any outside service: write the name in lowercase and in capitals to see whether letter shapes blur together, and type it into a plain text file to catch doubled letters or awkward joins. When she reaches the point of picking a suffix, she treats it as a separate column with its own note, such as ".studio for a portfolio feel" or ".com for habit", and marks which one she would say aloud in conversation. Nothing here has been registered or tested, so the page stays a planning sheet rather than a result.

Structuring Domain Components: SLD and TLD

The cited official guide defines a complete domain as two parts: the prefix, or SLD, which is the part you customize, and the suffix, or TLD, such as .com, .net, .org, or .co. It supports hundreds of TLDs across generic, country-code, and new categories.1

Before registering, the guide advises choosing a name that is concise, easy to remember, and related to the brand, and preparing two or three alternatives. It describes .com as the most general choice, with .net, .co, or industry-specific suffixes as possibilities if .com is taken. The guide also notes that certain country-code domains may have special registration requirements and directs readers to the prompts on its search page before registering.1

You can start by splitting a candidate into its second-level label and its top-level suffix, then judging each half separately before you commit. Take the sample name OakAndAwl: the label is the part you can invent, and the suffix is the part you mostly select from what is offered. Write them as two separate lines in your notes so you stop treating the whole string as one creative decision. For each line, record what you intend it to do. On the label line, your own words can note the keyword you are reaching for, such as furniture restoration, alongside a shorter spoken form a person could repeat after hearing it once. On the suffix line, note the impression you want a first-time visitor to carry away, such as a general-purpose or a country-specific feel, phrased in your own terms rather than as a claim about any registry.

Then you might try a small comparison rather than a single verdict. Write two versions of the same label, one with the keyword spelled out and one trimmed to the memorable core, and read each aloud next to the suffix you are weighing. A filled row could look like this: label "oakandawl," keyword "furniture repair," spoken-once result "clear on first hearing," preferred suffix "the general one," intended use "main site." A second row might carry the trimmed label and a note like "quicker to say, weaker keyword." Those fields are ones you can fill for yourself; they are not a form anyone else supplies.

You can also keep one worksheet column for the impression each suffix gives you when you say it after the label, and another for the keyword load you are willing to lose if it comes to that. When the two lines of your notes start to point in different directions, that is a useful signal that you are choosing between a description and a sound, not between two equally weighted names. The decision remains yours, and the notes simply let you see which half you are actually favoring.

Preparing Candidate Names and Backup Options

Set aside one evening to build a candidate sheet before you register anything, and treat it as a working document rather than a final answer. Open with three columns you can fill by hand: the label you are considering, what keyword or phrase it carries, and the impression you want a first-time visitor to take away. A furniture restorer, for example, might write down oakandawl, restoredoak, and awlandgrain, then note under each whether the keyword is obvious or only implied. You can choose to add a fourth column for a plain-language sentence you would say aloud when introducing the site, such as "I repair and refinish wooden furniture." Reading that sentence back helps you notice whether the label alone carries enough meaning or leans on the suffix to finish the job.

Once the rows exist, prepare at least two backups for every favorite rather than one. A useful habit is to vary one thing at a time: keep the same label and change the suffix, or keep the suffix and shorten the label. The restorer might list oakandawl with a country suffix, oakandawl with a generic suffix, and a trimmed awlworks with the same generic suffix, so she can see which change does the most work. You might mark one candidate as first choice, one as the fallback if the first is unavailable, and one as a longer-term alternative you would only use for a side project.

The backup sheet earns its keep when you write a short reason beside each row. Rather than a score, note the trade-off in plain words: "reads clearly when spoken, but the keyword is weak" or "keyword is strong, but I would have to spell it every time." These notes let you revisit the list a day later with fresh eyes and spot which candidates you keep defending out of habit. You can also set a simple personal rule in advance, such as preferring a label you can say once without correction, and note where each candidate breaks that rule.

Leave the finished sheet somewhere you will see it before you commit, and add new candidates as they occur to you. The goal is a small, reasoned set of options you can compare calmly, not a single name you feel forced to accept.

Balancing Keyword Relevance With Memorability

Use NamesLink 's homepage search box to enter your candidate name and compare the registration status shown for each available suffix, which helps you judge whether a keyword-based choice still leaves a memorable form. Prepare two or three backup options before searching, and if your first pick is taken, review the similar available names the results suggest. To manually verify the details, check the status labels and, for a name already registered, the Whois information before deciding.1

Verifying Availability Through Registrar Queries

According to the cited official guide, availability checking begins on the registrar's home page: you enter the desired domain name in the search box, using an example such as “mybrand.” The page then reports the registration status for that name across suffixes, distinguishing domains that are available to register immediately from those already registered by another party. For a registered name, the guide says you can look up the Whois information or try to contact the holder to buy it. It further states that when the preferred domain is taken, similar registrable domains are suggested, and it notes that certain country-code domains may carry special registration requirements that should be checked in the prompts on the query page before proceeding.1

Take your shortlist and, before you act on it, open the query page for the suffix you are considering and type each candidate label exactly as you would register it. You can start with the one candidate you like most and work down the list, entering the full name each time rather than a shortened form. A query that returns a clear available or taken result tells you whether that row of your worksheet moves forward; a query that returns nothing conclusive tells you to set that row aside rather than assume either outcome. If you are weighing two suffixes for the same label, run the query separately for each, since the same word can give different answers under different endings.

When a result comes back, record it next to the candidate in your own notes rather than relying on memory. A simple line works: the label as typed, the suffix queried, the date, and whether the answer was available, taken, or unclear. Keeping the exact spelling you entered matters, because a hyphen, a doubled letter, or a plural you might later drop is a different query. If you plan to check several names over more than one sitting, the dated record lets you see which results are still fresh and which you should re-run before deciding.

Consider treating the query step as a filter rather than a verdict. You might keep a taken result on the sheet if the name is one you would genuinely pursue through a secondary market, and mark it as such in plain words. You can also note, beside any available result, whether it was the label or the suffix you cared about more, so that the final choice still follows your own reasoning rather than the first green answer you saw. Prepare to re-query your top two or three choices once more before you register, and let that last pass confirm the set you carry forward.

Finalizing Registration Details and Privacy Settings

When buying, the cited official guide shows a registration-term choice from one to ten years. It also describes a holder information template: if no contact template is selected, the default template generated from account information is used, and you can add templates and change the default.1

The guide states that ICANN requires accurate registration information, including holder name or organization, email address, phone number, and full address with country, region, city, street, and postal code. It adds that domain privacy protection is switched on automatically to hide personal information in Whois.1

Open your registration notes at the row for the label you have finally chosen, and add two plain lines beneath it: who will be able to look up the registrant, and what you will write in the note field. You can decide these before any form asks, so the choices come from you rather than from the default already filled in.

For the first line, you might write "public contact" beside a working identifier, then add a second row marked "privacy service" with the same label. Under each, note in your own words what a visitor would see if they looked up the name: a name and address, or a substitute contact. A third row could read "public contact, separate role address," which is a condition example rather than a change to your earlier shortlist rather than a new channel. Keep the three rows as comparisons, and mark the one you are most comfortable with.

For the second line, sketch the note text you would type: "furniture restoration studio, site launch planned." Read it aloud once. If your chosen label appears differently in capitals, adjust the note to match how you would say it, then keep both versions on the page.

Consider also recording the renewal anniversary in the same notes, written as a month and day you will remember, and whether you want the registration to renew automatically. Neither answer is permanent; you can revisit them after the site is live.

Before you submit, set the page beside your shortlist and check that the label on the registration row matches the one you judged, letter for letter. If a backup label took its place, update the note and the anniversary line so the sheet and the registration tell the same story.

Frequently asked questions

What columns should I fill by hand on my candidate sheet?

Set aside one evening to build a candidate sheet before you register anything, and treat it as a working document rather than a final answer. Open with three columns you can fill by hand: the label you are considering, what keyword or phrase it carries, and the impression you want a first-time visitor to take away.

How can I build backups for my favorite name candidates?

Once the rows exist, prepare at least two backups for every favorite rather than one. A useful habit is to vary one thing at a time: keep the same label and change the suffix, or keep the suffix and shorten the label.

What should I write beside each row on my backup sheet?

The backup sheet earns its keep when you write a short reason beside each row. Rather than a score, note the trade-off in plain words: "reads clearly when spoken, but the keyword is weak" or "keyword is strong, but I would have to spell it every time."