2
5 Comments

Our own AI-visibility score started at 0/100. What 2,150 cited URLs taught us about getting recommended by ChatGPT

Hi IH — I'm Anil, solo and bootstrapped, building Promvia: it checks whether ChatGPT, Perplexity, Gemini and Google's AI answers actually name your product when buyers ask for a recommendation, and what those answers send your site. Launched August 2026, €0 MRR so far, building in public. Disclosure up front: the numbers below come from our own tracking.

The thing worth sharing is a finding, not a feature. We track a fixed set of buyer prompts every week across six answer engines and log every URL the answers cite — about 2,150 cited URLs over 14 days in one niche (software tools). Two things fell out:

  1. "Alternatives to X" prompts cite comparison-shaped pages (paths like /vs, /alternatives, /compare — vendor pages and blogs included, not just G2 or Capterra) in 34–43% of citations. "Best X" prompts: 2.8%.

  2. When we first counted by directory DOMAIN instead of page shape, the effect looked ~10x smaller. The domain list was a bad proxy. What gets cited is the page type, wherever it lives.

The practical version: a well-structured /alternatives or /vs page on your own domain competes for the same answer slot as a G2 grid. "Get listed on directories" and "build comparison pages" are sold as two tactics; at the citation level they look like one. And the cited pages had almost no organic traffic — winning the SERP and being chosen for an answer are different games.

Caveats, honestly: one niche, two weeks, URL-path labeling rather than rendered pages. Direction solid, magnitudes indicative. We pre-registered a follow-up (vendor-authored vs third-party comparison pages) and will publish it on Sep 7 whatever it says.

We eat our own cooking: Promvia's own domain scored 0 on day one, and we publish our own weekly run live at promvia.app/live so the score is a public number rather than a promise.

Question for people running product sites here: do your /vs or /alternatives pages pull AI citations (or AI referral traffic) out of proportion to their organic traffic? That publisher-side number is the one nobody seems to have.

posted toAvatar for product Promvia
Promvia
  1. 1
    The 2,150 cited URLs make the finding much more interesting than another AI-visibility claim. Have you seen /vs or /alternatives pages produce meaningful qualified traffic from AI answers yet, or is citation volume still the stronger signal?
    1. 1
      Honest answer: citation volume is the stronger signal for us so far, and I would not claim qualified traffic yet. Two reasons, both measurement rather than marketing. 1. Most assistants open links with no referrer, so the visit lands in analytics as Direct. We keep two buckets apart: confirmed (a referrer, or an assistant user-agent like ChatGPT-User fetching the page on a user's behalf) and inferred (Direct sessions landing cold on a deep /vs or /alternatives URL, which typed-in Direct almost never does). The inferred bucket runs roughly 2 to 3x the confirmed one. That gap is the honest size of the attribution hole. 2. On our own domain the numbers are small enough to say out loud: a handful of AI-referred visits and no attributed revenue. The comparison pages that got cited in the dataset were third-party ones, and we do not have their analytics, which is exactly the publisher-side number I was asking for. What I can say: the citations are weekly and reproducible, the traffic is not yet. We started publishing the source side in the open today (promvia.app/ai-source-index, 40 fixed buyer questions across seven engines every Monday), and the first week already showed the engines leaning on YouTube and Reddit far more than on any directory for consumer questions. If your /vs pages show AI referrals out of proportion to organic, I would genuinely like to see the numbers.
      1. 1
        That attribution gap is the interesting part, especially the confirmed vs. inferred split. I’d be interested in comparing notes on what the /vs pages are actually driving. What’s the best email to reach you on?
        1. 1
          Happy to compare notes: support@promvia.app reaches me directly. If you send the /vs URLs you are looking at, I can run them through the same weekly panel and share what the engines cite for their questions, no strings.
          1. 1

            Thanks! I’ve just sent it over.

            Looking forward to hearing your thoughts whenever you have a chance.