ilolink help center
Quick fixes for the most common issues: a page that looks broken once hosted, images that don't load, and files over the 15 MB cap — plus where to get the most from your analytics. Start with the fix that matches what you're seeing.
Most problems come from one thing: a published page has to be self-contained. It's served on an isolated origin under a strict content-security policy. Inline <style> and Google Fonts (fonts.googleapis.com stylesheets, fonts.gstatic.com files) work; so do https:// and data: images. Other external stylesheets and scripts, author JavaScript, relative asset paths, and http:// images are blocked and render broken. The three articles below cover the cases that actually come up.
Common fixes
- My HTML looks broken once hosted — a blocked CDN stylesheet or script; ask the AI for one self-contained file with inline CSS.
- My images don't load — relative paths and
http://URLs are blocked; use absolutehttps://ordata:images. - My file is over 15 MB — the per-doc cap; trim it, split it, or share the key part.
Getting more from ilolink
- Quick-start: publish in a minute — paste or drop your output, pick who can see it, get a link.
- Reading your analytics — what views, uniques, scroll depth, and heatmaps actually tell you.
- What ilolink can do — the full list of what's live, from visibility controls to feedback.
Questions
- Why does my page look different once hosted?
- It's served on an isolated origin under a strict content-security policy. Inline styles and Google Fonts still work, but a page that pulled other external stylesheets or scripts — or used relative asset paths or http:// images — renders broken. The fix is one self-contained file with inline CSS and absolute https assets.
- Is there a size limit?
- Yes — 15 MB per doc. That covers most write-ups, specs, HTML pages, and inline images. If it's bigger, trim it, split it, or share the key part.
Try it on your own doc
Publish a doc and see it live.