A URL on your application beats a PDF attachment — as long as the page behind it is not sitting in Google next to your phone number.
Filters and accordions keep working, and the page stays out of search results.
Asking an AI assistant to build a resume as a styled single-page site produces something noticeably better than a Word template: a proper layout, a skills section that is legible on a phone, maybe an expanding project list. Putting it online is the step that usually ends in a half-finished GitHub Pages repository. A published link is faster, but a resume is also the one document where being publicly indexed is genuinely bad — it carries your full name, email, phone number, and employment history in one place, which is exactly the combination scrapers collect. Pages published here are excluded from search engines by default, so the link works for the recruiter you sent it to without becoming a permanent public record.
A developer switching jobs has Claude build their resume as one HTML file: a header with contact details, four roles with expandable bullet points, and a project grid that filters by tag when you click a chip. Published, the filtering still works, so a hiring manager can click "React" and see only the relevant projects — which is the entire reason to send a page instead of a PDF. Because a job search runs for months and the same link goes on many applications, this is a case for a paid plan: a permanent link at a chosen slug that reads like a name rather than a random string, and does not lapse mid-process. The candidate also keeps a plain PDF for the application forms that demand an upload, and treats the link as the version a human actually reads. When the search ends, the page comes down in one action rather than living on at a public address indefinitely.
Free links last 7 days with a free account. On a paid plan every page you create stays online permanently.
See pricing