Directory · Content and GEO
Byword — what a crawler receives from byword.ai
Website measurement, not a product review. This page records what machine clients received from byword.ai. It does not evaluate Byword software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 69/100, measured 2026-10-09 21:19 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
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 data43
- 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
3 findings on this site, 1 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 Medium 1 Low 1 Note
1The page’s content only exists after JavaScript runsThe server delivered 9 words of readable text and a React mount point that is empty in the HTML. Everything a visitor sees is built by JavaScript after this resMediumDeveloper
What we saw
The server delivered 9 words of readable text and a React mount point that is empty in the HTML. Everything a visitor sees is built by JavaScript after this response.
Why it matters
The HTML the server sends is an application shell: a framework mount point and a script bundle, with almost no readable text. A browser runs the bundle and the page appears. A crawler that does not execute JavaScript — which is most AI crawlers and every training-data fetch — receives the shell and quotes nothing. This is measured on the bytes the server delivered, not on a rendered view; a framework by itself is not the defect, an empty delivery is.
How to fix it
Render the page on the server or at build time (Next.js/Nuxt/SvelteKit SSR or SSG, or a prerender step) so the delivered HTML already contains the text. Check by fetching the page with curl: the words a crawler needs must be in that response.
Developer: a template, theme or application change — a developer touches it
On Webflow (detected)
- Remove unused interactions and custom code embeds; Webflow's own runtime cannot be reduced.
- Put the main text in the page itself, not in elements filled by script.
Why this was decided
| Rule | CONTENT_NEEDS_JAVASCRIPT · rule pack sv28 · scope route |
|---|---|
| Evaluated | 2026-10-09 21:19:04 UTC |
| Decision | d1:1523def7446cc509e821 · finding f1:204751a997c088661e14 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build bbe60e38 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 4,357 | ae6c19652699 | kept |
21 more in the manifest.
Artifacts: manifest:32178ba03ba26923281bcee8585bb32d61d44e2c7629d97befbe7d49ab357db3
Grade effect Would cap the letter at C, but the score (69) already reads C, so the letter is the same without it. Moves no points.
Rule CONTENT_NEEDS_JAVASCRIPT under scoring rules v31 · fingerprint CONTENT_NEEDS_JAVASCRIPT|/ · persisting (6 scans)
Verify the fix Re-scan after the change. This finding is cleared when CONTENT_NEEDS_JAVASCRIPT is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
CONTENT_NEEDS_JAVASCRIPT · 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 byword.ai. $749, once.
1 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 4,351 decompressed bytes the homepage delivers, 1% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 1% · 43 B
- Markup & attributes 91.3% · 3,973 B
- Inline JavaScript 1.7% · 75 B
- HTML comments 6% · 260 B
What changed
No change recorded between the readings on file yet.
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 byword.aiIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If byword.ai 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 “Content and GEO” is our label for what the product is primarily sold as; it is not scored. Back to the directory.