Reddit share of voice for AI answers

It is two numbers, not one

Most guides on this collapse everything into a single AI share of voice percentage. That number blends sources you can influence with sources you cannot. Your own pages, review aggregators, news articles and video transcripts all feed it, and you cannot meaningfully change most of them on a weekly cadence. The number goes up or down and you are left guessing why.

Splitting the Reddit slice out fixes that. Reddit consistently shows up as one of the most-cited domains across AI answer engines, and it is the only major source where adding a credible, on-topic comment is something you can do today and see indexed within days. So the Reddit slice is both large and movable. That is the rare combination worth measuring on its own.

Measure it in three steps

The whole method is a sweep, an extraction, and a comparison. No paid platform is required for the first pass. An afternoon and a spreadsheet get you a real baseline.

Step three is where most people stop, treat the percentage as a grade, and move on. That wastes the most useful artifact the method produces. The gap list is not feedback. It is a queue of specific threads, each with a URL, where one good comment measurably changes the next sweep.

The join that turns it into a worklist

Step three is tedious by hand the moment you run the sweep more than once. You end up reopening the same threads to recheck presence. The fix is to keep a ledger of every thread you have commented in, and let a database do the comparison.

That ledger already exists if you run the open-source S4L autoposter. Its posts table, defined in schema-postgres.sql at github.com/m13v/social-autoposter, stores one row per thread the tool engaged: the thread_url, the thread_title, the captured thread_content, and the our_url of the comment it left. Once your cited-threads list is in a table, Reddit share of voice is one LEFT JOIN.

-- cited_threads: reddit.com URLs you pulled from AI answers
-- posts:         S4L's ledger, one row per thread you commented in
--                (schema-postgres.sql in github.com/m13v/social-autoposter)

SELECT
  c.thread_url,
  c.cited_by,                       -- 'chatgpt' | 'perplexity' | 'google_aio'
  p.our_url,                        -- your comment URL, or NULL if absent
  CASE WHEN p.our_url IS NULL
       THEN 'gap'
       ELSE 'covered'
  END                AS sov_status
FROM cited_threads c
LEFT JOIN posts p
  ON  p.thread_url = c.thread_url
  AND p.platform   = 'reddit'
  AND p.status     = 'active'
ORDER BY sov_status, c.cited_by;

-- Reddit share of voice =
--   count(sov_status = 'covered') / count(*)  * 100

Every row where our_url comes back NULL is a thread an AI engine already trusts enough to cite, where you are simply not in the conversation. That is the queue, ranked and deduplicated, with no manual rechecking. Run the sweep again next week and the same join shows you which gaps closed.

Why a comment beats a homepage mention

When an AI engine answers a category question, it does not quote your marketing site. It quotes the thread where a real person asked the question and other real people argued it out. That is why the Reddit slice moves the overall number more than another landing page does. You are not adding a source the model has to discover. You are adding a voice to a source the model already cites.

The catch is that a comment only earns a citation if it reads like it belongs there: specific, useful, and honest about tradeoffs. A comment that pattern-matches to an ad gets downvoted, and a downvoted comment does not get retrieved. This is the loop S4L runs as a service for established products: finding the threads that drive your category, writing comments that hold up in the room, and tracking which threads flip from gap to covered. The measurement and the work are the same loop.

Frequently asked