Directory · AI visibility monitoring
Profound — what a crawler receives from profound.dev
Website measurement, not a product review. This page records what machine clients received from profound.dev. 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 62/100, measured 2026-10-04 15:17 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.
4
findings
✗
llms.txt on its host
✗
entity map on its host
5
scans on record since 2026-09-18
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 delivered HTML is mostly content, and the machine files point at the rest.
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 data0
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals0
- Linked datan/a
- Quotable contentn/a
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is quote, because the three run in order.
What to fix
4 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 2 Note
1robots.txt declares no sitemapNo Sitemap: directive present.MediumSetting
What we saw
No Sitemap: directive present. /robots.txt
Why it matters
Adding one Sitemap: line lets crawlers enumerate the site instead of guessing at it.
How to fix it
Add a Sitemap: line to robots.txt pointing at the full sitemap URL, so crawlers find it without guessing.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
Why this was decided
| Rule | ROBOTS_NO_SITEMAP · rule pack sv27 · scope core |
|---|---|
| Evaluated | 2026-10-04 15:17:38 UTC |
| Decision | d1:0aaafb096bd8b8abadb0 · finding f1:64df496fbceaccab6a91 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: /robots.txt | 200 | 28 | 3bb00d50e6a7 | already_held |
21 more in the manifest.
Artifacts: manifest:d12173fcc84da834d3e5dd0c345d3dbca0dbbdfb26077f5564792747444a0f54
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 ROBOTS_NO_SITEMAP under scoring rules v28 · fingerprint ROBOTS_NO_SITEMAP|/robots.txt · persisting (2 scans)
Verify the fix Re-scan after the change. This finding is cleared when ROBOTS_NO_SITEMAP is no longer reported at /robots.txt; if it comes back after clearing, it is marked a regression, not a new finding.
ROBOTS_NO_SITEMAP · full transcript
Open the other 3
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 4 findings on profound.dev. $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 sitemap. 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 89,373 decompressed bytes the homepage delivers, 1.1% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 1.1% · 982 B
- Markup & attributes 29.4% · 26,283 B
- Inline CSS 56% · 50,085 B
- Inline JavaScript 1.3% · 1,145 B
- Inline SVG 12.2% · 10,878 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 24,571 B (27.5%) — embedded web fontsopens
/* cyrillic */ @font-face { font-family: 'Playfair Display'; font-styl - Inline SVG · 10,878 B (12.2%) — unnamedopens
<g><path fill="evenodd" d="M19.3748 0.914408C17.0406 -0.544155 13.967 - Inline CSS · 7,862 B (8.8%) — unnamedopens
.x .c1-1{letter-spacing:normal}.x .c1-2{text-transform:none}.x .c1-3{b - Inline CSS · 5,977 B (6.7%) — unnamedopens
@media (max-width: 450px){.x .c1-11{background-image:linear-gradient(t - Inline CSS · 3,964 B (4.4%) — unnamedopens
.x{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%;-webkit-tap
What changed
- 2026-09-27robots.txt no longer named a sitemapappeared
- 2026-09-27the homepage read as mostly markupappeared
- 2026-09-27no llms.txt was foundappeared
- 2026-09-27a new finding appeared: the machine files cost more than the pageappeared
5 scans on record, first 2026-09-18. 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 profound.devIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If profound.dev 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.