Fable 5 found the cause of a year-long revenue drop with an SEO audit
With an SEO audit on Search Console data, Fable 5 segmented lightGallery’s queries: brand and developer traffic −50%, free tools +330%, total −12%.

Luca Di Domenico
· 2 min read
In short
The developer who maintains lightGallery had been losing revenue for about a year and thought AI was the cause, especially since the site’s overall traffic was down only 12%. An SEO audit run by Fable 5 on Google Search Console and Google Analytics data split the queries into three categories with no specific instructions. Traffic from brand-related searches and from developers had dropped 50%, while traffic to the free tools had grown 330%: the traffic that generated sales had been cut in half. Opus 4.8 had produced a good SEO audit, but without segmenting the traffic on its own.
Fable 5 found the cause of a revenue loss that had been going on for a year, all on its own!
A year of declining revenue and a theory that sounded plausible
It did so by analyzing the site of a developer who maintains lightGallery, an open source library that generates revenue through the sale of commercial licenses.
For about a year, earnings had been falling and the developer thought AI was the cause.
The theory sounded plausible: today many developers can generate the code they need directly, instead of installing an external library.
On top of that, the site’s overall traffic was down only 12%, a drop that seemingly could not explain the sharp fall in revenue.
The SEO audit with Fable 5 on Search Console and Analytics data
Then they exported the data from Google Search Console and Google Analytics and asked Fable 5 to run an SEO audit.
The same analysis they had already tried with Opus 4.8.
The difference is that Fable 5, without receiving any specific instructions, split the queries into three categories:
- Brand-related searches
- Searches made by developers
- Searches related to the free tools on the site
The traffic that generated sales had been cut in half
That is when the real problem surfaced.
Traffic from brand-related searches and from developers had dropped 50%.
Traffic to the free tools, on the other hand, had grown 330%.
Total traffic was therefore down only 12%, but the traffic that generated sales had been cut in half!
This had been going on for a year and the developer had never noticed.
The difference with Opus 4.8
Opus 4.8 had produced a good SEO audit, but it had not segmented the traffic on its own.
Fable 5 did it without being told to, and uncovered a problem that had been causing a revenue loss for months.
Want to know what this means for your product?
If you're building software with AI and want a second opinion on how you're working, tell me about your project.
Related articles
Keep reading
The workflow that separates planning from execution to save tokens
Read: Grok 4.5 in Cursor