Where should my personal website link go on a CV?

Next to your name and contact details only if the domain itself is the pitch — your name, nothing else, and it is memorable. Otherwise put it lower, attached to the specific project or piece of writing it leads to, where the label can do the work the bare URL can't.

Does an applicant tracking system follow the link on my CV?

No. ATS software parses your document as text and stores whatever string sits there; it does not fetch the page, so the link's design, speed or content have zero effect on whether you pass the screen. A human decides whether to open it, later, on their own.

Should I use a URL shortener on my CV so the link looks cleaner?

No — a shortened link hides the destination and reads as either an ad or a tracking device, which is the opposite of what you want a stranger to feel a second before deciding whether to click. A plain, readable domain or a labelled deep link both signal exactly what's on the other side.

What happens to a CV link if I rebuild my personal website later?

Whatever page that link pointed to, if it wasn't your homepage, almost certainly stops existing. The fix is discipline, not tooling — never point a CV link at anything other than your root domain, so a rebuild changes what's there without changing what a five-year-old PDF still says.

The link on your CV that nobody clicks

Open the last CV you sent out and look at the line under your name. There is a decent chance it reads janesmith.com, sitting there in a slightly smaller font, doing nothing. Not because the recipient couldn't be bothered — because the link gave them no reason to. A bare domain makes no promise. It doesn't say what's behind it or why looking would be worth the four seconds between finishing your CV and opening the next one in the pile. So it gets skipped, the same way most of us skip the "click here to read our privacy policy" link at the bottom of an email, and for the same reason: no information about the payoff, no click.

This isn't a design problem. Redesigning your CV so the link is bolder or more prominent won't fix it, because the problem isn't visibility — recruiters read the top third of a CV closely enough to see a domain sitting right under a name. The problem is that the domain answers a question nobody asked. "Here is my website" is not information; "here is the project I'm proudest of" is. One of those gets clicked.

For anyone whose problem is that there's nothing worth linking to yet, the fastest fix is reach: upload the CV you already have, pick a look, and a finished one-page site is generated in about twenty seconds — live at a free subdomain in under two minutes. Its one honest limit: reach builds exactly one page, no sub-pages, no separate URL structure. For a CV-as-a-page that's closer to a feature than a cost, as the link-rot section below gets into.

What a domain promises versus what a reason promises

Compare two lines that could sit in the same spot on the same CV:

janesmith.com

Case study: redesigning checkout for a 40-person fintech → janesmith.com/checkout

The first is a location. The second is an offer, four words that tell the reader exactly what waits on the other side and lets them decide, before clicking, whether it's worth their next thirty seconds. A stranger scanning a CV is triaging, not reading, and triage runs on promises the reader can evaluate in under a second. "My website" cannot be evaluated — it could be a blog, a portfolio, a dead trial from years ago, nobody knows until they click, and most people don't spend a click on an unknown. A named destination can be evaluated instantly, and evaluating well is what gets it opened.

This is why the advice to "just add your website" undersells the actual job. The link itself was never the asset. The four words in front of it are.

Where the link belongs, and it depends on what it's carrying

A bare domain sits well in the header, next to your email and phone number, because a header is where identity information goes — this is who I am, here is how to reach me. It reads as an address, and an address in a header doesn't need to sell itself.

A link with a reason attached belongs somewhere else entirely: inside an experience entry, next to the specific role or project it illustrates. Led the redesign above → see the before/after sitting under a bullet point gets opened at a completely different rate than the same URL isolated at the top of the page, because it arrives exactly when the reader is already curious about that specific claim. The header placement answers "where can I find you." The project placement answers "can you prove that." Recruiters click the second one more, because it resolves a doubt they're actively holding rather than offering a destination they weren't looking for yet.

Most CVs only use the header slot. That's the whole diagnosis in one sentence: one opportunity to convert curiosity into a click, spent on the placement that carries the least of it.

Link rot is the part nobody plans for

Here's a failure mode specific to this exact use case. A CV is not a living document once it's sent — it sits in an inbox, an ATS database, a printed stack on someone's desk, for months or years after you stopped thinking about it. If the link points to a specific project page — janesmith.com/checkout-case-study — and you later rebuild your site, reorganize the URL structure, or move to a different builder entirely, that specific page is very likely to disappear. The domain survives. The deep link usually doesn't.

Someone digging through old applicants months later, for a different but related role, opens the CV you sent in the spring and clicks a link that 404s. That's a worse outcome than the bare domain you were trying to improve on, because a 404 doesn't read as "nothing here" — it reads as "this person doesn't maintain their own page."

The fix isn't to avoid deep links — the reason-attached link still wins on click-through — it's to never point a CV at anything other than the root domain, and let the root domain hold the specific project as a section rather than a URL you might restructure later. You get the specificity that earns the click without betting a two-year-old PDF against your next site redesign.

What an ATS actually does with the link, which is nothing

It's worth being precise about this, because a lot of CV advice implicitly assumes an applicant tracking system reads for quality the way a person does. It doesn't. An ATS parses your document into a plain-text record — name, contact fields, work history, keywords matched against the job description — and a URL in that text gets stored as a string, sometimes in a "website" field, more often just text near your contact details. Nothing fetches the page or checks whether it loads. The link passes through the screen completely inert and starts doing work only later, when a human opens the file and decides, on their own, whether four words next to a domain are worth a click. Optimizing a personal site's load time or SEO "for the CV screen" is solving a problem that doesn't exist; the only screen that matters is the human one, and the only lever there is the reason attached to the link.

The one case where the bare domain is right

All of this has an exception, worth stating plainly rather than pretending the rule is universal: if your name is genuinely the pitch — a recognizable name in a small field, a personal brand strong enough that people are curious about the person before any specific project — then janesmith.com in the header is exactly right, and adding a reason to it would undersell it. This is rare. Most people building a CV are not household names in their field, and pretending otherwise is how most bare-domain links end up unclicked: they were written for a reader who already knows who you are, sent to a recruiter who's never heard your name and needs a reason, not a shrine.

What actually goes at the other end of the link

None of the placement or labeling advice matters if the destination itself doesn't hold up in the four seconds it gets. This is where most people lose the click a second time — a half-built homepage, an About page with no specifics, a portfolio still showing the setup placeholder. The blank-canvas problem is why so many personal sites never get past a domain purchase: choosing a template and writing copy for it is a weekend most people never actually spend, so the CV link keeps pointing at nothing. reach, from earlier, is worth naming specifically here: its copy comes from the CV you gave it, not a shared template gallery, so what a recruiter finds behind the link actually matches the CV that sent them there. And its one limit solves the other problem this article is about — one page, no sub-pages, no separate URL structure means there's no deep link to rot, only the single address a CV should be pointing at in the first place.

Put the four words back on the CV

The bare domain isn't wrong because domains are wrong. It's wrong because it does the one thing a stranger scanning a stack of CVs has no patience for: it asks for a click without saying what the click is worth. Attach a reason, put it where the reason is relevant, and point it at an address stable enough to survive the next redesign. That's the whole fix.

For more on when a personal page actually gets opened during an active search, see the job search you can be found in; for the narrower comparison of a page against the platform recruiters already search, see LinkedIn's open-to-work signal versus your own page; and for the underlying idea that a CV itself can just be a URL, see the CV as a URL.