Digital Asset Constellation: Building the Content Campaign in One Day
A ChatGPT Conversation Became a Warehouse Query. The Warehouse Query Became 13 Live Pages Across 9 Sites.
Three things stood out.
What we measured for Digital Asset Constellation
Four readings from a campaign that started as a ChatGPT conversation and ended as 13 live pages. The baseline ratio is the reason it was worth doing.
AI crawler readership outran human clicks by roughly 490 to 1. That ratio is the entire argument for filling the gap, and it is invisible if you only look at clicks.
Publishing because a topic feels timely is a guess. Publishing because the warehouse already shows AI systems reading your sites on that exact gap is a plan.
Impressions without clicks and crawlers without readers describe the same condition: demand arriving ahead of the content that would answer it.
One campaign across a portfolio is really three implementations. That cost is structural and shows up in every multi-site push.
Digital Asset Constellation: the short version
Krisada brought a Kodi conversation proposing a Digital Asset explainer series and a Digital Asset Observatory.
Instead of writing content on spec, the plan got checked against real GSC and AI-crawler data in the Digital Karma Data Warehouse first.
The data held up. What shipped was 13 pieces of content across 9 sites, using the actual architecture each site already had, not a template forced onto all of them.
Digital Asset Constellation in plain English
Someone suggested we write a series about digital assets. Before writing anything, we checked our own data to see if AI systems and Google were already paying attention to that topic on our sites. They were, just not showing up in search yet. So we published 13 real pages across 9 sites to close that gap, and fixed a couple of real bugs we found along the way.
Digital Asset Constellation: the starting conditions
The starting claim was simple: digital assets are entering the news cycle through legislation coverage, and the portfolio already had the properties to own that topic early.
That is an easy claim to make and a hard one to verify.
The warehouse made it checkable instead of a guess.
What changed in Digital Asset Constellation
Pulled 90-day GSC and AI-crawler data for the 7 sites in the original proposal, plus a 180-day scan of every 'digital asset' family query across the full portfolio.
The cluster sat at 9,903 impressions and 28 clicks over 90 days, average position in the 40s to 70s.
Nobody in the portfolio ranked for this topic yet.
But the same 7 sites logged 13,781 AI-crawler requests in that window, ClaudeBot and GPTBot leading on most of them.
The sites were already being read. They just were not being found.
That gap became the thesis: publish real content on top of AI visibility that already existed, and see if search visibility follows.
Built a 3-tier plan (AssetClassLeverage.com as the public hub, DatasetSEO.com as the data layer, AISymantix.com as the AI-behavior research layer), then executed it.
Each of the 7 original sites turned out to run a different content architecture.
Three were straightforward JSON-article sites.
Three were marketplace or product templates with no blog system at all. The fixes split cleanly:
- One needed a one-line router change
- One used an existing generic page template
- One was cloned from a static-page pattern already on the site
Read each site's actual router and template code before writing anything, rather than assuming one format would fit all seven.
A ninth site, SmartDigitalInvesting.com, got added mid-build after Krisada flagged it as growing on its own.
The warehouse confirmed it: impressions climbed from 3 to 798 a month between February and July.
That site's report template turned out to be shipping placeholder text for every report it had ever published.
Fixed that as part of adding its first real one.
What the Digital Asset Constellation results show
Three things stood out.
First, the data changed the plan before any content got written.
The original proposal treated AssetClassLeverage.com and AISymantix.com as the two candidates for hosting the Observatory.
The warehouse showed AssetClassLeverage.com already had the only glossary, directory, and category scaffolding of the seven sites, and that DatasetSEO.com had already claimed the measurement-layer role in a post from three days earlier.
The architecture assigned itself once the data was in front of it.
Second, assuming one content format across nine sites would have broken at least three of them.
The fix cost was small everywhere, once the actual router was read first.
Guessing would have cost more.
Third, what looked like a naming conflict (two sites, AssetClassLeverage.com and AIAssetLeverage.com, competing for the same 'digital asset' queries) was not a conflict at all.
Krisada runs multiple properties after the same search terms on purpose.
Redundancy crowds out competitors more effectively than one property holding the position alone.
The two sites kept distinct angles (investment framework on one, AI-build methodology on the other), which is what makes the redundancy additive instead of duplicate.
What Digital Asset Constellation teaches us
Publishing content because a topic feels timely is a guess.
Publishing content because the warehouse already shows AI systems reading your sites on that exact gap is a plan.
The difference between the two is one query against data you already collect.
Explore More Cases Like Digital Asset Constellation
Compare the starting conditions, changes and results across the case study library.