CrawlCheck

Directory · Video and image generation

VEED — what a crawler receives from veed.io

Website measurement, not a product review. This page records what machine clients received from veed.io. It does not evaluate VEED software, features, pricing or support.

87
Cgrade

Answer engines can reach and read this site. It needs more it can quote.

AI visibility 87/100, measured 2026-09-18 03:19 UTC from outside its network, as twelve named crawler identities plus an unnamed client and two mobile-browser controls. An engine can reach and read this site. What is left is giving it something specific to say.

Held at C A medium-severity finding sets the letter.

Open the full report veed.io ↗

7

findings

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.

96

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.

75

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.

88

Stage 3 · 30% of the score

Quote

Is there a specific fact it can state and attribute?

The facts an assistant is asked for are declared and consistent.

The stage to fix first is read, because the three run in order.

What to fix

7 findings on this site, 4 of them scored serious. The top one is below in full, free. Which the other 6 are, what we saw, and the bytes behind each one are what a licence buys — or we implement the whole list for you.

4 Medium 3 Note

1robots.txt rules do not apply to named agents1 named User-agent group (1 agent) do not repeat 7 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignores `*`MediumSetting

What we saw

1 named User-agent group (1 agent) do not repeat 7 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignores `*` entirely, so those rules do not apply to any of the named agents. Worst group: `oai-adsbot` bypasses /cdn-cgi/, /api/v1, /api/v2, /api/graphql, /login$, /signup$, /new$. /robots.txt

Why it matters

A crawler reads only the User-agent group that matches it best and ignores every other group, including `*`. Naming an agent and giving it only `Allow: /` therefore deletes all of your `*` Disallow rules for that agent. The file still parses and the agent still reaches your homepage, so this is invisible on inspection — but the paths you meant to keep out of search are open, and search engines will crawl and may index them.

How to fix it

Every User-agent group that names a crawler must repeat the Disallow rules you want applied. A named group with no rules means 'allow everything' for that crawler.

Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing

ROBOTS_RULES_SHADOWED · full transcript

2🔒 Medium finding, held backMedium
3🔒 Medium finding, held backMedium
4🔒 Medium finding, held backMedium
5🔒 Note finding, held backNote
6🔒 Note finding, held backNote
7🔒 Note finding, held backNote

See the other 6

Every finding, what we saw, why it matters, how to fix it, and the evidence bytes — on this report and every re-scan. From $29 a month.

Unlock the findings

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 — $749

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.

robots.txtEvery crawler reads this first
sitemapNamed in robots.txt and resolves
llms.txtPoints onward, links stay on this host
entity graphParses as JSON and points home

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 895,682 decompressed bytes the homepage delivers, 1.3% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 1.3% · 11,673 B
  • Markup & attributes 16.3% · 145,830 B
  • Structured data (JSON-LD) 0.2% · 1,702 B
  • Inline CSS 0% · 280 B
  • Inline JavaScript 79.1% · 708,446 B
  • Inline SVG 3.1% · 27,383 B
  • HTML comments 0% · 368 B

The individual blocks that weigh the most, so the fix is a search rather than a hunt:

  • Inline JavaScript · 702,538 B (78.4%) — a framework state payloadopens {"props":{"pageProps":{"navbarV2Data":{"items":[{"type":"dropdown","ti

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 veed.io

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If veed.io 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 “Video and image generation” is our label for what the product is primarily sold as; it is not scored. Back to the directory.