How to share Grok output as a page

Copy Grok's output into one self-contained file, paste or drop it into ilolink, and get a link at ilolink.com/<slug>. Readers need no account. Then see how it was read: views, scroll funnel, heatmaps, feedback. Grok gives you text, Markdown, or HTML — put it in one file.

Why not just send the Grok link or output?

Grok answers in text, Markdown, or HTML — a write-up, a spec, a styled page. None of that is a standalone page you can hand to someone. A raw .md or .html file doesn't render when you email it — it downloads, or shows as source. And a link back to the chat shares the thread, not a clean page: the reader lands in your conversation, not on the finished thing.

A hosted page fixes both. Copy the output into one self-contained file, publish it, and you get a real URL that opens and renders for anyone — and, on the other side, tells you how it was read.

How to publish Grok output

The loop is short:

  1. In Grok, copy the answer as Markdown, or the generated HTML with its CSS inline, into one self-contained file. Ask for a single file, not a project.
  2. Paste it, or drop the file, into the composer at ilolink.com.
  3. Pick a visibility mode — public, unlisted, private (teamspace members only), password, or expiring.
  4. 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: scripts are dropped and no arbitrary JavaScript runs. Inline CSS is kept, so a styled page renders as designed; inline <style> and Google Fonts work, but external stylesheets, relative asset paths, and http: images do not — use inline CSS and https/data: images. If Grok gave you something interactive, by default it's shown frozen to its static state rather than executing, and forms are inert — unless you mark the doc trusted at publish time, in which case it runs as-is inside a sandboxed frame on the isolated origin. The cap is 2 MB per doc.

What you learn after sharing

This is the part Grok doesn't give you. Once the link is out, ilolink shows 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 exactly how far readers got.
  • Heatmaps — click and scroll, viewable by device class.
  • Reactions, notes, and comments — readers can react, leave a short note, or thread a comment, no account.

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 start from share anything an AI made for the cross-tool version.

Questions

Do readers need an account to view it?
No. Anyone with the link can open the page — there's no login to view. Publishing is the other half: that needs a free account, and your docs live in your teamspace, reachable from any device you sign in on.
Is it free?
Yes, for one person — free for up to 3 published documents. Paste text, 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.
What if the Grok output has interactive JavaScript?
By default it's frozen to its static state — the CSS is kept so the layout looks right, but no arbitrary JavaScript runs, so an interactive page renders as a static snapshot, not a working app. If you mark the doc trusted at publish time, it runs as-is inside a sandboxed frame on the isolated origin instead.
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.

Try it on your own doc

Copy your Grok output into one file, pick who can see it, and get a link in seconds.

Publish your first doc

Keep reading