Last updated August 4, 2026
How to Create a Personal Website: The Decisions That Come First
Most unfinished personal websites don't fail at the building step — they fail because nobody made the decisions below first, so every later choice becomes a fresh debate.
These decisions can genuinely be made in an afternoon, sitting down with a notebook or a blank document, before touching any design tool or builder. The output isn't a finished website — it's clarity that makes every subsequent step faster and less prone to the kind of indecision that stalls most self-built projects.
Who Is This Site Actually For?
Not "everyone who might Google me" — a specific reader. A recruiter evaluating you for a role reads differently than a client deciding whether to hire you, and a site trying to serve both equally usually serves neither well. Pick the primary reader and let secondary audiences be secondary.
What's the One Thing You Want Them to Do?
Email you? Book a call? Download a resume? A site with one clear intended action converts better than one that lists five equally-weighted options. Decide this before you write a single word of copy.
What Do You Actually Have to Show?
An honest inventory: real projects, real work samples, real testimonials if you have them. Don't design around content you don't have yet — a "coming soon" portfolio section undermines trust more than a smaller, fully-populated one.
How Much Time or Budget Do You Actually Have?
This determines your path more than anything else. If you have real time to invest and enjoy the process, DIY is legitimate. If you know what you need but don't want to spend the hours, a done-for-you service exists for exactly that gap.
One Page or Several?
A single, well-built page beats a five-page site with two pages left thin. Only go multi-page once you genuinely have enough distinct, substantial content to justify separate pages.
What Does Success Actually Look Like?
Define this concretely before building — is success a specific number of inquiries per month, a single great job offer, or simply having something professional to point people to? A vague sense of "it should work" makes it impossible to know later whether the site is actually succeeding or needs revision.
How These Decisions Interact With Each Other
These aren't independent choices — your answer to "who is this for" shapes what counts as the right one action, which shapes how much content you actually need, which shapes whether one page or several makes sense. Working through them in this order, rather than jumping straight to page count or design, tends to produce a more coherent final site than tackling them in isolation.
A Quick Self-Check Before You Start Building
If you can write one clear sentence combining your answers — "this site is for [specific audience] to [specific action], showing [specific proof]" — you're ready to move to execution. If that sentence still feels vague or tries to cover multiple unrelated goals, it's worth spending more time on these decisions before building anything.
Common Ways These Decisions Get Skipped
The most common shortcut is jumping straight to comparing website builders or templates, treating the tool choice as the actual decision that matters — it isn't, until the underlying questions above are answered. A close second is answering these questions too broadly ("this is for anyone who might be interested") rather than committing to a specific enough answer to actually guide content and design decisions.
How to Revisit These Decisions as Your Situation Changes
These aren't one-time decisions locked in forever — a career shift, a new specialty, or a change in what you're looking for next all warrant revisiting the same questions. Treating the site as a living reflection of current goals, rather than a fixed artifact from whenever it was first built, keeps it actually useful rather than gradually becoming outdated.
Why This Planning Phase Matters More Than It Might Seem
Skipping straight to building without this groundwork doesn't just risk a weaker final site — it often produces genuine indecision throughout the entire build, since every subsequent choice (what to write, what to include, how to structure it) implicitly depends on answers to these questions that were never actually settled. Doing this work upfront converts dozens of small, recurring decisions into a handful of clear ones made once.
Frequently Asked Questions
What if I genuinely don't know who my primary audience is yet?
Think about who you've actually wanted to send a link to in the past few months — that real, specific memory is usually a better guide than an abstract attempt to define an audience from scratch.
Is it a problem if my answer to "what's the one action" changes over time?
No — the site can and should evolve as your goals change; the point is having clarity for the current version, not locking in a permanent answer.
How honest do I need to be about what I currently have to show?
Completely honest — designing around content that doesn't exist yet is exactly what produces the half-finished "coming soon" sections that undermine trust more than a smaller, complete site would.
Should these decisions be made alone, or is it useful to talk them through with someone else?
Talking them through with someone who knows your work can surface blind spots, particularly around what you actually have to show — you often underestimate your own relevant work.
What if my available time or budget only supports a very minimal site?
That's a completely legitimate answer — a well-built single page beats an ambitious multi-page plan that never gets finished within your actual available time.
How do these planning decisions differ if I'm building for a business versus purely personal use?
The underlying questions are the same, but a business context usually makes the target audience and desired action clearer faster, since there's typically a more specific commercial goal driving the site.
Should I write these decisions down, or is thinking them through mentally enough?
Writing them down, even briefly, tends to expose vague or contradictory thinking that stays hidden when the process is purely mental — it's a small extra step that catches real problems before they become baked into the finished site.
What if my answers to these questions conflict with each other?
That conflict itself is useful information — it usually means one of the underlying goals needs to take priority over the other, and resolving that tension now is far cheaper than discovering it after the site is already built.
How much time should this planning phase actually take?
For most people, a single focused sitting — an hour or two of genuine thinking — is enough to reach real clarity, though the value comes from honesty, not from the time spent.
Is it possible to over-plan and delay actually starting the build?
Yes — these decisions are meant to take a single focused session, not become an extended research project of their own; once you have honest, specific answers, moving to execution is the right next step.
Should I involve other people in making these decisions?
A trusted second opinion can be useful, particularly for the 'what do I actually have to show' question, since people often underestimate their own relevant work — but the final decisions should reflect your own honest assessment.
How do these planning questions change for someone with a very unconventional career path?
The same underlying questions apply, though the answers may take more thought to articulate clearly — an unconventional path often has a more interesting story to tell once you've done the work of identifying its actual throughline.
Can these planning decisions be made differently for a business-focused personal site versus a purely career-focused one?
Yes — a business-focused site typically has a clearer, more transactional 'one action' (booking, purchasing) while a career-focused site's action is often softer (an email, a conversation), which shapes how directly the site should push toward that action.
Is it worth creating multiple draft answers to these questions before settling on one?
For genuinely difficult cases, yes — writing two or three different framings and comparing them can clarify which one actually feels most accurate and compelling before committing.
What's the relationship between this planning phase and the actual content-writing that follows?
This planning phase produces the strategic answers; the content-writing phase translates those answers into actual sentences and sections — skipping straight to writing without this groundwork tends to produce content that sounds fine sentence by sentence but doesn't add up to a coherent overall site.
Does this planning process differ meaningfully for a done-for-you build versus a DIY one?
The underlying questions are identical either way — a done-for-you service still needs your honest answers to build the right site, so this planning work isn't something outsourcing the build lets you skip.
Should I share these planning answers with whoever is actually building the site for me?
Yes, explicitly — a done-for-you service can only build the right site if it has clear, honest answers to these questions upfront, so treating this as internal-only thinking wastes the value of having worked through it in the first place.
What if I realize partway through building that my original answers were wrong?
That's a normal part of the process, not a failure — revise the specific answer that changed, and adjust the affected content accordingly, rather than treating the entire plan as invalidated by one changed assumption.
None of these decisions require extensive research or expertise — they require honesty about your actual current situation, which is exactly why they're worth resolving before any building begins rather than being discovered halfway through a stalled project. The clarity gained here pays for itself many times over in the building phase that follows.
Already know what you need?
See Plans & Pricing →Related: Done-for-You vs. DIY Website Builders · How to Make a Personal Website