Share a ChatGPT or Claude HTML page in under a minute
The fastest path: copy the AI's output, paste or drop it into ilolink, pick who can see it, and get a link. Then open your dashboard and watch the first view land — readers need no account, and there's nothing to install.
How do I publish an AI page fast?
Five steps, most of them a paste and a click:
- Get one self-contained output from the AI — a single HTML file with its CSS inline, or a block of Markdown. One file, not a project split across assets. The cap is 15 MB per doc.
- Paste it, or drop the file, into the composer at ilolink.com. Publishing takes a free account — sign in once and you land straight on the composer.
- Pick a visibility mode — public, unlisted, private (teamspace members only), password-protected, or expiring. Expiry is opt-in.
- Copy your link. You get
ilolink.com/<slug>. Send it anywhere. - Open your dashboard and watch views and scroll come in as people read.
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: scripts and javascript: URLs are dropped, and no arbitrary JavaScript runs. Your CSS is kept, so a static landing-page mockup renders exactly as designed. 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 isolated origin. For the wider view, see share AI output as a real link, and check what ilolink accepts before you paste.
What you get back
The link is only half of it. Once the page is out, ilolink shows you how it 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 — live click and scroll maps, by device class.
- Feedback — reactions, short notes, and threaded comments anchored to the doc.
- Context — average time, top referrers, countries, device class, and 30-day daily views.
That's the loop: publish, share, and see how it landed. The full read-side picture is in analytics, heatmaps, and feedback.
Questions
- Do I need an account?
- To publish, yes — a free one. Sign in, paste or drop your file on the composer, and get a link. Readers don't need an account to open it.
- How long does it take?
- Under a minute. Most of the work is a paste and a click: paste the output, pick a visibility mode, and copy the link.
- 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.
- Does an interactive app stay interactive?
- Not by default. Uploaded HTML is sanitized on ingest, so an interactive app is shown frozen to its static state. But if you mark the doc trusted at publish time, it runs as-is inside a sandboxed frame on the isolated origin. Static CSS-styled pages render exactly as designed.
Try it on your own doc
Publish your first doc.