The Challenge
By late 2024, Reel Axis faced a paradox familiar to many B2B agencies: the company had real authority — Inc 5000 ranking, 10 Clutch reviews, three acquisitions, 17+ external source mentions — but was completely invisible to AI platforms.
The cause was technical. The reelaxis.com website was a React Single Page Application (SPA) built with Vite and React Router. Every page rendered client-side only. When GPTBot, ClaudeBot, or PerplexityBot crawled the site, they saw an empty <div id="root"></div>. The company's entire web presence was invisible to AI search.
Meanwhile, the market was shifting. 60% of Google searches had become zero-click. 37% of B2B product discovery was starting in AI interfaces. Reel Axis's clients — and Reel Axis itself — were losing visibility in the channels where buyers were increasingly making decisions.
The diagnostic: Despite 17+ authoritative source mentions across Clutch, G2, D&B, ZoomInfo, Inc 5000, HubSpot, and LinkedIn — Reel Axis had zero AI citations. The entity existed in AI training data. The website content did not.
The Approach
Rather than hiring an external agency, Reel Axis decided to solve the problem internally — and turn the solution into a new service. The approach:
- Semantic Blueprint — Mapped the entire entity landscape: existing authority signals, knowledge graph gaps, competitive citation analysis, topical authority clusters
- Technical AIO — Migrated from React SPA to Astro SSG. Zero JavaScript by default. Every page renders complete HTML at build time.
- Schema Architecture — Comprehensive Schema.org JSON-LD: Organization, Person, Service, WebSite, BreadcrumbList, FAQPage on every page. Single @graph container per page.
- AI Crawler Access — robots.txt with explicit GPTBot, ClaudeBot, PerplexityBot Allow directives. llms.txt at site root. Auto-generated sitemap.
- Content Architecture — 6 topical authority clusters, 51 planned pages, hub-and-spoke internal linking, bridge content connecting B2B demand gen authority to AIO positioning
- Entity Expansion — Not replacing the existing entity but expanding it. Inc 5000, Clutch, HubSpot signals preserved. AIO positioning layered on top.
The Build
The site was built by a 12-agent team using the Narrow AI agentic web service — itself a proof point that AI-first operations are practical, not theoretical. The team included specialists for strategy, information architecture, design, schema engineering, copywriting, and frontend engineering.
The technology stack — Astro SSG, Tailwind CSS v4, TypeScript, Schema.org JSON-LD — was chosen specifically for AIO requirements: zero JS by default, complete HTML at build time, structured data in static <head> tags.
The Results
The results of the transformation are measurable across multiple dimensions:
- Technical: Every page delivers complete HTML to AI crawlers. Schema.org validated. AI crawlers explicitly allowed. llms.txt published.
- Entity: Organization schema includes foundingDate, award, memberOf, hasCredential, knowsAbout, hasOfferCatalog, 7 sameAs links. Person schemas for both leaders with disambiguatingDescription.
- Content: 51 planned pages across 6 topical authority clusters. Pillar guides, service pages, entity anchor pages, bridge content connecting old authority to new positioning.
- Performance: Sub-5-second build time. Under 50KB CSS. Lighthouse targets: 95+ Performance, 100 Accessibility.
Key Takeaways
- The #1 barrier is rendering. Real authority doesn't matter if AI crawlers can't read your content.
- Entity expansion beats entity replacement. Preserving existing authority signals while adding new positioning is more effective than starting from zero.
- Your own transformation is the best case study. Walking the talk creates credibility no sales pitch can match.
- Structure matters as much as content. Schema.org, internal linking, topical clusters, and crawl paths are as important as the words on the page.