What a personal website is actually for

Most advice about personal websites starts with instructions and never gets to the question that actually matters. Here is how to pick a domain. Here is how to write an About page. Here is a checklist of sections to include. All of it assumes the answer to "why would anyone open this" and skips straight to construction, which is how you end up with a beautifully built page that nobody has a reason to visit twice.

So start with the question instead. A personal website has exactly three jobs. It is the thing that shows up when someone searches your name. It explains, in about the time it takes to read one screen, what you do and who that's useful for. And it gives one obvious, working way to get in touch. That's the whole list. Everything else — the blog nobody updates after March, the testimonials carousel, the "my journey" timeline with a photo from every job you've had — is procrastination dressed as content strategy, and it is usually the reason the site never ships.

The three jobs, and why they're the only three

Take them one at a time, because each one rules out a different set of features people assume belong on a personal site.

Ranking for your name is a search-engine problem before it is a design problem. If someone types your name into a search box — a recruiter after a phone screen, a client who was handed your card, an editor checking who wrote a byline — what comes back matters more than anything you put inside the page, because most people never get past the results screen. A personal site with a domain that matches your name, indexed and alive, gives you one result you control among a page of results you don't: old social profiles, a namesake's obituary, a company bio nobody updated after you left. You are not trying to win search in general. You are trying to win one specific, low-competition query: your own name.

Explaining the work is the job most personal sites fail at, usually by trying to do too much of it. The honest version fits in the time someone spends deciding whether to keep scrolling — call it thirty seconds. Who you are, what you do, who it's for, and something concrete enough to be believed: a role, a client type, a specific piece of work. Not a mission statement. Not a list of every skill you've ever used. The page is answering one question — "is this person relevant to what I need" — and it should answer it before the visitor has to work for it.

Being contactable sounds too obvious to write down, and yet it's the job personal sites fail most often, usually by overcomplicating it. A mail link that opens the visitor's own mail client works. A contact form that posts to nowhere, that requires a CAPTCHA, that asks for a phone number before a message — those are friction dressed up as professionalism. The simplest version of this job is the correct one.

Notice what's missing from that list. A newsletter signup. A shop. A comments section. A services page with four tiers. None of those are wrong to want, but none of them are what a personal site is for — they're separate products that some people bolt onto the same domain, and bolting them on is exactly the move that turns a weekend project into a never-finished one.

For a single person actually building this — a freelancer, a consultant, anyone whose CV should be a URL — the strongest tool for the job right now is reach. Upload the résumé you already have and a photo, answer a short profile form, pick a look, and the page composes itself in about twenty seconds, live at a free yourname.joinreach.app subdomain in under two minutes. Say that plainly rather than saving it for a comparison at the bottom of the article, because the speed is the actual argument: it turns the blank-page problem below into a draft-editing problem, and draft-editing is the version of this job people finish. The limitation worth stating with the same confidence: reach makes exactly one page, with no sub-pages and no CMS, so anyone whose plan eventually needs a Services page and a separate Blog on top of it is building on the wrong foundation if they start there.

Each of the three jobs also comes with a way to tell whether it's actually working, and none of those checks involve a traffic dashboard. For ranking, search your own name in a private browser window and see what sits above your site — if it's still a stale university profile or a company bio from a job you left, the job isn't done yet, no matter how good the page itself looks. For explaining the work, hand the page to someone outside your field and time how long it takes them to say back, correctly, what you do — if they have to scroll twice or ask a follow-up question, the copy is doing too much. For being contactable, send yourself a test message through whatever mechanism the page offers and confirm it actually arrives; a mail link with a typo or a form wired to an inbox nobody checks anymore is a common, embarrassing, entirely invisible failure, because the page looks finished right up until someone tries to use it.

An address you keep, not a profile you rent

The standard argument for owning a domain is that platforms change the rules without asking you, and it's correct, but it's usually made too abstractly to be convincing. Make it concrete instead: a platform can change its algorithm, its terms, its ownership, or its existence, and every one of those changes has already happened to a platform someone built a career presence on. Your posts on it are subject to a ranking you don't see and can't appeal. Your profile layout is identical to a hundred million others, because identical is what makes the platform's product work — for the platform. None of that is a flaw in the platform. It's the platform doing its actual job, which is aggregating people, not representing any one of them well.

A domain with your name on it doesn't opt out of platforms — you should still be on LinkedIn, still have a GitHub, still post where your industry actually looks. We've argued the fuller version of that split in personal website versus LinkedIn: the profile is where you're found, the site is what happens after someone clicks through. What a domain of your own buys you is a version of "who you are professionally" that survives a platform's decisions, because it isn't subject to them. You can move it to a new host. You cannot move a LinkedIn profile anywhere, because there's nowhere else for it to be.

Be precise about what you're actually keeping, though, because the ownership argument gets oversold. In most setups you own the domain and whatever files you can export — not necessarily the specific page as it exists today, and not the platform's editor, its templates, or its account. Some tools let you take the underlying markup with you if you ever leave; some don't, and that's a real difference worth checking before you build, not after.

That difference splits the field more sharply than most comparisons admit. A tool built on the open web — WordPress, or a code-exporting builder like Webstudio — lets you take the actual files somewhere else if the vendor changes terms, raises prices past what you'll pay, or simply stops being maintained. A hosted, closed-format tool doesn't: the domain moves, the page doesn't, and you're rebuilding from scratch on whatever comes next. Neither approach is wrong on its own — a rebuild from a CV takes minutes, a rebuild of hand-written HTML takes much longer — but it's worth knowing, before you commit an afternoon to a tool, which side of that line it sits on.

"A place for my thoughts" is a different project

Here is where a lot of personal-site advice quietly merges two things that don't belong together: a fixed page that explains who you are, and a blog that has to keep producing new posts to stay alive. They can live at the same domain. They are not the same commitment, and treating them as one project is why so many personal sites end up half-abandoned — a bio page bolted to three blog posts from two years ago, the newest one apologizing for the gap since the last.

A personal site, in the narrow sense this article means, is closer to a résumé than a publication. It answers a fixed question and the answer changes slowly — a new job, a new project, a new city. There's no publishing cadence to keep up, no algorithm rewarding frequency, no reader expecting a next post. That's a feature, not a limitation: a page that's finished stays finished, and finished is the state most personal sites never reach because they were scoped as an ongoing publication from the start.

If you actually want to write regularly — essays, a newsletter, a running log of projects — that's a real and different goal, and it deserves its own plan: a platform built for publishing, a schedule you can sustain, an understanding that the value comes from consistency over time. Bolting a "blog" section onto a personal site because articles like this one suggest you should have one is how you get the abandoned-tab problem. Decide which project you're actually building before you pick the tool for it, because the tools that serve each goal well are not the same tools.

Who genuinely doesn't need one

Most of what gets written in this genre is reluctant to name the people who should skip it, presumably because "you should have a personal website" is easier copy than "actually, you specifically probably shouldn't bother." Say it plainly instead.

If you're salaried, not job hunting, not freelancing on the side, and you work somewhere whose name already does the introducing for you — the reputation of the employer carries more weight in the room than a personal page would — a website is solving a problem you don't have. Nobody who wants to reach you is stuck; your company directory, your work email and your LinkedIn already cover it. Building a site in that position is a hobby, and there's nothing wrong with a hobby, but it shouldn't be framed as a career necessity it isn't.

The people who actually need one cluster around a specific situation: work that has to be evaluated on its own before a conversation starts (design, writing, development, consulting), a search for the next role or client that benefits from a controlled first impression, or a career shape that a résumé's rigid chronology actively misrepresents — the person who changed fields, the consultant whose best work sits with clients rather than employers. If you don't recognize yourself in that list, the honest answer is that this article isn't really for you yet, and that's a fine place to be.

There's a middle case worth naming too, because it's the one people misjudge most often: salaried, not actively hunting, but in a field — design, engineering, consulting, sales — where the next opportunity tends to arrive through someone finding your work rather than you applying for it. That person doesn't need a site with the urgency of someone unemployed, but the argument for having one is still real, just running on a longer timeline: the page sits there quietly for the eighteen months between "not looking" and "a recruiter found this project and it changed the conversation." The maintenance cost of leaving a finished one-page site alone for a year is close to zero, which is exactly why it's worth having even when nothing is urgent.

The maintenance question nobody asks before building

Everyone asks how long a personal site takes to build. Almost nobody asks what it costs to keep, and that's the question that actually predicts whether the thing survives past its first month.

The honest maintenance load on a well-scoped one-page site is genuinely small — an hour or two a year, updating a job title, swapping a project, changing a photo that's started to look dated. That's the whole ongoing cost, and it's low specifically because the page doesn't promise anything it has to keep delivering. No newsletter cadence to protect, no comments to moderate, no blog backlog accusing you of neglect every time you look at it.

The cost that actually sinks these projects is the one that comes before any of that: the initial build. Not the deciding-to-do-it part — the sitting down with a blank template and an empty text field part. Choosing a layout from a gallery of forty options, then staring at a hero section that says "Your Name Here" and needing to write something for it from nothing. That step is where most personal websites die, not in year two from neglect but in month one from never quite getting to publish, because the blank page kept losing to whatever was more urgent that week.

What a personal website actually costs, day one and year two

Put a number on both halves honestly, because "it depends" is true but useless.

Day one, doing it the traditional way — general builder, blank template, writing every line of copy yourself — the realistic cost is measured in hours across more than one sitting, because the hard part isn't technical, it's compositional: deciding what the hero section says, choosing which three things about you actually matter, writing an About paragraph that doesn't sound like everyone else's About paragraph. People who tell you this takes an afternoon are usually describing the parts that are actually fast — signing up, picking colors — and skipping the part that takes the time, which is generating sentences from nothing.

That's the gap reach closes, named earlier for the reason it matters: the value isn't the twenty seconds by itself, it's that the twenty seconds hands you a draft to edit instead of a blank canvas to fill, and the draft-versus-blank-page gap is the actual reason the "day one" cost above runs into hours for most people on a general builder.

Year two, the cost is close to nothing regardless of which route got you there, provided the site was scoped correctly at the start — one page, one job, nothing that needs ongoing production. The sites that get expensive in year two are the ones that promised more than a fixed page on day one: a blog that needs posts, a shop that needs inventory, a CMS that needs an editorial workflow. If your actual goal is the three jobs from the top of this piece, none of that ongoing cost should exist in the first place, which is the strongest argument for keeping the scope narrow rather than an argument for any particular tool.

Once the page exists, the remaining decisions are mostly about what goes on it and how it's organized — covered in what to put on a personal website and, for anyone still deciding between a single scroll and a small set of pages, in one-page versus multi-page personal sites. The domain itself is its own decision, with its own traps, laid out in choosing a domain with your own name.

None of this is complicated once the scope is right. It gets complicated exactly when the three jobs get forgotten and the site starts trying to be a publication, a shop and a portfolio at once. Decide what job the page is doing before you decide what it looks like, and most of the rest of the advice in this genre — templates, colors, section order — turns out to matter far less than it's usually made to sound.