Directory · Web data and extraction
Firecrawl — what a crawler receives from firecrawl.dev
Website measurement, not a product review. This page records what machine clients received from firecrawl.dev. It does not evaluate Firecrawl software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 63/100, measured 2026-10-06 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.
3
findings
✓
llms.txt on its host
✗
entity map on its host
6
scans on record since 2026-09-02
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.
- Structured data43
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals75
- Linked datan/a
- Quotable content40
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is read, 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
1The homepage depends on files this site's own robots.txt disallows40 render resources referenced by the homepage are disallowed to every crawler by this site's own robots.txt: /_next/static/chunks/0t-zvozl5h7qf.css (/_next/staMediumSetting
What we saw
40 render resources referenced by the homepage are disallowed to every crawler by this site's own robots.txt: /_next/static/chunks/0t-zvozl5h7qf.css (/_next/static/), /_next/static/chunks/2wkqjoezjesq6.css (/_next/static/), /_next/static/chunks/1cy6_hohvklxq.css (/_next/static/), /_next/static/chunks/36vau4m3pbz-h.css (/_next/static/). A crawler that obeys robots.txt will not fetch these, so it renders the page without them. /robots.txt
Why it matters
Googlebot renders pages, and a stylesheet or script it is forbidden to fetch is rendered without. Layout, visibility and any content a script inserts are then judged from a page the site never intended to show. Only rules in the * group count here - a rule aimed at one named crawler is a narrower question.
How to fix it
Allow crawlers to fetch the CSS and JavaScript the page depends on. Remove the Disallow rules covering those paths, or serve the content without them.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
Why this was decided
| Rule | RENDER_RESOURCE_BLOCKED · rule pack sv28 · scope route |
|---|---|
| Evaluated | 2026-10-06 19:18:02 UTC |
| Decision | d1:34d36e6ad305927dcdb6 · finding f1:92f244157568be17c846 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 83491b85 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 1,195,457 | 43da8782280c | kept |
| read: /robots.txt | 200 | 400 | 0496db1c1c61 | kept |
20 more in the manifest.
Artifacts: manifest:46bb1cea4cedaaf4a7e0ff06069086be93bc9304061950b6c3837b39e3acfea5
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 RENDER_RESOURCE_BLOCKED under scoring rules v28 · fingerprint RENDER_RESOURCE_BLOCKED|/robots.txt · persisting (7 scans)
Verify the fix Re-scan after the change. This finding is cleared when RENDER_RESOURCE_BLOCKED is no longer reported at /robots.txt; if it comes back after clearing, it is marked a regression, not a new finding.
RENDER_RESOURCE_BLOCKED · 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 firecrawl.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 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 1,195,390 decompressed bytes the homepage delivers, 1.8% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 1.8% · 21,908 B
- Markup & attributes 21.5% · 256,733 B
- Inline CSS 0.9% · 10,632 B
- Inline JavaScript 36.4% · 435,265 B
- Inline SVG 39.3% · 469,742 B
- HTML comments 0.1% · 1,110 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline SVG · 22,504 B (1.9%) —
.size-28opens<g><g transform=" translate(293.035, 553.013) scale(0.97724, 0.97724) - Inline SVG · 22,430 B (1.9%) —
.size-28opens<g><g transform=" translate(293.035, 553.013) scale(0.97724, 0.97724) - Inline SVG · 22,430 B (1.9%) —
.size-24opens<g><g transform=" translate(293.035, 553.013) scale(0.97724, 0.97724) - Inline SVG · 22,430 B (1.9%) —
.size-24opens<g><g transform=" translate(293.035, 553.013) scale(0.97724, 0.97724) - Inline SVG · 22,430 B (1.9%) —
.size-28opens<g><g transform=" translate(293.035, 553.013) scale(0.97724, 0.97724)
What changed
- 2026-10-06resolved: the hsts header asks for browser preloading but does not qualify for itresolved
- 2026-10-02score moved 60 → 62score-up
- 2026-10-02a new finding appeared: the hsts header asks for browser preloading but does not qualify for it againreturned
- 2026-09-21resolved: the hsts header asks for browser preloading but does not qualify for itresolved
- 2026-09-18a new finding appeared: the machine files cost more than the pageappeared
- 2026-09-18a new finding appeared: the hsts header asks for browser preloading but does not qualify for itappeared
6 scans on record, first 2026-09-02. 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 firecrawl.devIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If firecrawl.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 “Web data and extraction” is our label for what the product is primarily sold as; it is not scored. Back to the directory.