How to choose a domain name for a blog

First, decide who the reputation belongs to

Everything else follows from this, and it is worth answering before you look at a single domain. Readers will end up following one of three things.

The personal-name route is undervalued for writing specifically. A person's name has infinite semantic room — you can write about anything without the domain contradicting you — and the reputation compounds across every subject you ever cover. Its real cost is not vanity but transferability: a publication named after you is difficult to sell, hand over, or grow into a team without a rebrand.

The publication route is the one to choose if you can already imagine a second writer. Doing it later is a migration.

Choose a scope you can live inside

If you go with a topic, the deciding question is how far the name lets you drift. Not how well it describes your current plan — how much room it leaves.

A useful exercise: list the ten articles you are certain you will write, then list five you might write in two years if your interests move the way they usually do. Read the domain against all fifteen. The names that fail this fail on the last five, and those are the ones that actually determine whether you keep writing.

Names anchored to a subject one level up from your specific interest tend to survive best. A blog about a particular framework becomes wrong when the framework does; a blog about the craft of building things with frameworks does not.

Keywords belong in the titles, not the domain

This is the single most common blog-naming mistake, and it comes from a real observation applied in the wrong place. Search traffic does depend heavily on matching what people are looking for — in the article titles, the headings and the content, all of which you can change.

The domain is the one part you cannot change without a migration. Putting a fast-moving keyword there fixes today's positioning into a permanent asset, and it buys you very little: a keyword in a domain gives a human reader instant context and does not carry a site that lacks good writing. Does your domain name affect SEO covers what it does and does not do.

There is also a compounding argument on the other side. A distinctive publication name eventually gets searched for by name, and nobody else can rank for it. A generic topic domain competes forever with everyone who chose the same words.

Make the recommendation easy

Blogs spread through a specific action: somebody who read something useful tells somebody else. That happens in messages, in conversations, and in a sentence at the end of a meeting — 'there is a good piece about this on ___'.

So the address has to survive being said. Read the whole thing aloud, hyphens and all, and have somebody type it. Anything you need to spell out will not be recommended verbally at all; the recommender will say 'I'll send you a link', and half the time they will forget.

This is why hyphens hurt blogs more than they hurt companies. A business gets typed from a card or a search; a blog gets typed from something somebody said.

Check where the blog is likely to go next

Blogs rarely stay only blogs. They become newsletters, then podcasts, then occasionally communities or products, and each of those wants the same name in a different place.

Before registering, check the name as a newsletter title, as a podcast title in a directory, and as a handle on the platforms you would plausibly use. You are not committing to any of that — you are finding out now whether the name has room, which costs ten minutes and saves a rename.

Search publication platforms specifically. A great many newsletters and blogs live on hosted platforms and never appear in a domain search at all, so a name that looks unclaimed can already have an audience attached to it.

Avoid the dated-trend trap

Trends make excellent article subjects and terrible domains. The technology in the name, the year in the name, the fashionable framing of a subject — all of them attract attention now and become a liability on a schedule.

The test is to read the domain as if it were five years old. If it sounds like it is about something people used to care about, that is exactly what it will sound like, because it will be.

Research before you publish, not after

A media brand can conflict with an existing publication or business, and blogs are especially prone to this because so many exist under names nobody registered anywhere.

Search the exact name and near-spellings, then search it alongside your subject, then check the trademark registers for the markets you write for. An existing publication in your own subject area is a practical problem regardless of the legal position — your readers will find them, and cite them, when they meant you. How to check whether a name is already in use covers the searches.

Then imagine the thousandth article

The last test, and the one that matters most. Not whether the name suits the piece you are about to publish — whether it suits the body of work you want to have.

A blog is a long project, and its name gets read tens of thousands of times by people deciding whether to trust what is under it. Choose for the archive rather than for the launch.