Directory · Voice, speech and transcription
AssemblyAI — what a crawler receives from assemblyai.com
Website measurement, not a product review. This page records what machine clients received from assemblyai.com. It does not evaluate AssemblyAI software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 74/100, measured 2026-09-18 01:17 UTC from outside its network, as twelve named crawler identities plus an unnamed client and two mobile-browser controls. An engine can technically reach this site and would struggle to get anything quotable out of it.
1
finding
✓
llms.txt on its host
✗
entity map on its host
1
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 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 read, because the three run in order.
What to fix
1 finding on this site. The top one is below in full, free. Want it fixed for you? We implement it and re-measure.
1 Note
1The machine files cost more than the pageThe machine files a crawler reads before the page total 217,225 bytes, 1.17x the homepage HTML (185,167 B); the heaviest are /sitemap.xml 212,865 B, /llms.txt 3Note
What we saw
The machine files a crawler reads before the page total 217,225 bytes, 1.17x the homepage HTML (185,167 B); the heaviest are /sitemap.xml 212,865 B, /llms.txt 3,959 B, /robots.txt 401 B.
Why it matters
A crawler reads robots.txt, the sitemap, llms.txt and the agent files before the first page, and pays for every 404 that answers with a full page. Keep machine files as small as their job allows and serve absent paths with a short 404 body.
How to fix it
Read the evidence below, then change what the server sends at that path. Re-scan to confirm: done is measured, not asserted.
MACHINE_CHAIN_HEAVY · full transcript
Or 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 1 finding on assemblyai.com. $749, once.
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 entity graph. 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 185,085 decompressed bytes the homepage delivers, 6% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 6% · 11,183 B
- Markup & attributes 66.8% · 123,638 B
- Inline CSS 5.5% · 10,266 B
- Inline JavaScript 18.5% · 34,210 B
- Inline SVG 1.9% · 3,426 B
- HTML comments 1.3% · 2,362 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 5,142 B (2.8%) — unnamedopens
.scrollbar-hide[data-astro-cid-zdfrvv5v]{-ms-overflow-style:none;scrol - Inline JavaScript · 4,420 B (2.4%) — unnamedopens
(()=>{var g=Object.defineProperty;var w=(c,s,d)=>s in c?g(c,s,{enumera - Inline JavaScript · 4,014 B (2.2%) — unnamedopens
(function () { var PRODUCTION_ORIGIN = 'https://www.assemblyai.com'; v - Inline JavaScript · 3,215 B (1.7%) — unnamedopens
var v=()=>{window.va||(window.va=function(...i){window.vaq||(window.va - Inline JavaScript · 2,856 B (1.5%) — unnamedopens
var p=()=>{window.si||(window.si=function(...r){window.siq=window.siq|
What changed
No change recorded between the readings on file yet.
1 scan 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 assemblyai.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If assemblyai.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 “Voice, speech and transcription” is our label for what the product is primarily sold as; it is not scored. Back to the directory.