Insights
Notes from real projects.
How we build fast 3D websites, web platforms and pages that Google and AI assistants can read. Numbers are measured, sources are linked.
First-hand write-ups by Ion Rusu, the founder of Bitnoda, a software development studio for Romania, the Republic of Moldova and the EU.
Details
Each one starts from code running in production, usually on bitnoda.team itself.
How we pre-render a 3D Vue site so Google and AI can read it
A 3D website can be fast and fully indexable if the 3D scene is treated as a layer on top of pre-rendered HTML, not as the page itself. On bitnoda.team, every route is pre-rendered to static HTML with vite-ssg, and three.js loads only after the page is visible, and only on devices that can run it. Measured on the production build on 29 September 2026, the home page’s first load needs about 92 KB of compressed JavaScript; the roughly 228 KB of 3D code comes later.
Read the articleMaking a website readable by ChatGPT, Perplexity and Google’s AI
AI search engines such as ChatGPT search, Perplexity, Copilot and Google’s AI features answer from pages they can crawl, read and trust. On bitnoda.team that meant five concrete changes: content in pre-rendered HTML, AI crawlers explicitly allowed, one consistent JSON-LD entity graph, an llms.txt generated from the site’s own copy, and sitemap dates that reflect real edits. None of them guarantees a citation; together they remove the reasons not to be cited.
Read the article