Who they are
Kubock is an AI studio for filmmakers: script, characters, scenes and a rough cut in one workspace. Built by filmmakers, genuinely useful, and built on Next.js. It scored a solid 85 for Google but only 54 for AI.
That was the strange part. Kubock had already done the work: structured data, an FAQ, a guide. In the browser it was all there. The scan still said AI could barely tell what Kubock was or who it was for.
What the scan found
The scan reads a page the way Google and AI crawlers do: the raw HTML, before any JavaScript runs. That is exactly where the gap was. Kubock's schema and FAQ were being drawn by JavaScript in the browser, so a person saw them, but a crawler fetching the page got an almost empty shell. The signals existed; they just were not in what the machines actually read.
- Structured data visible on screen but missing from the raw HTML
- FAQ and answers rendered by JavaScript, invisible to AI crawlers
- A homepage that, to a machine, barely said what Kubock is
The result
The fix was not writing new content, it was serving the content that already existed where machines can see it: rendering the schema and the key copy on the server, in the HTML itself, instead of painting them in after the page loads.
The re-scan told the story. AEO jumped from 54 to 95, with SEO steady at 85. Same site, same content, now actually readable by the engines people ask. For framework sites this is the quiet killer: your signals can be perfect and still invisible if they only exist once the JavaScript has run.