Kirgo GEO case study
Kirgo is an iGaming company whose game and promotion pages were heavily JavaScript-dependent, limiting what AI crawlers could read. Its pre-optimization Readiness Score was 32 out of 100, the lowest of our seed cohort.
Readiness Score
Client overview
Kirgo is an iGaming company whose game and promotion pages were heavily JavaScript-dependent, limiting what AI crawlers could read. Its pre-optimization Readiness Score was 32 out of 100, the lowest of our seed cohort.
Industry: iGaming
Website: https://kirgo.com
Problem
Client-side rendering hid most content from AI crawlers, and the site had no structured data describing the product, organization, or FAQs.
Readiness Score, before and after
Kirgo’s Readiness Score before optimization was 32/100 (Not ready).
Readiness Score
Source: Cited site audit of Kirgo, Feb 2026. After scores are published here once they are measured. The Readiness Score measures how ready a website is for AI engines to read, trust and quote. It is not a measure of how often AI recommends the brand.
Methodology
- 01Audited server-side rendering and JavaScript dependency
- 02Tested rendered vs. raw HTML available to AI crawlers
- 03Reviewed schema coverage and content authority signals
Findings
- Core content only available after client-side JavaScript execution
- Zero structured data on key game and promotion pages
- No author or organization authority signals
Recommendations
- Move to server-side rendering / static generation for key pages
- Add Organization, Service, and FAQPage schema
- Introduce authored, credentialed content with Person schema
Frequently asked questions
What was Kirgo’s Readiness Score before optimization?
Kirgo scored 32 out of 100 on its initial Generative Engine Optimization audit.
How did JavaScript rendering hurt Kirgo’s AI visibility?
Most of Kirgo’s content only appeared after client-side JavaScript ran, so AI crawlers that read raw HTML saw little usable content to cite.
Last updated