Registering an exceptional 86/100 on the AI-Crawler Reality Index, iloom.com sits in the highest tier of AI extractability among indexed domains. Compared to other infrastructure sites (avg score: 57), iloom.com performs above the benchmark, suggesting strong competitive positioning in AI search. While the majority of content is server-rendered, the 15% ghost ratio suggests some content remains invisible to static crawlers. The 6.8× token bloat ratio falls within the normal range, though there is room to trim navigation, footer, and script overhead. Rich structured data (4 schema blocks) gives AI systems strong semantic signals for entity recognition and knowledge graph inclusion. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.
🧮 Score Transparency — How is this calculated?
📊 ACRI Sub-Scores (AI Readiness Detail)
iloom.com ranks much higher on Google (Tranco Top 22%) than in AI search (Top 1%). This is the 'Invisible Giant' pattern — implement the patches above to close the AI gap. ACRI measures technical crawler readiness. Read the methodology →
Why iloom.com ranks here
Fastest improvements
- Reduce token bloat (navigation/footer/code) so agents reach your main content faster (see Token Bloat).
- Create an
llms.txtfile so AI crawlers can discover your content structure without heavy crawling. Generate llms.txt → - Run a full entropy audit to find which DOM regions waste the most tokens. Run Entropy Audit →
Traditional SEO
38/100 25 % of Global Score 🟢 High Confidence📝 Title Tag
Optimal range: 30–60 characters for SERP display.
📋 Meta Description
Optimal range: 120–160 characters for snippet control.
🔤 Heading Hierarchy
- ✗ Exactly 1 <h1> tag — found 0
- ✓ Has <h2> headings — found 4
- ✗ <h2> not before <h1>
🔍 Indexability
- ✓ Canonical tag present →
https://www.iloom.com/ - ✓ No noindex directive
- ✓ Meta viewport set
- ✗ HTML lang attribute
- ✗ Hreflang tags
- ✓ Googlebot allowed by robots.txt
🌐 Social / OpenGraph
- ✓ og:title — 일룸 공식 홈페이지 | 일상에 새로운 설렘과 다채로운 가치를 더하는 일룸입니다.
- ✓ og:description — 일상에 새로운 기대감과 설렘을 더하기 위해 누구보다 다정하고 깊게, 한 발 앞서 고민합니다. 매 순간 진심을 다하는 일룸과 함께 보다 의미있고 다채로운 매일을 만들어보세요.
- ✓ og:image — preview
- ✓ twitter:card — summary_large_image
📐 How the SEO Pillar score is calculated
SEO Pillar = Title (20 pts) + Meta Desc (20 pts) + Heading Hierarchy (20 pts) + Indexability (20 pts) + Social/OG (20 pts)
Each sub-score is derived from the checks above. Canonical tag, lang attribute, og:image, and a single H1 are the highest-impact items.
AI Readiness / GEO
87/100 40 % of Global Score 🟢 High ConfidenceThis pillar aggregates citation share, hallucination risk, bot access, schema health, and content extractability. The individual diagnostic sections below contribute to this score.
Is AI lying about your brand? This panel measures how likely LLMs are to hallucinate facts when extracting information from your page.
🤖 Bot Access Matrix
👻 Rendering (Ghost Ratio) Docs
📊 Structure & Information Density Docs
🏷️ Schema Health Docs
Schema Coverage Map
📐 AI Efficiency Metrics Docs
Token Bloat Research
Multimodal Readiness
TDM Rights
🔥 Structural Entropy Check Research
🔬 AI-Crawler Simulation
See your website the way AI crawlers do. CSS stripped, structure labeled, content chunked.
Toggle to "AI Agent View" to see what GPTBot, ClaudeBot, and other AI crawlers actually extract from this page.
AI Answer Preview
NEWSee how AI models summarize your site. Left: your actual content. Right: what the LLM extracts and says about you.
🔧 Tech Stack
Performance & Speed
40/100 20 % of Global Score 🟢 High Confidence⏱️ Time to First Byte
Google considers <200 ms "good". AI crawlers may have even shorter timeouts.
📦 Page Weight
DOM nodes
HTML payload
🗄️ Cache & CDN
- ✗ Cache-Control header
- ✗ CDN cache status
- ✗ CDN detected
🔬 Tracker Tax
tracker scripts
third-party domains
token overhead
📐 How the Performance Pillar score is calculated
Perf Pillar = TTFB (35 pts) + Page Weight (25 pts) + Cache/CDN (20 pts) + Tracker Tax (20 pts)
TTFB <200 ms = full marks. DOM >3000 or payload >300 KB incurs heavy penalties. Tracker scripts beyond 5 reduce score.
Architecture & Trust
57/100 15 % of Global Score 🟢 High Confidence🗺️ Sitemap & Robots
- ✗ Sitemap declared in robots.txt
- ✓ Googlebot allowed
- ✓ GPTBot allowed
- ✓ ClaudeBot allowed
🔗 Linking
internal links
external links
🔒 Security & Trust
- ✓ HSTS header (Strict-Transport-Security)
- ✗ Content-Security-Policy header
- ✓ HTTP status 200 OK (got 200)
♿ Accessibility Signals
- ✗ HTML lang attribute
- ✓ Meta viewport for mobile
- ✗ Single H1 for screen readers
📐 How the Architecture Pillar score is calculated
Arch Pillar = Sitemap & Robots (30 pts) + Linking (25 pts) + Security (25 pts) + Accessibility (20 pts)
Having a valid sitemap, allowing AI bots, HSTS, and a good internal link count are the highest-impact items.
🏅 AI-Verified Trust Badge
Your site scores 72/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.
<a href="https://seodiff.io/radar/domains/iloom.com" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=iloom.com" alt="AI-Verified by SEODiff" width="280" height="52"></a>
💡 Paste in your site footer, GitHub README, or email signature. Badge updates automatically as your score changes.
🔗 Similar infrastructure Sites
Domains with a similar tech stack, industry, and AI readiness profile to iloom.com. Compare side-by-side.
| Domain | ACRI | AI Score | Tech Stack | Token Bloat | Schema | |
|---|---|---|---|---|---|---|
| iloom.com (this site) | 72 | 86 | Custom / Proprietary | 6.8× | 4 | — |
| quinyx.com | 73 | 80 | Custom / Proprietary | 6.6× | 4 | Compare → |
| congee.pl | 73 | 82 | Custom / Proprietary | 6.2× | 4 | Compare → |
| cmso.com | 70 | 80 | Custom / Proprietary | 6.6× | 4 | Compare → |
| softwarefreedomday.org | 70 | 81 | Custom / Proprietary | 6.3× | 4 | Compare → |
| kisanshop.in | 69 | 77 | Custom / Proprietary | 6.9× | 4 | Compare → |
Remediation Patches
COPY-PASTEAuto-generated code fixes tailored to iloom.com. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Iloom?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Add your answer here — describe what Iloom does in 1-2 sentences."
}
},
{
"@type": "Question",
"name": "How does Iloom work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Explain the key features and how users interact with Iloom."
}
}
]
}
</script>
Projected Impact
ROI EST.If you apply the patches above, here's the estimated improvement for iloom.com:
*Estimates based on SEODiff's scoring model. Actual results depend on implementation quality.
📋 Data Export
Download scores and metadata for audits, client reports, or CI/CD pipelines. Exports contain computed metrics only (no copyrighted content).
All data is generated automatically and updated with each crawl. JSON exports contain scores and metadata only (no copyrighted content).
Is this your company?
Monitor your AI visibility score weekly and get alerted when changes happen.
Start Free →