Best Domain Name for a Personal Website

The best domain name for a personal website is, in our view, your full name on a .com, written the way people say it, registered in your own name and renewed for as long as you want to be found. Google's documentation says the words in a domain name have hardly any effect on ranking and that the top-level domain does not matter outside country targeting, so the decision is about being easy to type, easy to keep and hard to confuse with someone else.

A top-level domain, or TLD, is the ending of the address: .com, .name, .uk. The domain you pick will appear in citations and email signatures for years, and moving off it later has a cost, so this is a decision about ownership and durability more than search tactics.

Every statement about Google below comes from Google Search Central or Search Console help pages, and every rule about registration comes from ICANN or a registry page. Where a page does not address person sites, we say so.

The short version

Choose firstname-lastname written as one word on a .com if it is free. Google documents that domain keywords have hardly any effect and that it does not care which TLD you use.
If the exact name is taken, change something you will use everywhere (a middle initial, a profession word, a different TLD) instead of buying a near-identical copy of someone else's address.
Register the domain in your own name, with accurate contact data and an email you control. ICANN requires accurate data and an update within seven days of a change.
Turn on auto-renew, keep the payment method current and renew for several years. A lapsed domain runs through grace periods and can then be released to anyone.
If you must change domains later, use permanent server-side redirects, Google's Change of Address tool for the old domain, and keep the old domain registered for at least a year.

Best domain name for a personal website: what Google documents and what it does not

Google's SEO Starter Guide says the keywords in a domain name or URL path alone have hardly any effect on how a page ranks, and that Google Search does not care which TLD you use. The guide adds one exception: a TLD can be a minor signal when you target a specific country.

The pages we read contain no statement that a domain matching a search query, such as a person's exact name, ranks higher because of the match. We therefore do not recommend firstname-lastname.com as a ranking tactic. We recommend it as an address: it is what a person who has heard your name will type first, and it reads correctly in print.

Google's site names documentation covers the name shown for a site in results. Google generates the site name automatically from the home page and from references to the site across the web. The main way to state a preference is WebSite structured data on the home page, with your preferred name. Each domain or subdomain can have one site name, and subdirectories such as example.com/news are not supported. The page does not address person sites, so it gives no rule for personal names.

So write your name on the home page exactly as you want it displayed, with the spelling you use in bylines and profiles, and choose a domain that matches it closely.

firstname-lastname.com or .name, a country TLD, or another ending

A .com with your full name is the default, and nothing Google documents makes another ending better for ranking. Google treats any TLD that resolves through the IANA root zone as a generic TLD, unless ICANN lists it as a country-code TLD. New generic endings are therefore handled like .com, and the choice among them is about trust, memorability and cost.

Country-code TLDs, such as .uk or .de, are a different case. Google's documentation on multi-regional sites calls a country-code TLD a strong signal that a site targets that country. That suits an audience in one country and narrows a global one. The page also warns that some countries restrict who can register their country-code TLD, so check the requirements before you build on one.

Google's page lists .co, .io, .me, .tv, .ai and .fm among country-code endings it treats as generic, and says the list may change. .eu and .asia are generic regional TLDs.

The .name ending is a generic TLD operated by VeriSign, per the IANA database. VeriSign describes it as a domain for individuals who want an online identity that matches their name. Under Google's classification it carries no documented search advantage or penalty against .com.

Ending	What Google documents	Fit for a personal name	Main risk
.com	Generic TLD, no country signal	Best default: the first thing people type	Exact name often taken
.name	Generic TLD under the IANA root-zone rule	Says "personal site" plainly	Less recalled, readers may try .com first
Country code (.uk, .de)	Strong signal for that country	Good when your audience is in one country	Narrows to one country; some have eligibility rules
.me, .io, .co	Listed as treated like generic TLDs	Works if the whole address reads naturally	Google says the list may change
Other generic (.info, .dev)	Generic TLD, no country signal	Fallback when .com and .name are gone	Weaker recall and trust cues

Take the .com if it is free. If not, take the same name on .name or on the country ending that matches your audience, unless the address becomes hard to say aloud.

Hyphens, initials and middle names when the exact name is taken

Write the name as one word first (firstnamelastname.com), because a hyphen disappears when someone says the address aloud. The hyphenated form (firstname-lastname.com) is the first fallback, and it is what most people try next.

Google's URL structure guidance recommends hyphens over underscores to separate words in URLs and discourages joined words in URL paths, using greendress as its example of a join that is not recommended. That text is about URL paths, not domain names, and it does not say a hyphenated domain performs better or worse. The decision is practical: hyphens help a reader parse a long name and hurt a listener trying to type it.

Work down this order and stop at the first candidate you would be comfortable printing on a business card.

Full name, one word, .com. Best except for availability.
Full name with hyphen, .com. Fine if the joined name is ambiguous.
First initial and last name. Short, but ambiguous when spoken.
First name, middle initial, last name. The best fix for a shared name, provided you use the initial everywhere else too.
Full name plus a profession or place word. Works when the word is stable. It dates badly if you change field or move.
Full name on .name or a country ending. Keeps the exact spelling when the .com is gone.

Avoid numbers and filler words: readers get them wrong when typing from memory.

Test a candidate before you pay for it

Say it aloudRead the address to someone and ask them to type it. Every error is a visitor you lose.
Type it from memory on a phoneIf you hesitate between two spellings, so will your readers.
Search the exact stringSee what already uses it, including look-alike sites for another person with your name.
Look up the registrationUse ICANN's lookup tool to see what the public registration record shows. Most personal data is likely to be redacted.
Check the renewal priceICANN's renewal FAQ says renewal fees can be higher than first-year promotional prices, so read the renewal line, not the headline.

When the exact name is registered, the owner is a namesake using it (the next section applies), a seller who parked it, or someone whose registration may lapse. The renewal timeline below shows why waiting for a lapse is a poor plan.

Same-name collisions: when another person owns the address you want

A domain cannot make a search engine decide which of several people with the same name you are. Google's site names page says the name shown comes from the home page and from references across the web, and it gives no rule for resolving two people with one name. We therefore treat the domain as one signal among many and focus on consistency.

Consider an invented example. A consultant named Jordan Ellis finds that jordanellis.com belongs to a photographer with the same name. The consultant has two realistic options.

Add a stable differentiator. A middle initial (jordanrellis.com) works only if Jordan also publishes as Jordan R. Ellis in bylines, profiles and the home page title. A profession word works only if Jordan expects to keep the profession.
Change the ending. jordanellis.name keeps the exact spelling and signals a personal site. Readers who try .com will find the photographer, so Jordan must put the full address in every signature.

Avoid a near-copy of the namesake's address: it sends visitors to the wrong person and can look like impersonation.

Whichever form you pick, write it identically in the home page title and heading, the WebSite markup name, profiles and bylines. Consistent references are what Google's site names page lets you control: structured data, the title and the headings. Afterward, run the Page One Score to review the results for your name.

Registrant data and WHOIS privacy: whose name goes on the registration

Register the domain in your own name, or in a company you control, with an email address you read that does not depend on the domain itself. ICANN lists among registrant responsibilities taking sole responsibility for registering and using the domain, providing accurate contact information and answering registrar inquiries within fifteen days.

ICANN's page on keeping registration data accurate says registration agreements must direct registrants to give accurate and reliable contact details and to correct them within seven days of any change. A registrar may act if a registrant does not reply to an accuracy inquiry for more than fifteen days. The page states that registrars must suspend or cancel for knowingly false data, a missed update or a missed reply, while the Registrar Accreditation Agreement wording says a registrar may. Read your own registrar's terms for which applies.

The privacy question has a precise answer from ICANN's page on privacy and proxy services. In a privacy service, you remain the registered domain holder and the provider publishes alternative contact details in place of yours. In a proxy service, the provider is the registrant of record, supplies its own details, and you use the domain under a license from the provider. ICANN calls a proxy legally distinct from a privacy service. For a name site you intend to keep, a privacy service is the safer shape, because the legal holder is still you.

The GDPR has also changed what public lookups show: ICANN's page on registration data says access to most personal data was restricted, while registries and registrars must still give reasonable access to data that was previously public. Check your own record with ICANN's lookup tool after registering.

Renewal and expiry: how a name domain gets lost

A domain is rented, not bought. ICANN's renewal FAQ says the registrant is responsible for renewing, that periods typically run from one to ten years, and that auto-renewal only works if the payment method on file is current.

ICANN's Expired Registration Recovery Policy page for registrants lists what happens around a lapse in generic TLDs. Registrars must send at least two reminders, about one month and about one week before expiration, to the registrant email on file. If the domain is deleted they must send at least one more notice within five days after expiration. They may offer an auto-renew grace period of 1 to 45 days, during which the domain may be available to third parties or auctioned depending on the registrar's terms. Before deleting, registrars must disrupt DNS for up to eight days, which can take a website and email offline. Generic TLD registries must then offer a 30-day Redemption Grace Period, with a restore fee that may apply, and the FAQ says a domain not restored then spends five days in PendingDelete before it is released.

Windows around a lapse, upper boundsDays, generic TLDs, as stated by ICANN; windows may overlap and not all are additive

Auto-renew grace period (if offered)Up to 45 days

Redemption Grace Period30 days

DNS disruption before deletionUp to 8 days

PendingDelete before release5 days

Source: ICANN pages on the Expired Registration Recovery Policy and domain renewal FAQs. Country-code TLDs follow their own registry rules and may differ.

Notices go to the email on file, so a registrant email on the lapsing domain itself is a trap: if the domain stops resolving, the notices may have nowhere to arrive. Use an address elsewhere. For a country-code ending, ask the registry or registrar for its own timeline.

Google's spam policies define expired domain abuse as a lapsed domain bought and repurposed primarily to manipulate search rankings, usually with content of little or no value. Our reading is that this policy targets ranking manipulation and says nothing about returning a name to a former owner. If your name domain lapses and a stranger registers it, you are left with the new owner and the registry and registrar rules, and renewing on time avoids all of that.

Turn on auto-renew, renew for several years at once, keep a second payment method, and put the expiry date in your calendar a month ahead. This is information, not legal advice, and a dispute over a name is for your own counsel.

Changing domains later: what Google says about moving a site

Google says to expect ranking fluctuation while it recrawls after a domain change, and its site move documentation sets the sequence.

Plan first: change one thing at a time, and avoid combining a move with a redesign or a URL restructure. Prepare the new site, verify old and new in Search Console including every variant, and build a URL mapping from the old addresses to the new ones. Use server-side permanent redirects (301 or 308), go directly to the final destination and avoid chains. Do not send many old URLs to one unrelated page such as the home page. Google lists client-side redirects as a last resort, and its redirect documentation says JavaScript redirects depend on rendering that can fail. Then submit Change of Address in Search Console for every verified variant of the old domain, including www and non-www, even variants you do not actively use. Google's Change of Address page adds that the tool works only at domain level, does not move subdomains below the domain, and that you should not chain moves (A to B, then B to C) right away.

On permanent redirects, the documentation says not to worry about link credit. For medium-sized sites the switch can take a few weeks or more; the page gives no figure for a small personal site.

The two Google pages state different durations, and you should follow the longer one. The site move page says to keep redirects generally for at least a year. The Change of Address page says its effects continue for 180 days, after which Google no longer recognizes a relationship between the old and new sites. It asks you to keep redirects at least 180 days, longer if traffic still arrives, and to keep paying for the old domain at least a year so that others cannot buy and misuse it.

Stage	What happens	Figure from Google
Before	Verify both domains, map URLs, prepare redirects	No fixed time
Move day	Redirects live, Change of Address submitted for each old variant	Same day
Weeks after	Google recrawls; rankings fluctuate while new URLs replace old	A few weeks or more for medium sites
Day 180	Change of Address period ends; Google no longer treats the sites as related	180 days
Year one	Keep redirects and keep the old domain registered	At least one year

The redirect only works while you still own the old domain, so if you change your name, move to a new domain but keep paying for the old one. If you buy a domain that someone else used before, Google's move documentation says to check it for leftover manual actions and URL removals before you build on it.

Root domain or subdomain: where the name site should live

Put the site at the root of a domain you own: yourname.com, not a subdomain of something else. Google's SEO Starter Guide gives no general rule between subdomains and subdirectories. It says subdirectories can be easier to manage and subdomains may suit certain topics or industries, so the choice follows your situation. For a person, the situation points one way.

Root of your own name domain. Full control and one site name. The right default.
Subdirectory on the same domain (yourname.com/blog). Easier to manage, and every page stays under one site name.
Subdomain of your own domain (blog.yourname.com). Acceptable when a separate system hosts it. Google's site names page says each domain or subdomain can have its own name, and a subdomain without its own markup may fall back to the domain-level name. Change of Address does not move subdomains below the specified domain, so a subdomain is a second property to maintain.
Subdomain of an employer, platform or school (you.employer.com). You do not control it, and it can disappear when the relationship ends. Treat it as a profile, not your main address.

The same principle applies to the www question. Google's duplicate URL documentation says to indicate one preferred version, with redirects or rel=canonical, and lists redirects first among its signals. Its site names page treats www as equivalent to the bare domain. Choose one, redirect the other, and set the same structured data on both so the home page signals agree.

If you register several versions of your name to protect it, such as the .net or a hyphenated form, point them all at the main domain with permanent redirects. Do not publish separate sites on them. Google's spam policies list, under doorway abuse, multiple domain names or pages targeted at specific regions or cities that funnel users to one page. That wording is about regional targeting, and in our reading a redirect from a defensive registration is not what it describes, but a set of near-duplicate sites adds nothing and is the pattern to avoid. For help building the page that your domain should point to, see our personal brand service.

Your next step: pick, register and protect the name this week

Decide the exact string with the candidate test, register it with a registrar whose renewal prices you have read, and list yourself as the registrant. Turn on auto-renew, then put the same name on the home page, in the WebSite markup and in your profiles. Reputation Partners advises clients whose name is shared or already crowded with unwanted results.

If this is happening to you now

If your exact name is taken by someone else, or results about a namesake already fill page one, choosing a domain is only the first step. A private audit shows what searchers and AI assistants find today and which assets should carry your name. Start with the private audit.

Questions people ask

Should I register my name before I need a website?

Yes, if the exact name is free and the fee is small, because waiting risks someone else taking it. Follow the registrant, contact and renewal rules above, point the domain at a profile in the meantime, and keep the renewal date in your calendar.

Do I need to buy every version of my name?

No. Buy the main domain and the one or two variants people are most likely to mistype, such as the hyphenated form. Point extras at the main domain with permanent redirects. Each extra name adds a renewal to track, and a lapse on a variant is a free address for someone else.

What if the owner of my exact name is not using it?

Look up the registration with ICANN's lookup tool to see what the public record shows. Personal details are often redacted, so you may have to reach the owner through whatever contact route the record or registrar provides. The price may rise if the owner learns the name matters to you. Do not buy a near-copy that could mislead visitors.

I changed my name. Should I move my domain?

Usually yes, if the old name is what people will no longer search. Register the new name, move the site with permanent redirects, submit Change of Address for the old domain and keep the old domain registered for at least a year. Google says not to chain a second move onto the first right away.

Is it risky to buy a domain someone used before?

It can be. Google's site move documentation says to check a bought domain for leftover manual actions and URL removals. Its spam policies also describe expired domain abuse, which is about repurposing domains to manipulate rankings. Look at the domain's past content in an archive before you build on it, and do not reuse its old pages.