crawlable.synthworx.com
Scanned Fri, 31 Jul 2026 16:41:41 GMT · https://crawlable.synthworx.com/repros/2026-07-31-wasm-table/index.html
AI assistants cannot properly read this site
95% of your page content only exists after JavaScript runs
Send this to whoever can deploy the fix
We’ll email the full findings plus a prioritised fix checklist for crawlable.synthworx.com. Access failures come first, followed by response-content and structure fixes. No account needed.
Initial response and browser render
Word counts of readable text before and after browser execution. The gap is a rendering dependency, not a claim about every vendor’s crawler behavior.
Crawler access
Live requests were sent with each vendor’s published user-agent string. This tests how the site handles the claimed identity; a user-agent alone does not authenticate the vendor. A robots.txt pass with a failed request points to another access control.
| Crawler | Vendor | Role | robots.txt | Live request |
|---|---|---|---|---|
| GPTBot | OpenAI | Training | Allowed | HTTP 200 |
| OAI-SearchBot | OpenAI | Search indexretrieval | Allowed | HTTP 200 |
| ChatGPT-User | OpenAI | Live fetchretrieval | Allowed | not probed |
| ClaudeBot | Anthropic | Training | Allowed | HTTP 200 |
| Claude-SearchBot | Anthropic | Search indexretrieval | Allowed | not probed |
| Claude-User | Anthropic | Live fetchretrieval | Allowed | not probed |
| PerplexityBot | Perplexity | Search indexretrieval | Allowed | HTTP 200 |
| Perplexity-User | Perplexity | Live fetchretrieval | Allowed | not probed |
| Google-Extended | Training | Allowed | not probed | |
| Applebot-Extended | Apple | Training | Allowed | not probed |
| meta-externalagent | Meta | Training | Allowed | not probed |
| Amazonbot | Amazon | Search index | Allowed | not probed |
| Bytespider | ByteDance | Training | Allowed | not probed |
| CCBot | Common Crawl | Training | Allowed | not probed |
Findings (4)
1 critical access or response issue found in this scan.
95% of your page content only exists after JavaScript runs
- Evidence
- Raw HTML contains 16 words. After rendering, the page contains 341 words.
- Why it matters
- No major AI crawler executes JavaScript — GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot and PerplexityBot all read raw HTML only. Google renders JS, so this site can rank normally in Google search while being close to blank in ChatGPT, Claude and Perplexity. That gap is invisible in Google Search Console.
- Fix
- Serve the primary content in the initial HTML response via server-side rendering, static generation, or prerendering for crawler user-agents. Verify with `curl` — if the content is not in the raw response, AI crawlers do not have it.
No structured data on the homepage
- Evidence
- No JSON-LD blocks and no microdata found.
- Why it matters
- Structured data is how a machine learns your entity name, what you sell, where you operate and how to contact you, without inferring it from prose. Without it, assistants are more likely to describe you vaguely or confuse you with a similarly named company.
- Fix
- Add JSON-LD for Organization (name, url, logo, sameAs, description) plus the type matching the page — Product, Service, LocalBusiness or Article.
No question-shaped content
- Evidence
- No question headings and no FAQPage schema found.
- Why it matters
- Assistants answer questions. Pages organised as explicit question/answer pairs are markedly easier to retrieve and quote than undifferentiated marketing prose.
- Fix
- Add a server-rendered FAQ section using the real questions prospects ask, marked up with FAQPage schema.
Missing meta description
- Evidence
- No meta[name="description"] in the raw HTML.
- Why it matters
- Removes a concise, author-controlled summary that assistants frequently reuse verbatim.
- Fix
- Add a 140–160 character description stating what the business does.
Get these fixed and keep them fixed
The diagnosis stays free. Paid plans generate reviewable robots.txt, JSON-LD and llms.txt artifacts, then re-scan on schedule and email you when a check regresses.