Directory · Web data and extraction
Voyage AI — what a crawler receives from voyageai.com
Website measurement, not a product review. This page records what machine clients received from voyageai.com. It does not evaluate Voyage AI software, features, pricing or support.
Answer engines are being served something other than this site.
AI visibility 81/100, measured 2026-10-05 12:18 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can reach and read this site. What is left is giving it something specific to say.
Held at D A high-severity finding sets the letter.
5
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 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 data57
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals50
- Linked datan/a
- Quotable content100
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is quote, because the three run in order.
What to fix
5 findings on this site, 3 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 High 2 Medium 2 Note
1No XML sitemap foundNo sitemap at any conventional path and none declared.HighDeveloper
What we saw
No sitemap at any conventional path and none declared.
Why it matters
Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found.
How to fix it
Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt.
Developer: a template, theme or application change — a developer touches it
On Next.js (detected)
- App Router: app/sitemap.ts returning MetadataRoute.Sitemap, one entry per URL with lastModified set to the content's real change date.
- Reference it from app/robots.ts (sitemap field) so crawlers find it.
Why this was decided
| Rule | NO_SITEMAP_FOUND · rule pack sv27 · scope core |
|---|---|
| Evaluated | 2026-10-05 12:18:03 UTC |
| Decision | d1:9549b941ac0e627e7991 · finding f1:038fb2cfbb23c11512d2 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: /sitemap.xml | 404 | 12,820 | 0ffcd7926b9f | already_held |
| read: /sitemap_index.xml | 404 | 12,820 | 0ffcd7926b9f | already_held |
| read: /wp-sitemap.xml | 404 | 12,820 | 0ffcd7926b9f | already_held |
21 more in the manifest.
Artifacts: manifest:68f0ced437548a6b2e3073266cbc5b129b89c74e353ab815106592f38c3489bb
Grade effect Caps the letter at D. Without it the letter would be C (score 81). Moves no points; the score is built from the measured rows.
Rule NO_SITEMAP_FOUND under scoring rules v31 · fingerprint NO_SITEMAP_FOUND|/ · persisting (5 scans)
Verify the fix Re-scan after the change. This finding is cleared when NO_SITEMAP_FOUND is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
NO_SITEMAP_FOUND · full transcript
Open the other 4
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 5 findings on voyageai.com. $749, once.
3 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 174,268 decompressed bytes the homepage delivers, 1.5% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 1.5% · 2,547 B
- Markup & attributes 12.7% · 22,045 B
- Inline JavaScript 36.4% · 63,466 B
- Inline SVG 49.5% · 86,176 B
- HTML comments 0% · 34 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline JavaScript · 38,258 B (22%) — unnamedopens
self.__next_f.push([1,"0:[\"$\",\"$Lb\",null,{\"buildId\":\"JebAKZ1K7- - Inline SVG · 28,578 B (16.4%) —
.h-fullopens<defs><radialGradient id="cursorRevealGradient"><stop offset="0%" stop - Inline SVG · 12,180 B (7%) —
.mx-autoopens<g clip-path="url(#clip0_531_2287)"><path d="M116.485 41.1088C101.218 - Inline SVG · 10,527 B (6%) —
.h-fullopens<path d="M325.24 1287.41C347.14 1279.25 369.53 1272.43 392.27 1266.99L - Inline SVG · 5,865 B (3.4%) —
.text-spring-greenopens<path d="M35.0157 32.0543H34.0915L33.874 31.8368L26.6161 14.9561C26.45
What changed
- 2026-10-02score moved 65 → 77score-up
- 2026-09-19a stale edge copy was servedappeared
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 voyageai.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If voyageai.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 “Web data and extraction” is our label for what the product is primarily sold as; it is not scored. Back to the directory.