Freebies, drafts, little tools — as a creator you keep needing a link that reaches specific people and nowhere else. A working guide to private share links for the three things creators send most.
The creator playbook is built around reach. Grow the list, rank the post, get the thing found. But the further you get, the more of your output is the opposite of public. The freebie is for the list, not the search index. The draft is for one reader, not the feed. The little tool is for a segment, not the whole internet. None of that wants to be found — it wants to be delivered, to a specific short list, and stay out of everywhere else.
That's a different verb, and most tools don't have it. Publishing makes things public; a private share link makes things delivered. This guide walks the three artifacts a creator sends most — freebie, draft, tool — and marks the one place where a link stops being the answer.
You made something to give away — a template, a swipe file, a mini-guide, a resource page. The usual options both leak. Wire it into an email tool behind a gate and the friction costs you the opt-ins you were trying to earn. Drop it on a public host and the URL is one search away from people who never joined your list — "early access" that anyone can stumble into isn't early access.
A private link sits between those. You drop the HTML, you get an unguessable URL, and that URL is the handout. It opens in any browser with no signup on the reader's side, so the friction that kills freebie conversion isn't there. And because the page is no-index by default, "exclusive" stays actually exclusive instead of surfacing in search the week after launch.
When you do want a gate, you have a few clean ones, and none is an account. Add a password and send it through the same channel as the link, so a casual forward stops at the prompt. Or set an expiry so a launch-week bonus actually stops working when the window closes — scarcity that's real, not staged. And if the freebie's whole job is to grow your list, the page becomes the lead magnet you host: turn on the email gate and it opens behind a short form, the visitor enters their address to unlock, and the leads collect in your dashboard to export as CSV — no separate form tool to wire up. (Syncing those addresses into an automated sequence is still a backend job; the capture and export happen on the page.)
The point isn't to lock people out. It's that "anyone can open this" should mean anyone you sent it to — not anyone at all.
This is the handoff creators underrate. You finished a draft — a landing page, an essay laid out the way it'll actually read, an interactive prototype — and you want exactly one or two people to react before it ships. Not the world. Not your whole audience. A trusted reader, an editor, a co-founder.
Every default option distorts it. Email flattens anything interactive into a screenshot. A public host means your unfinished thing is technically live on the open web while you're still deciding whether it's any good. A screen-share traps the feedback in a call you both have to attend. None of those is "show this one person the real thing, privately, on their own time."
A private link is. The draft renders exactly as it will when it's real — animations, layout, the lot — at a URL you hand to one person, and no-index keeps a half-formed idea out of search while you sit with it. When that reader is ready to respond, turn on Review: they pin a comment to the exact element they mean — this headline, that button — with no account, and you resolve the thread on your side. No more "the part near the middle, you know the one." Review itself is free on every plan; on Studio you can also export the resolved thread as a prompt and hand it straight to Claude or Codex to make the edits.
For drafts that came out of an AI builder, the same flow covers the vibe-coded app or the v0 page you want eyes on before it's public. And drafts are where analytics earn their keep — knowing your reader actually opened the thing beats waiting on a reply that may never come.
The third artifact is the one you built to draw people in. A pricing calculator. A quiz that returns a result. A one-page site for something that doesn't need a whole site behind it. These are HTML and JavaScript that run entirely in the browser — exactly what a private-link host serves cleanly.
The trap is assuming a small interactive thing needs a full website to live on. It doesn't. If the page is self-contained, you drop it and it works — filters, results, the interactive bits all intact, nothing flattened. You hand the link to a specific audience: a newsletter segment, a partner, a community. When it's ready for everyone, you can move it to your own custom domain so it reads as yours rather than as a generic share URL.
Here's where a private link stops being the answer. The moment your tool needs to save something — write a quiz result to a database, sign users in, hit a backend on every load — you've crossed from a static page into an application. A self-contained file can't do that, and pretending otherwise just breaks later.
That's not a flaw to route around; it's a different job. For an app with a server and a database, deploy it on a platform built for exactly that — Vercel or Netlify will run the backend properly. A private link still earns a role alongside it: the static slices around the app — the lead magnet, the preview build, the marketing one-pager — are precisely the self-contained pages a private link handles best. Use each tool for the slice it's good at.
Three artifacts, one habit. The freebie, the draft, the tool are all finished files meant for specific people, and the question is never "how do I make this public" — it's "how do I deliver this to the right people and nowhere else."
A private share link answers that directly. Private and no-index by default, so nothing leaks before you mean it to. No signup on the viewer's side, so the friction that costs you opens isn't there. Password, expiry, analytics, a custom domain, and pinned feedback when the artifact calls for them. The file you made stays the file you made — it just travels the way creator work should: to a list, not to the world.
If something's sitting in a folder right now — a giveaway, a draft, a tool — that's your test case. Drop it, get the link, send it to one person. Browse the use-case library or start free.
Your freebie is the first thing a stranger ever taps in your bio — and a raw storage or design-tool URL gives you away before the page loads. Why a link-in-bio freebie should ride on a branded, own-domain link, and how to do it with no website and no server.
How analysts, freelancers, and agencies hand AI-built client work over as a private, branded link instead of a raw chat export — so the work reads as a finished decision, not a transcript of the model making it.
Designers, freelancers, agencies, consultants, in-house teams, and educators all hit the same wall — handing a finished HTML deliverable to the people who should see it. How the channel choice changes by role.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.