By Lesli Rose · April 27, 2026 · 8 min read
This brand has what most online education businesses spend a decade trying to build: tens of thousands of paying students, a Top 1% marketing podcast with millions of downloads, an 80,000-strong email list, press coverage in every major tier-1 SEO and marketing publication, and endorsements from the most quoted experts in their category. They have been operating profitably for 12 years.
When I looked under the hood of their site -- because they are mid-pivot from "authority site building" to a premium AI training subscription -- I found a 12-year-old WordPress site with strong earned visibility and a critical gap in owned infrastructure. The pivot is correct. The category is right. The market is ready. But the technical foundation that should be carrying the new positioning into Google and AI search has not moved with the brand.
72
Technical SEO
70
On-Page SEO
35
Content / Blog
18
Schema
38
AI Discoverability
65
Social SEO
80
Earned Visibility
Earned Visibility at 80. Schema at 18. That gap -- the inverse of most audits I run -- is the entire story.
No Organization schema. No Person schema for the two well-known co-founders. No Course schema on the premium subscription page. No FAQPage schema, despite a "Common Questions" section sitting on the money page. No BreadcrumbList. Nothing.
For a brand whose entire reputation rests on knowing how SEO works, this was the most surprising finding in the audit. The kind of detail that the most quoted SEO expert in their network would notice in 30 seconds. The fix is a copy-paste afternoon for one developer.
For a brand that sells AI training, having no llms.txt file reads as inconsistent to a sophisticated buyer. The product positioning ("battle-tested AI systems from successful founders") and the technical signal at the root of the domain do not match. AI tools that check for llms.txt as a discoverability signal find nothing and fall back to inferring the brand identity from copy.
A 12-year-old brand whose authority was earned through hundreds of in-depth articles now has a /blog/ index that displays a single post. That is either a deliberate prune or a migration in flight. Both have costs. The current state -- one post on the index -- is the worst of the two: a user landing from a Google search expecting the legacy archive sees a single new article and bounces. A crawler sees a brand that abandoned its content. Neither outcome is what the team wanted.
The fix in either direction is straightforward, but it has to be decided explicitly. 301 redirects from old slugs to thematic pillar pages preserve the equity. Restoring the archive preserves the long tail. Doing nothing slowly bleeds both.
For a recurring subscription priced up to $1,000/mo, a 3.7 Trustpilot rating with most reviews suppressed is a friction point. The new buyer journey for an AI training subscription is: Google the brand, check Trustpilot, ask AI "is this legit?" Three of those touchpoints depend on a healthy review presence. The fix is review platform triage -- replying to every visible review with specific outcomes, requesting refreshed reviews from existing happy students, and publishing AggregateRating schema once the platform health is restored.
The brand appears in 9 of the top 10 SERP results for the legacy category ("best authority site course"). It appears in 0 of the top 10 SERP results for the new category ("best AI course for entrepreneurs," "best AI automation course for business owners"). The 85/15 rule from AirOps (October 2025) -- 85% of AI brand mentions come from third-party sources, brands are 6.5x more likely to be cited through external domains -- is currently working in the brand's favor for SEO and against it for AI. The pivot itself is a news hook the brand can use to earn placements in the new category's listicles within 90 days. They have not done this yet.
The brand has a podcast with hundreds of episodes and millions of downloads. It does not have a YouTube channel that meaningfully repurposes those assets. For a brand selling AI training to operators, the YouTube version of the podcast is the highest-leverage gap in the audit. Every episode could be a long-form upload with timestamps and a keyword-optimized description. Two short-form clips per episode could go to YouTube Shorts, Instagram Reels, and LinkedIn. That is a content engine running on existing assets, not new production.
A pivot is not just a positioning change. It is an infrastructure change. The schema, the llms.txt, the robots.txt, the blog architecture, and the social distribution all have to move with the brand or the new positioning runs on the old plumbing. This brand is mid-move. The earned visibility is doing the heavy lifting. The owned infrastructure is the lever that has not been pulled yet. The work is structural, not creative.
You changed your category, your homepage, and your offer. Did you change your schema, your llms.txt, your robots.txt, and the structure of your blog archive? If not, your old infrastructure is quietly reverting your buyers back to the old positioning every time AI is asked who you are.
Brands that grow primarily through earned visibility often underweight owned infrastructure because it has not historically been the channel that drove revenue. Schema becomes a missing layer once the brand pivots into a category where AI citation rates matter.
Pruning collapses the topical graph and lowers DR over time. Keeping but not maintaining dilutes the new positioning. The right answer is usually to 301 legacy URLs into thematic pillar pages tied to the new direction -- nothing is lost, equity is consolidated.
Mid-pivot brands often have strong earned visibility for the old category and zero for the new. The 85% of AI brand mentions that come from third parties continue to recommend you for the old positioning until you actively earn placements in the new category's listicles and comparisons. The pivot itself is a news hook.
For well-scoped technical fixes -- schema injection, llms.txt, robots.txt, meta rewrites, redirect maps -- a self-contained Claude Code prompt is faster than an agency engagement. The audit becomes the spec; Claude Code becomes the implementation layer.
Related reading: Schema Markup for AI · The 85/15 Rule · What is llms.txt?