Directory · Content and GEO
Alli AI — what a crawler receives from alli.ai
Website measurement, not a product review. This page records what machine clients received from alli.ai. It does not evaluate Alli AI software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 70/100, measured 2026-10-09 14:22 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can technically reach this site and would struggle to get anything quotable out of it.
Held at C A medium-severity finding sets the letter.
3
findings
✗
llms.txt on its host
✗
entity map on its host
7
scans on record since 2026-09-17
The three stages, in the order an engine hits a site
Each stage gates the next. An engine that cannot reach a page never reads it; one that cannot read it never quotes it. That is why reach is a ceiling and not just a weight.
Stage 1 · 40% of the score
Reach
Can a named answer-engine crawler get your pages at all?
At least one answer engine was refused, challenged or served less than a browser.
Stage 2 · 30% of the score
Read
Once it has the bytes, can it find the words?
The content is buried in markup, or the files that guide a crawler are missing.
Stage 3 · 30% of the score
Quote
Is there a specific fact it can state and attribute?
An assistant would have to paraphrase your page instead of quoting a fact.
The stage to fix first is quote, because the three run in order.
What to fix
3 findings on this site, 2 of them scored serious. Every one is named below; the top one is shown in full, free. What we saw, why each matters, how to fix it and the bytes behind it are what a licence buys — or we implement the whole list for you.
2 Medium 1 Note
1Two business records on this page claim the same identity1 identity collision in this page's structured data: two nodes share the same url.MediumDeveloper
What we saw
1 identity collision in this page's structured data: two nodes share the same url.
Why it matters
A system resolving which business this page is about has more than one candidate for one identity. Two LocalBusiness or Organization nodes sharing a phone number, an @id or a coordinate pair give a retrieval system no way to decide which record is the entity, so it may pick either or neither. This reads only what the page declares - it does not assert the business is duplicated or wrongly located.
How to fix it
Merge the duplicate business nodes into one, keep a single @id, and remove any plugin that emits a second empty LocalBusiness record.
Developer: a template, theme or application change — a developer touches it
On Webflow (detected)
- Page settings → Custom code → Inside <head> tag: one <script type="application/ld+json"> block; site-wide markup goes in Site settings → Custom code.
Why this was decided
| Rule | ENTITY_COLLISION · rule pack sv28 · scope route |
|---|---|
| Evaluated | 2026-10-09 14:22:31 UTC |
| Decision | d1:48d35d18bfa206edaf66 · finding f1:9fde3481f1565f0dc037 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 9a7fa5f9 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 425,639 | 766c0dfe8ef6 | write_unconfirmed |
23 more in the manifest.
Artifacts: manifest:14623cdc44c70dc33b4ea19c47ea588e9ad0d8e9bdfc7045908b1a3149199293
Grade effect Caps the letter at C together with 1 other medium-severity finding; the letter rises only when all of them are gone. Moves no points.
Rule ENTITY_COLLISION under scoring rules v31 · fingerprint ENTITY_COLLISION|/ · persisting (7 scans)
Verify the fix Re-scan after the change. This finding is cleared when ENTITY_COLLISION is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
ENTITY_COLLISION · full transcript
Open the other 2
What we saw, why it matters, how to fix it, and the evidence bytes for every finding — on this report and every re-scan. From $29 a month.
Unlock the findingsOr have them fixed
We implement the list on your site and re-measure, with a sealed before and after. One site, $749 once.
Get this fixed — $749The main product
We fix the 3 findings on alli.ai. $749, once.
2 of them are scored serious. One site. You keep the grade for free — this is the part where the list stops being a list.
- Every finding implemented on the site itself: machine files, schema, NAP, the lot
- An entity map authored for your business, not a template with the name swapped
- Measured again afterwards — the before and the after, sealed, so it is evidenced rather than claimed
- Thirty days of monitoring included
- Work starts within two business days
What it covers · one payment, nothing recurring
The chain a crawler follows
The chain breaks at robots.txt. Everything after that point is only reachable by a crawler guessing the conventional path.
A machine file that does not parse is worth less than one that is absent, because it looks present. Rows behind this.
Where the bytes go
Of the 407,455 decompressed bytes the homepage delivers, 3.7% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 3.7% · 14,885 B
- Markup & attributes 9.5% · 38,615 B
- Structured data (JSON-LD) 2.9% · 11,840 B
- Inline CSS 59.6% · 242,746 B
- Inline JavaScript 20.5% · 83,349 B
- Inline SVG 1.7% · 7,070 B
- HTML comments 2.2% · 8,950 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 42,507 B (10.4%) — unnamedopens
.ps-cite strong{color:var(--ac);font-weight:800} /* Answer — 채팅 버블 */ - Inline CSS · 41,608 B (10.2%) — unnamedopens
/* ============================================================ v4.2 P - Inline CSS · 41,531 B (10.2%) — unnamedopens
.rag-insight-grid.four .rag-insight-val{font-size:14px} .rag-insight-t - Inline JavaScript · 40,499 B (9.9%) — a framework state payloadopens
(() => { 'use strict'; const reducedMotion = window.matchMedia('(prefe - Inline CSS · 33,808 B (8.3%) — unnamedopens
@media(max-width:900px){ .footer-col{border-bottom:1px solid var(--bd)
What changed
- 2026-10-05a stale edge copy was served againreturned
- 2026-10-02score moved 66 → 70score-up
- 2026-10-02the stale edge copy clearedresolved
- 2026-09-20a stale edge copy was served againreturned
- 2026-09-18the stale edge copy clearedresolved
7 scans on record, first 2026-09-17. Score movements are shown only between readings taken under the same score version; finding codes are comparable across all of them.
Is this your site?
This listing reads the public record. Claim it and Watch keeps that record on your terms: every list this page holds back, finding age, and twice-daily re-measurement. Free for 30 days, no card.
Claim the record for alli.aiIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If alli.ai is yours you can prove it in a minute and for nothing — a DNS TXT record or one meta tag on the home page, both checkable by anyone.
Claiming marks you as the verified owner and lets you correct the category and the company name. It moves no score, no rank and no position.
Claim this listing — free or ask about a verified profile
Dispute or re-scan
If a reading here is wrong, it is our instrument that is wrong, and we want to know. Tell us what is wrong and the site is re-measured; the result is published as measured. Nothing about a listing, a payment or a request changes a number.
By email instead: hello@crawlcheck.io. Category “Content and GEO” is our label for what the product is primarily sold as; it is not scored. Back to the directory.