Do I need an account?

To publish, yes — a free one. Readers never do. You sign in, paste or drop your content, and get a link; your docs live in your teamspace, reachable from any device you sign in on.

Yes, for one person — free for up to 3 published documents. You paste Markdown or HTML, or drop a file up to 15 MB, and get a link at no cost. Inviting teammates takes a paid plan — a one-time $9 for 5 people or $19 for 10.

Can I password-protect it?

Yes. Visibility can be public, unlisted, private (teamspace members only), password-protected, or expiring. Expiry is opt-in, not a default penalty.

Does it work for a Claude artifact?

Yes. Have Claude export the artifact as a single self-contained file — one HTML file with inline CSS, or Markdown — then paste or drop it in. A static mockup renders as designed; an interactive app is shown frozen.

Share anything an AI made, as a real link

Why isn't AI output already shareable?

Because the AI never gave you a page. A ChatGPT canvas renders inside a sandbox with no publish button. A chatgpt.com share link shares the whole conversation — every prompt and false start — not the standalone thing you built. And a raw .html file doesn't render when you email it; it downloads, or shows up as source. So the output that looked finished on screen has nowhere to live once you want to send it to someone.

ilolink is that missing step: a place to put one AI-made artifact so it becomes a URL, served like any web page, with the reading captured on the other side.

How do I turn it into a link?

The loop is short:

Ask the AI for one self-contained file or export — a single HTML file with its CSS inline, a Markdown doc, an image, or a file. One artifact, not a project.
Paste it, or drop the file, into the composer at ilolink.com.
Pick a visibility mode — public, unlisted, private (teamspace members only), password, or expiring.
Get ilolink.com/<slug> and send it.

The branded link 302-redirects to an isolated render origin, view.ilolink.com, where the doc is served under a strict content-security policy (default-src 'none'). Untrusted AI HTML is sanitized on the way in: javascript:, data:, and vbscript: URLs are dropped, and no arbitrary JavaScript runs. A static landing-page mockup renders exactly as designed — the CSS is kept. By default an interactive JS app is shown frozen to its static state rather than executing — unless you mark the doc trusted at publish time, in which case it runs as-is inside a sandboxed frame on that same isolated origin. The cap is 15 MB per doc.

What can I share this way?

Today, cleanly:

HTML pages and landing-page mockups — the CSS survives sanitizing, so the layout looks right.
Markdown docs — specs, briefs, write-ups, README-style output.
AI-generated images.
Files — under the 15 MB cap.

Slides, PDFs, spreadsheets, and diagrams — plus audio and video — are on the roadmap, not shipped. Media hosting isn't live yet, so don't plan around per-slide or per-page analytics today. When it lands, it lands; for now, the honest set is HTML, Markdown, images, and files.

What do I learn after I share?

This is the part the AI tools don't give you. Once the link is out, ilolink shows you how the page was actually read — all cookieless, from a rotating visitor hash, with no fingerprint and no personal profile:

Views — total, plus approximate unique views (uniques are approximate by design).
Scroll funnel bucketed at 0 / 25 / 50 / 75 / 100%, so you see where people stop.
Heatmaps — click and scroll, viewable by device class.
Reactions and notes — readers can react or leave a short note, no account.
Comments — threaded, anchored to the doc.

There's more — average time on page, top referrers, countries, device class, 30-day daily views. See analytics, heatmaps, and feedback for the full picture, or open your documents once you've published one.