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.
Copy the output straight from your AI tool — the raw HTML or markdown, not a screenshot. There is no file to save and no app to install first.
Paste it into the box above. The preview renders it the way the recipient will see it, so you can confirm the formatting before you share.
Create the link and send it. Whoever you send it to opens a clean, read-only page in their browser — on a laptop or a phone — with nothing else from your chat attached.
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.
No. Every published page is served with noindex directives in both the HTTP response headers and the page metadata, so search engines are told twice not to list it. For a document that contains your phone number and address history, that default is the point — you want it openable by the person you sent it to and invisible to everyone else.
For a single application, the free tier’s seven-day expiry is often ideal — the link outlives the interview loop and then retires itself. For an active search where the same URL goes onto dozens of applications over months, pay for permanence; a link that dies halfway through a hiring process is a bad first impression you will not be told about.
Yes. Scripts run in the published sandbox, so accordions, tag filters, and smooth-scrolling navigation behave as built. Avoid anything that depends on remembering a visitor between sessions, since the sandbox withholds browser storage — but a resume has no real reason to need that.
Keep both. Plenty of applicant tracking systems only accept an uploaded file, and fighting that is not worth it. Use the link where a human will click it — in your email signature, on the application’s "portfolio" field, in a LinkedIn message — and the PDF where a form insists.
免費帳號的連結保留 7 天。升級付費方案後，你建立的每個頁面都會永久上線。
查看方案與價格