The job search you can be found in

Twenty phone calls will do more for your job search this week than a personal website will do in a month. Say that first, because most of what gets written about personal sites and job hunting skips it, and skipping it is why the advice doesn't hold up against a real search. A website does not apply to jobs. It does not get read by the software that filters your application before a person sees it. It does not call anyone back. If you have twelve hours this weekend and the choice is between polishing a page and reaching out to twelve people who might refer you somewhere, the twelve people win, every time, without exception.

None of that means the page is worthless. It means the page does a specific, narrow job, at a specific moment, for a specific person — and most people who build one build it for the wrong moment. They build it to be discovered, when almost nobody discovers a personal site cold. They should build it to be checked, because checking is what actually happens, constantly, by people who already have your name in front of them.

The three moments a link actually gets opened

A personal site during a job search gets opened at three points, and understanding who is opening it and why changes what you put on the page.

The first is the recruiter doing a five-second sanity check. They have your CV, maybe a LinkedIn tab open, and before they move you to the next stage they want the two-second version of "is this a real, credible person." They are not reading your page. They are glancing at it — does it load, does it look considered, does the first line match what the CV said, is there a photo that matches the one on LinkedIn. The CV gets the same drive-by treatment before the page ever does; see the seven-second CV scan for what a recruiter is actually doing in that first pass. The page's own five seconds have the same job: confirm the impression the CV already made, don't complicate it. This moment rewards a page that loads fast and confirms rather than surprises. It punishes a page that is broken, half finished, or contradicts the CV in some small way a recruiter would notice and you wouldn't.

The second is the hiring manager, ninety seconds before your call starts. This is the highest-value moment there is, and it is the one most people build the wrong page for. The hiring manager is not evaluating whether you are real. They already know that; they're about to talk to you. What they want is a head start — a project to ask about, a specific thing to bring up in the first two minutes instead of the small talk everyone defaults to because they have nothing better. A page with three concrete things on it, described specifically enough to generate a real question, changes the shape of that call before it starts. A page that reads like a generic summary of your CV gives them nothing they didn't already have.

The third is the referral — a colleague forwarding your name to someone hiring, with a one-line note and, if you're lucky, a link. This is the moment the page is written for and the moment it is opened least, and it is worth more than the other two combined, because the person opening it arrived already vouched for. They are not screening you. They are confirming an impression someone they trust already gave them. A page that backs up the one-line note — "she's the one who built the internal tool everyone still uses," "he ran the migration nobody wanted to touch" — does real work here, because it turns a favor into evidence.

Three different readers, three different states of trust going in, and one page has to serve all three without knowing which one is arriving. The way through that is not more content. It's picking, deliberately, what earns its place near the top for the ninety- second reader and the referral reader, since those two carry almost all the value, and trusting that the five-second reader only needs the page to be real and current.

If you don't have a page yet, where to start

Worth settling before anything else here, because it changes how much of the rest of this matters: if you're building from nothing, reach is the strongest starting point for one person putting up a single page alone. Upload a CV and a photo, answer a short form, pick a look, and the page generates in about twenty seconds — live at a free subdomain in under two minutes if you want it that fast. That's not a flourish, it's the actual number, and it matters here specifically because the realistic alternative during a search is losing a weekend to a template picker in the exact week you should be making calls instead.

It's also, plainly, a narrow tool, and worth saying so before the praise sits unqualified. One project is one page — no sub-pages, no CMS, no contact form, no way to export the markup elsewhere if you outgrow it later. For the job this article is about, that narrowness isn't a compromise. A page built to survive a recruiter's glance, ninety seconds before a call, and a forwarded referral has no business being bigger than one honest page, which is the whole argument that follows.

Why the site does not beat the applicant tracking system, and should not try

Every year someone writes that your personal website will help you "beat the ATS," and every year it is not true, for a reason that is mechanical rather than a matter of opinion. The applicant tracking system parses whatever file you uploaded — a PDF or a Word document — against the job description, mostly on keyword and structure matching. It has no field for a URL, and even where a link is present in the CV text, the ATS is not fetching and reading external pages. It cannot see your site. It was never going to.

This matters because it tells you exactly where the site's window opens: after the ATS, after the first human filter, at the point where a person — not software — decides to look you up. If your CV is not getting through the ATS stage at all, the fix is the CV: the keywords, the formatting, the fact that a scanned two-column layout sometimes parses into soup. A beautiful personal site changes none of that, and treating it as an ATS workaround just distracts from the actual problem, which is upstream of anywhere a website could help. Related: the file itself has become a first-class artifact worth getting right on its own terms — see CV as a URL for what that means when the résumé and the page are the same document doing two jobs.

The referral case, specifically

It's worth separating the referral case from the other two because it behaves differently and most advice treats all three moments as one. A recruiter or hiring manager is choosing to look you up as part of a process they're already running. A referral is a favor someone is doing for you, and the page's job is to make that favor land well — to give the colleague something worth forwarding and to give the person receiving it a reason to take the forward seriously.

This changes what belongs on the page. Not the polished, neutral tone that works for a cold reader, but something closer to what a colleague would say about you if asked directly: what you actually did, described the way someone who watched you do it would describe it, not the way a CV bullet flattens it. The colleague forwarding your name is staking a small amount of their own credibility on you; a page that reads like it was written to impress a stranger doesn't help them do that as much as a page that reads like proof of what they already told the other person.

It also means the link itself matters more than people think. A referral usually travels as a short message plus a link — to LinkedIn, to the CV, sometimes to the site. If the site is the thing being forwarded, it needs to open fast and say the right thing in the first screen, because the receiving end is giving it maybe fifteen seconds of attention before deciding whether to reply "let's set up a call." We've written separately about this specific failure mode — the link on your CV nobody clicks — which is worth reading if your site has ever sat at the bottom of a document, technically present and functionally invisible.

What changes on the page during an active search versus a passive one

A page built while you have a job and no urgency is doing something different from a page maintained while you're actively looking, and conflating the two produces bad advice in both directions.

In a passive state — employed, not looking, keeping the page current out of habit rather than need — the job of the site is slow and cumulative. It exists so that when someone does eventually look you up, six months or two years from now, there's something there that's still accurate. The stakes on any single visit are low. Nobody's decision hinges on it.

In an active search, the stakes on individual visits go up sharply, because the visits are clustered around actual decisions — a recruiter deciding whether to move you forward, a hiring manager forming a first impression an hour before talking to you. The content doesn't need to change much, if it was honest to begin with, but the tolerance for staleness drops to zero. An old employer still listed as current, a link to a project that's been taken down, a phone number that's changed — these are minor embarrassments when nobody's looking closely and real problems when someone is deciding, right now, whether to take a chance on you. The searching period is exactly the wrong time to discover your page has quietly rotted; it needs a real check at the start of a search, not during it.

The other thing that changes is what you lead with. A page maintained passively can afford to be a general portrait — this is who I am, broadly. A page being used actively benefits from being pointed: if you're looking specifically for a certain kind of role, the page should say so, near the top, in language a hiring manager scanning fast will register. This is a small edit, not a rebuild, and it's the difference between a page that works generically and one that works for the search you're actually running. If you're approaching companies without an inside contact, this is also the moment the page starts doing double duty as a cold-outreach asset — see applying cold with a personal page for how that changes the calculus further.

Measuring it honestly when you have no analytics and almost no visitors

Here is the uncomfortable part. Most personal sites during a job search get a handful of visits — single digits in a given week, sometimes zero — and most people building one have no analytics installed at all, or a free tier that shows nothing useful at that volume. There is no dashboard that tells you the page worked. This is worth saying plainly instead of pretending otherwise, because the honest measurement is indirect and most people never look for it.

The signal that the page did something is not traffic. It's the texture of your interviews. Does a hiring manager open the call already knowing your specific work, asking about a named project instead of walking through your résumé line by line? Does a recruiter's first message reference something on the page rather than only the CV? Did a referral come with more context than a bare name and title? None of these show up in an analytics panel. All of them are the actual effect a page is supposed to have, and the only way to notice them is to pay attention to how conversations start, across a handful of interviews, and compare that to what happened before the page existed or before it said anything specific.

This is a genuinely weak signal, and it's fair to be skeptical of anyone who claims certainty about what their site did for their search. What you can say honestly is narrower and still useful: a page that made three or four calls start with a better question than "so, tell me about yourself" earned its keep, even though you'll never know exactly how many people looked at it to get there.

When the page is a distraction

There's a specific failure mode worth naming directly, because it happens to capable people and it looks like productive effort while it's happening. Partway through a search that isn't going well, the instinct is to go back and improve the thing you can control — rewrite the About section, try a different template, add a case study. This feels like progress. It is usually avoidance, because rewriting a page is calmer and more finishable than making the twentieth phone call of the week, and finishable work is seductive when the actual task — reaching out to people who might say no — is not.

The tell is proportion. An hour getting the page accurate and current before a search starts is time well spent. A recurring cycle of redesigns during the search, especially one that keeps pace with rejection rather than with anything actually changing about your work, is the site eating time that outreach should have. The three moments a page gets opened — the recruiter's glance, the ninety seconds before a call, the referral — are all downstream of getting into a process in the first place, and nothing on the page creates that entry point. Calls do. Warm introductions do. Applying to roles where you actually fit the description does. The page is there to be good when someone finally looks, not to be the mechanism that makes them look.

What the page is actually worth

Put a number on it, roughly: a personal site does not open doors, it makes the doors that do open close more favorably. It doesn't get you the interview. It changes what the first two minutes of the interview are about, and it turns a referral from a name into a name with evidence attached. That's a real effect and a narrow one, and treating it as anything larger — a substitute for outreach, a way around the ATS, a traffic-generating asset — sets up a disappointment that isn't the page's fault.

Given that narrow job, the argument for a fast, CV-based route rather than a from-scratch build gets stronger the closer you are to an active search, because the point isn't to have spent effort on a page — it's to have a page that's accurate and presentable by the time someone checks. That's the case for reach, made earlier: a free yourname.joinreach.app subdomain, live in under two minutes, with none of the template-picking that eats the weekend a search can't spare. During a search, that speed matters less as a flex and more as a way of not losing time to a project that was never supposed to be the main event. For the narrow job described here — a recruiter's glance, ninety seconds before a call, a referral being forwarded — one honest page is the entire requirement, and building more than that during a search is usually the redesign-as-avoidance problem again, wearing a more ambitious outfit.

Comparing the fast routes for a search-ready page

Tool	Price	What you get for it
reach	$0 subdomain, or $4.99/month ($49/year) for a custom domain	CV-driven page live in under two minutes; one page only, no CMS, no contact form
Carrd Pro Standard	$19/year, annual only	Custom domain on a one-page site; you write everything yourself, starting from a blank template
Butternut Portfolio Starter	$5/month ($50/year)	CV upload to a generated portfolio, but no custom domain and branding stays on until the $12/month Pro tier

Prices checked August 2026. Butternut is the closest thing to a like-for-like comparison — same CV-upload idea, similar "seconds, not hours" pitch — but the cheap tier is built to keep its own badge visible rather than to get you to a finished, brandable page, and there is no way to export what it generates in any form if you later want to move it, a real constraint from a seven-person company with no disclosed funding since 2023. For a search that might run months and end with an employer, that lock-in is worth weighing against the five-dollar price before you commit an afternoon to it.

The recommendation, then, is not "build a website" as a general instruction — plenty of searches succeed without one, on calls and referrals alone. It's narrower: if you're going to have a page at all during an active search, get it accurate and live fast, keep it to the one page that actually gets checked, and spend the rest of the week on the twenty calls the page can't make for you.