I asked 12 AI engines if they knew my product. Only 5 did.

Last week I did something a bit weird. I asked 12 different AI chatbots whether they knew my product exists.
Some background. I run a small tool called SCORIXA. It scans a business's Google reviews and tells them roughly how much money they're losing every month because of the bad ones. Solo founder, pre-revenue, the usual grind.
People keep saying AI search is the new SEO. Everyone's googling less and just asking ChatGPT "what's the best tool for X". So I wanted to know, in the most basic way possible, do these AI engines even know I'm here?
So I opened ChatGPT, Gemini, Grok, Meta AI, Google's AI Mode, Claude, Perplexity, Copilot, DeepSeek, Kimi, Brave, and You.com, and I asked all of them the same questions. Stuff like "what is SCORIXA" and "what tools calculate revenue lost from bad reviews".
This is not science. It's just me messing around for an afternoon. But the result was interesting enough that I wanted to write it down.
5 of them knew the product. ChatGPT, Gemini, Grok, Meta AI, and Google's AI Mode. The other 7 had no clue. A couple of them even mixed my name up with a football stats thing and, weirdly, a type of volcanic rock. Cool.
What stood out to me is the 5 that knew me all seem to pull a lot from Reddit and live web content. The ones that didn't lean more on older or narrower training data, and I just haven't earned enough mentions out there yet for them to have picked me up.
A few things I took from it, if you're building something new:
Reddit is doing more than I expected. The engines that knew me kept surfacing stuff that traced back to Reddit threads. Being genuinely active in the right communities seems to feed straight into this.
Structured data actually helps. I added a Wikidata entry mostly so the AIs would stop confusing my brand with the rock and the football thing. Seems to help them tell you apart.
It really is just citations again. The engines that didn't know me aren't broken. I just haven't been mentioned enough places yet. AI visibility is basically SEO wearing a new hat. Other people referencing you is still the whole game.
If you're first in a niche, that's worth a lot. There's not much else for the models to learn from, so your early content shapes how they describe the whole category later.
Anyway. If you've built something, try this yourself. Just ask the big AI engines about your product and your category and see what comes back. Took me 20 minutes and it was a pretty humbling little audit.
If you're curious what the tool actually is, it's here: https://scorixa.me
Question for anyone who's tried this. Are you also seeing Reddit weighted this heavily, or is that just my category?

Comments

[Performance Dev]

Great experiment, Amine. I run a site audit tool and did a similar test recently. The pattern I noticed: the chatbots that knew your product were using retrieval-augmented generation over live web indexes, not their base training sets.

Reddit being weighted this heavily tracks. Reddit has high domain authority, fresh content density, and AI pipelines ingest it at scale because it is permissively licensed for training. But the deeper mechanism: chatbots with real-time web search surface Reddit because it ranks well in the underlying search index. The ones relying on static training snapshots miss you completely.

The lever nobody talks about: structured data markup for AI crawlers. Schema.org with Speakable + About gives AI search engines reliable entity definitions. And you already found the Wikidata trick - that fixes entity resolution (rock vs tool).

If you want to go deeper, I wrote about crawl topology and how AI agents discover content on our site. Short version: get mentioned in frequently-crawled authority spaces and give crawlers structured signals that say "this is a tool, not a rock."

[Amine Fakiri]

Appreciate this — the RAG-vs-training-snapshot distinction is exactly where I landed too. The structured-data piece is the part I hadn't fully acted on; I've got the Wikidata entity in place but haven't layered the Schema.org entity markup with sameAs yet, so that's my next move. Curious what you've seen work better , entity markup sitewide, or concentrated on the homepage? I'll check out your crawl-topology write-up.

[Performance Dev]

Sitewide entity markup on every unique page type is what moved the needle for us — homepage + contact + service pages. Single JsonLD block per page with @type, @id, sameAs, and Speakable.