The problem with attaching a file
Every resume you email is a copy frozen at the moment it left. Spot a typo the next morning and there is nothing you can do about the twelve versions already sitting in twelve inboxes.
There are three other things a file does badly.
On a phone it lands in downloads. A recruiter opening your application between meetings gets a file manager, then a PDF sized for A4 on a screen the size of a hand.
It looks like every other attachment. resume_final_v3.pdf tells the reader nothing before they open it. yourname.sofast.host says who you are in the link itself.
It has no analytics of any kind. You have no idea whether it was ever opened.
What a link does instead
Update the file and the link now serves the new one. Everyone who has it sees the correction, including people you cannot email again.
Tap it on a phone and it renders in the browser. No download, no app, no zooming.
The address carries your name.
PDF or a web page?
Both work here. The honest answer depends on who reads it.
When the layout is the point, when you need it printable, or when you already have a version you are happy with. It goes up as it is and gets a link and a QR code.
Turn a PDF into a link →When most readers are on a phone, which for job applications they are. A web page adapts to the screen; a PDF does not. An AI tool will convert your resume content into a responsive page in a few minutes, and you host that the same way.
Plenty of people do both: the web page as the link they send, with a download button on it pointing at the PDF for anyone who wants the file.
Common questions
Most application systems accept a URL field, and a link in an email signature or a LinkedIn profile is read constantly. Where a system demands a file upload, attach the PDF and put the link in the document as well — then late corrections still reach anyone who follows it.
The link is public to anyone who has it, and it will not be indexed unless something links to it. For a resume that is usually the right balance. If you need real access control, this is not the tool yet.
Not at launch. If that matters to you, an outside analytics script added to an HTML version is the usual approach.
Your name, as plainly as possible. yourname.sofast.host or yourname-cv.sofast.host. You will end up reading it out loud on a call, so pick something you can say without spelling it.
Yes — a separate site per version, within your plan's site count, each with its own address. Keep the addresses distinguishable so you do not send the wrong one.
Leave it up. It is one of the sites your plan already covers, and the next time you need it, it is already there and already correct.