W-10 · AiS LABZ case study
Our own site was invisible to ChatGPT, Claude and Perplexity. We fixed it the way we fix clients' sites, and documented every step.
The short answer
Aislabz.com was a JavaScript app whose server returned 39 bytes of HTML, so AI crawlers that read raw HTML saw a blank page. We rebuilt it as static HTML in the same design: 107 KB of source and 2,071 crawlable words on the homepage, full schema, and a twice-weekly publishing engine.
What was in the way?
- The server returned an empty container. Everything a human read was painted by JavaScript.
- Two hostnames served the same site with conflicting canonicals.
- Analytics pointed at a property nobody could see.
What changed?
- Every word now in the source HTML, readable by every crawler.
- One canonical host with 301s from every variant.
- 9 AI crawlers explicitly allowed in robots.txt.
- Twice-weekly publishing, each post indexed on the day it goes live.
How did we do it?
The same four-phase method on every engagement: diagnose, model, build, compound.
Diagnose
Read the site the way GPTBot does: raw HTML, no JavaScript.
Model
Same design, same URLs, every word in the source.
Build
A static rebuild with Organization, FAQPage, BlogPosting and BreadcrumbList schema, a single canonical host, llms.txt, a new GA4 property and a verified Search Console domain property.
Compound
Two articles a week, each with an answer block, FAQ schema and internal links, shared to LinkedIn and the Google Business Profile.
Who did we work with?
What happens next?
Case studies like this one, and the authority programme behind them.
Common questions
Many AI crawlers read raw HTML and do not run JavaScript. If your content only appears after scripts run, they see nothing.
View the page source. If your headline isn't in it, AI crawlers can't read it either.
No. The rebuild kept the design and URLs exactly as they were.
Your number next