Directory · AI visibility monitoring
Profound — what a crawler receives from tryprofound.com
Website measurement, not a product review. This page records what machine clients received from tryprofound.com. It does not evaluate Profound software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 71/100, measured 2026-10-05 19:18 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
20
scans on record since 2026-08-16
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?
Every named crawler was served the same page a browser gets.
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.
- Structured data43
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals0
- Linked datan/a
- Quotable content60
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is quote, because the three run in order.
What to fix
3 findings on this site, 1 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.
1 Medium 2 Note
1Almost nothing a machine receives from this page is readable text1.4% of 529,175 decompressed bytes is visible text, and the largest single block is inline javascript at 75,671 bytesMediumDeveloper
What we saw
1.4% of 529,175 decompressed bytes is visible text, and the largest single block is inline javascript at 75,671 bytes
Why it matters
A crawler pays for every byte it fetches and can only quote the text. Under 5% readable content means an answer engine downloads the whole page and comes away with almost nothing it can use — the difference between being quotable and being skipped. The content-ratio row above passes at 20%, so without this a page at 2% and a page at 19% were scored identically.
How to fix it
Move inline CSS and JavaScript into external files, drop unused page-builder styling, and make sure the words a visitor reads are in the HTML itself.
Developer: a template, theme or application change — a developer touches it
Why this was decided
| Rule | PAGE_IS_MOSTLY_CODE · rule pack sv27 · scope route |
|---|---|
| Evaluated | 2026-10-05 19:18:56 UTC |
| Decision | d1:e1a57e2e913e63724829 · finding f1:ba9dca68e23e1f86de75 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 71386c1f · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 529,396 | 3bc13b316374 | kept |
21 more in the manifest.
Artifacts: manifest:282aa667c938ff9d88f985f84521c2781913b414099e5c4241670f8b8a1fd068
Grade effect Caps the letter at C. Without it the letter would be B (score 71). Moves no points; the score is built from the measured rows.
Rule PAGE_IS_MOSTLY_CODE under scoring rules v28 · fingerprint PAGE_IS_MOSTLY_CODE|/ · persisting (24 scans)
Verify the fix Re-scan after the change. This finding is cleared when PAGE_IS_MOSTLY_CODE is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
PAGE_IS_MOSTLY_CODE · 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 tryprofound.com. $749, once.
1 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 llms.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 529,175 decompressed bytes the homepage delivers, 1.4% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 1.4% · 7,466 B
- Markup & attributes 59.8% · 316,659 B
- Inline JavaScript 26.4% · 139,753 B
- Inline SVG 12.2% · 64,815 B
- HTML comments 0.1% · 482 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline JavaScript · 75,671 B (14.3%) — unnamedopens
self.__next_f.push([1,"1:\"$Sreact.fragment\"\n2:I[12985,[\"/_next/sta - Inline JavaScript · 28,014 B (5.3%) — unnamedopens
self.__next_f.push([1,"32:[\"$\",\"section\",null,{\"aria-labelledby\" - Inline JavaScript · 13,370 B (2.5%) — unnamedopens
self.__next_f.push([1,"7b:[[\"$\",\"div\",null,{\"className\":\"relati - Inline JavaScript · 10,507 B (2%) — unnamedopens
self.__next_f.push([1,"78:I[414867,[\"/_next/static/immutable/chunks/4 - Inline SVG · 6,201 B (1.2%) — unnamedopens
<path d="M0 4a4 4 0 0 1 4-4h8a4 4 0 0 1 4 4v8a4 4 0 0 1-4 4H4a4 4 0 0
What changed
- 2026-10-05a new finding appeared: the machine files cost more than the pageappeared
- 2026-09-16score moved 77 → 75score-down
- 2026-09-15score moved 76 → 77score-up
- 2026-09-07score moved 72 → 73score-up
20 scans on record, first 2026-08-16. 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 tryprofound.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If tryprofound.com 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 “AI visibility monitoring” is our label for what the product is primarily sold as; it is not scored. Back to the directory.