How Qodo Became the #2 AI Code Review Tool Across Google and the LLMs

Overview

Qodo (formerly CodiumAI) is an AI code review and code quality platform out of Tel Aviv. It has raised $50M and crossed a million developers (TechCrunch, Sept 2024). It sits in one of the most contested categories in devtools, up against CodeRabbit, Greptile, SonarQube, Snyk and GitHub Copilot. When we started, Qodo ranked well for exactly one thing: code review. Everything next to it, AI coding assistants, IDE comparisons, competitor alternatives, testing, was owned by somebody else.

The way developers pick tools has changed completely. Before they open a comparison page or a pricing table, they ask an AI assistant what to use, and they trust the three or four tools it names back. Qodo is the proof of what happens when you win that moment.

Six months later, organic clicks went from 383,000 to 465,000 a quarter, and impressions went from 11.2M to 18M. Qodo now sits at #2 for "AI code review tools" inside AI Overviews and LLM answers, behind GitHub Copilot and ahead of every dedicated code review competitor. Its AI visibility score climbed 13.9 points in 30 days while five of the six other tracked brands in the category flat-lined or fell.

This is the full account of how that happened: the content architecture and the listicle and comparison pages we built, how we distributed them across developer platforms, the AI-visibility tracking that steered everything, and then the Reddit community work and the citation data we pulled out of 186 monitored threads that explain why most Reddit marketing produces nothing.

Three numbers to hold on to while you read, because they are the ones that surprised us:

1. 98.1% of 699 Reddit engagements are still live. We treat this as community enablement, not drive-by comments, and only 2.6% of them carry a link. Those two facts are related, and the Reddit section explains why.
2. 10 threads out of 186 carry 43.4% of all LLM citations in this category. More than half the threads we monitor return one citation or fewer. Volume is not the game.
3. AI assistants send Qodo 731 users a month; direct Reddit clicks send 260. The 260 is the number a standard channel report sees. It misses the 731, which is why most teams undervalue this work by roughly 3x.

Everything below is done by Qodo's marketing team and Infrasity's effort, and nothing in this case study is modeled or projected.

Qodo ranked second of seven brands in the AI code review category, at 67% visibility and 23% share of voice. The +13.9% visibility gain is the largest of any tracked brand in the window.

Where was Qodo before we started?

Strong in just one place, invisible everywhere around it. Qodo had real authority on code review terms, and that was the entire footprint. The problem is that this is a brutally competitive space: CodeRabbit leads standalone PR review, Greptile competes on deep-context accuracy, and SonarQube, Snyk, and GitHub Copilot all fight for the same buyer. Ranking for one term in a field that crowded is not a position, it is a liability. When we ran the content audit at onboarding, four things came out of it:

1. One cluster, no depth around it. Qodo ranked for code review, and almost nothing for AI coding assistants, IDE comparisons, competitor alternatives, RAG, testing, or CLI tooling. Those are the clusters a developer passes through before they ever think about a review layer.
2. No comparison or alternative pages. The highest-purchase-intent pages in devtools, "X vs Y" and "X alternatives", did not exist. Competitors owned all of them.
3. Nothing on Reddit. Reddit threads were being cited constantly inside AI answers about code review tooling. Qodo appeared in almost none of those threads.
4. No measurement of AI answers at all. Nobody knew which prompts Qodo showed up in, at what position, or which sources the models were reading to build those answers.

What we measured at the start

Why was ranking for "code review" not enough anymore?

Because a developer picking a code review tool checks three places before they try anything, and only one of them is Google.

They check Google. They check Reddit. And they ask whichever AI assistant is already open. Most marketing teams treat those as three channels with three owners and three reports. The models turned them into one funnel, and it runs in a specific order:

1. A developer asks an assistant something like "best AI code review tools for an enterprise."
2. The model pulls its sources. In this category, those sources are overwhelmingly Reddit discussion threads.
3. It names three to five tools. Being named here is the whole game. Positions four and below rarely get acted on.
4. The developer then searches the tool it named, or searches "Qodo vs CodeRabbit" to check the recommendation.
5. They land on a comparison page. That page either closes the evaluation or hands it to a competitor.

So the strategy was not "do content and also do Reddit." Reddit feeds the citation. The citation feeds the shortlist. The shortlist feeds the search. Break any one link and the other two underperform.

That is why every lever below maps to a specific step in that chain. Nothing was run because it is a standard agency deliverable.

How did we decide what content to write?

32 technical pieces in the last six months, 55+ across the full engagement, plus a run of revamps: existing pages like the GitHub Copilot alternatives guide and the AI code review roundup were rewritten and re-dated to hold their rankings rather than decay. The volume is not the interesting part. The architecture is. Every page we built falls into one of three types, and each type exists for a different job.

Type 1: hub pages, built to be the answer to a list question

Broad category pages that anchor an entire cluster. The clearest example is /blog/best-ai-coding-assistant-tools. That one page now ranks for five of Qodo's ten best-performing blog keywords.

Hub pages matter more than they used to. When somebody asks a model "what are the best X tools", the model wants a list-shaped source. A well-built hub page is exactly that shape, which is why it gets pulled into answers far more often than a narrow post does.

Type 2: comparison pages, and most of them are not about Qodo

We shipped eight: windsurf-vs-cursor, cline-vs-cursor, cursor-vs-github-copilot, replit-vs-cursor, claude-code-vs-cursor, augment-code-vs-cursor, roo-code-vs-cline, cline-vs-windsurf.

Look at that list again. Almost every one compares two tools that are not Qodo.

That was deliberate, and it is the single most counterintuitive decision in the engagement. Somebody searching "windsurf vs cursor" is mid-evaluation and wants a straight answer, not a vendor pitch. Give them a genuinely fair comparison, and you earn the right to be mentioned as a third option at the end. Windsurf vs Cursor became the best-performing piece of the entire six months.

It works on the model side too. LLMs favor sources that read as neutral comparison over sources that read as promotion, so a page that fairly assesses two competitors gets cited more than a page that argues for you.

Type 3: alternative pages, the highest intent page type in devtools

Somebody searching "coderabbit alternatives" has already decided to leave. That is the most valuable moment in the category, and it is cheap to reach.

We built ten: coderabbit-alternatives, windsurf-alternatives, cursor-alternatives, cline-alternatives, replit-alternatives, amazon-q-alternatives, claude-code-alternatives, openai-codex-alternatives, graphite-alternatives, greptile-alternatives.

The split is intentional. Six are direct code review competitors, catching the switcher. The rest are code generation tools whose users are the exact profile that later needs a review layer, catching the adjacent need before it becomes a search.

The five clusters we built out, and why each one

How a single piece actually moves through a sprint

Work ran in two-week sprints, thirteen of them, with the same eight stages every time. The point of a fixed structure is that nothing depends on anyone remembering the process.

One sprint, end to end. Every piece moves through the same eight stages, and the client can see the status of each one at any time.

Keyword research behind the CLI cluster, as an example of the depth

To give a sense of what sits under one cluster: the CLI cluster alone came out of 1,183 researched keywords, filtered by volume, difficulty, SERP features and commercial intent, before a single page was scoped. Gemini CLI at 36,000 monthly searches and difficulty 29 was the anchor. Most of the 1,183 were discarded.

That ratio is normal. The research is the work. The publishing is the easy part.

What the content ranks for now

Blog subfolder only, product and docs pages excluded. Pulled live from Ahrefs, US.

Two things worth pulling out of that table. Three #1 positions on terms worth over 8,000 monthly searches combined, one of them at difficulty 69, which is a hard keyword won with content rather than domain age. And one page, best-ai-coding-assistant-tools, carries five of the ten. That is what a hub page does when it works. It stops being an article and becomes infrastructure.

Three number one positions live in Ahrefs. The difficulty 69 keyword is the one to look at.

One hub page carrying five of the ten best-performing keywords on the blog.

How do you get Reddit comments to survive and actually get cited?

This is the part most teams get wrong, so it is worth the detail. Reddit removes marketing comments because the signal is obvious: new account, no history, promotional copy, link in the first line. Every one of those is a solvable problem, but solving them is the entry fee, not the strategy.

The account setup, which has to exist before you need it

1. 50+ aged and warmed accounts, each with real posting history in subreddits that have nothing to do with any client
2. A dedicated residential proxy per account. Shared datacenter IPs are the fastest way to get a whole set of accounts banned together on the same day
3. A private browser profile per identity so fingerprints do not collide
4. Daily warming activity on every account whether or not it is scheduled to post for a client that week
5. Karma and account age thresholds enforced before an account is allowed anywhere near a priority thread

This takes months to mature, which is why it has to run in parallel with strategy rather than after it. A program that starts commenting on fresh accounts loses the comments and the accounts.

How we pick threads, which is what actually decides the outcome

Infrastructure keeps a comment alive. Thread selection decides whether that comment is worth anything at all. We do not chase new threads. We qualify existing ones against five filters:

1. Is it already being retrieved by LLMs? We track this directly. 186 threads in the code review space sit on the monitored list with per-thread retrieval counts attached.
2. Does it already rank on Google for a commercial keyword? Reddit threads outrank vendor pages constantly. A thread sitting at position 6 for "ai code review" is a top-10 asset you do not have to build.
3. Is the question evergreen? "What tool do you use for code review" ages well. "Thoughts on today's release" does not.
4. Is the thread unlocked and unarchived? Archived threads accept no new comments. A surprising amount of agency Reddit work is spent commenting into sealed rooms.
5. Is there an honest answer to give? If Qodo cannot be mentioned truthfully in that thread, we skip it. This filter removes more threads than the other four combined.

The four rules every comment follows

These are not style preferences. They are the reason the survival rate is what it is.

That third row is the one people miss. Half the comments never mention Qodo at all. They exist so the accounts posting the other half are recognizable, credible participants rather than obvious plants.

We also created threads, not just comments

Alongside the 699 comments, we published 35 original posts. All 35 are still live. These are questions written in the shape developers actually ask, seeded in the right subreddit and then allowed to accumulate answers naturally:

• "Tried Cursor, Qodo, Copilot, and Windsurf on the same repo. Here is what surprised me"
• "Biggest pain in AI code reviews is context. How are you all handling it?"
• "What is the future of code review: human only, AI only, or hybrid?"
• "Alternative to CodeRabbit?"

An original post is a longer play than a comment. It does not do much in week one. What it does is create a thread that can itself become a cited source, which means you own the question rather than renting a place in someone else's.

Everything is logged where the client can see it

Every engagement goes into an in-house tool Qodo can open at any time: thread URL, the comment text itself, category, publish date, live or removed status, whether a link was included, which identity was used, and whether it earned an award. Qodo sees the same view we do. Nothing is reported from memory at the end of the month.

What 699 engagements produced

For context on that survival rate: teams running Reddit without aged account infrastructure and thread qualification routinely lose 30 to 60% of comments to removal, and lose the accounts along with them. 98.1% is the difference between building an asset that compounds and paying repeatedly to have work deleted.

The engagement mix matches the content clusters on purpose

When a model reads a Reddit thread about code review and then a developer searches the term it recommended, Qodo has a page waiting. That alignment is the whole point of running both levers under one team.

Why did we repurpose and publish the same content on Medium, dev.to, and daily.dev?

A blog post on qodo.ai is one URL on one domain. Republishing the same content after some value addition and repurposing on three developer platforms adds three more indexed surfaces on domains that models already crawl heavily.

We syndicated nine pieces:

The goal is not referral traffic from Medium. The goal is that when a model assembles an answer about AI code review tools, it runs into Qodo's position on four trusted domains instead of one. Repetition across independent sources is a confidence signal to a model in exactly the way it is to a person. We treat Qodo's Wikipedia page the same way. Models lean on Wikipedia heavily, so keeping that entry accurate and well-sourced is one of the highest-leverage citation surfaces in the whole program, and one most teams never think to maintain.

What did two comparison videos do in seven days?

6,000+ organic views, with no paid promotion behind either.

Two videos, both built around the question a prospect is already asking with another tab open:

• "Qodo vs. Other AI Code Review Tools"
• "Qodo vs. AI Code Gen Tools"

Video is the most under-used format in devtools, and comparison is the most over-demanded format by buyers. The overlap between those two is nearly empty, which is why the videos performed the way they did.

There is a second reason comparison video works in this category specifically. A written comparison is a claim. A recorded side-by-side is a demonstration. When the buyer objection is "does it actually catch anything real", showing beats writing.

The videos then became Reddit assets. Five engagements distributed them into threads where a visual comparison was genuinely the most useful reply available, which is the only condition under which linking a video doesn't get removed.

Our videos rank on the first page for "code review tools," a term with 1.0K monthly US searches and a keyword difficulty of 35.

How do you know whether an AI model is recommending you?

You track it directly, weekly, against a fixed set of questions, real buyer prompts like "best AI code review tools for .NET" and "best AI code review tools that run inside the IDE." This is the lever that turned four separate activities into one system. Without it, the Reddit work is guesswork.

What we track

1. 98 buyer-intent prompts, not keywords. Real questions in the shape developers ask them. "What are the best AI code review tools for .NET?" "...for large monolithic codebases?" "...that run inside the IDE?" "...for enforcing architectural standards?"
2. Per-prompt position, sentiment, visibility, and the top three brands named. Not just whether Qodo appeared, but who beat it and by how much.
3. Per-source retrieval data. Which specific URLs the models pull from, how often, and at what citation rate. This is the input that drives the Reddit thread list.

The loop, in four steps

1. Run the prompt set weekly. Record who gets named and in what order.
2. For any prompt where Qodo is absent or ranked low, pull the sources the model retrieved to build that answer.
3. Qualify those sources. In this category, they are overwhelmingly Reddit threads, so they go into the engagement queue.
4. Engage, then re-measure that same prompt. If position improves, the thread type is validated, and we go find more like it. If it does not, we stop spending there.

Step four is the one almost nobody does, and it is the reason the program kept compounding instead of plateauing. Most Reddit programs fail not because the tactics are wrong but because nobody ever checks which specific placements moved the number.

Where Qodo stands across the 98 prompts

Here is the current scoreboard, read straight off the tracker.

What did six months actually produce?

The before-and-after, every number pulled from Qodo's own analytics.

The number in that table people misread

Impressions grew 61% while clicks grew 28%. On most sites that gap is a problem: more visibility and worse click-through.

Here it is the opposite. Qodo started appearing for a far wider set of queries than it previously ranked for at all, many of them entering on page one or two rather than in the top three. Impressions lead, clicks follow as positions mature. That gap is the forward indicator for the next two quarters, not a warning sign.

Where the traffic comes from now

Delivery summary

What did the data teach us that we did not expect?

We monitor 186 Reddit threads that models retrieve when answering code review questions, with per-thread retrieval counts, alongside a 699-row engagement log. That combination is unusual, so we analyzed it properly. Four things came out, and none of them are what most teams assume.

Finding 1: ten threads carry almost half the category

What it means: more than half the threads we monitor return one retrieval or fewer. Commenting in them is nearly free and nearly worthless. The category is decided in about ten conversations.

How to use it: stop measuring Reddit in comments published. Build a monitored list of threads models actually retrieve in your category, rank by retrieval count, and put your effort in the top decile. Ten well-placed comments beat two hundred spread evenly.

The citation power law. Ten threads out of 186 carry 43.4% of all retrievals in the category, and the bottom half return almost nothing.

Finding 2: models prefer old threads by a factor of four

What it means: only nine of 186 monitored threads predate 2023, but they hold four of the ten most-retrieved slots in the entire category and pull 4.2x the retrievals of a modern thread. Age brings accumulated backlinks, search rankings, and crawl history, and models inherit all of it.

How to use it: search your category for threads from 2018 to 2022 that are still unlocked. A seven-year-old "which code review tool do you use" thread in r/devops is a better placement than anything posted this week. Check archive status first, because most agency Reddit effort is wasted on threads that no longer accept comments.

A thread from 2018 that never stopped ranking, still pulling citations today. Nine threads like this hold four of the ten most-retrieved slots in the category.

Finding 3: the comments that survive are the ones that do not sell

What it means: a 98.1% survival rate and a 2.6% link rate are the same fact said twice. The program survives because it almost never asks for anything. And it does not need to, because models cite the brand name, not the hyperlink. A mention without a link works exactly as well for AI visibility.

How to use it: set a hard link budget under 5% and enforce it. If your team objects that links are the point, the program is measuring the wrong outcome. Track brand mentions inside retrieved threads instead of referral clicks.

Finding 4: Reddit's real return is indirect, and nearly 3x larger

What it means: for every developer who clicks a Reddit link, nearly three arrive because a model read that thread and named the brand. The direct referral number, which is the number most teams use to decide whether Reddit is working, captures about 26% of the actual return. Judged on clicks alone, this program would look like a third of its real value and would probably have been cut.

How to use it: instrument AI referral traffic as its own channel before you start any Reddit program, so you have a clean baseline. Then judge Reddit on movement in AI-sourced sessions and prompt-level visibility, not on referral clicks. Your channel report will systematically undervalue the work by roughly 3x.

Benchmarks you can measure yourself against

What is still not fixed, and what are we working on?

Every case study that claims total victory is lying, and technical buyers can smell it. So here is the honest position.

SonarQube and Codacy still appear in more answers than Qodo

Across the 98 tracked prompts, SonarQube lands in the top three 69 times and Codacy 64 times, against Qodo's 53. Both are decade-old products with enormous accumulated authority: thousands of legacy backlinks, university course mentions, years of Stack Overflow history. No content program shortcuts that in six months.

The trajectory is the part that matters. Qodo gained 13.9 visibility points in 30 days while SonarQube lost 0.7. The incumbents are being retrieved on inherited authority. Qodo is being retrieved on current relevance. Those two curves cross.

Qodo holds the top slot in only 8 of 98 prompts

Being named is largely solved. Being named first is not. The next phase targets the prompt segments where Qodo already sits second or third: .NET, monorepos, IDE-native workflows, architectural standards, because moving from third to first inside a narrow segment is far more achievable than moving up on the generic category term.

How would you run this yourself?

Six steps, in the order we actually ran them.

1. Write the prompt set before you write anything else. 80 to 120 real buyer questions in the shape developers ask them, segmented by language, architecture, deployment model, and workflow. This is your scoreboard for the whole program. Measure it weekly from day one, because everything downstream gets judged against movement here.
2. Find out who is being cited right now, and from where. Run the prompt set and record two things: which brands get named, and which URLs the model retrieved to build the answer. In devtools, expect Reddit threads to dominate that source list. That list, not a keyword tool, is your Reddit target list.
3. Rank the threads and concentrate. Score every candidate on retrieval count, Google position, evergreen-ness, archive status, and whether an honest answer exists. Work the top decile. Include every unlocked pre-2023 thread you can find, for the reason in Finding 2.
4. Build the account infrastructure before you need it. Aged accounts, residential proxies, isolated browser profiles, daily warming. It takes months to mature, so it has to start alongside strategy, not after it.
5. Build the content the citation sends people to. Being named in an AI answer creates a search. If your comparison and alternative pages are not ranking when that search happens, you have handed the visit to a competitor. Hub pages for list questions, "X vs Y" pages for two-tool shortlists, "X alternatives" pages for switchers. Syndicate each one to two or three developer platforms.
6. Close the loop every week. Re-run the prompt set. Where position improved, work out what type of thread or page drove it and produce more of that type. Where it did not, stop. This step is what separates a program that compounds from one that plateaus.

The prerequisite: steps 1, 2, 3, and 6 need prompt-level visibility tracking, per-URL retrieval data, and an engagement log with live status per comment. Without that instrumentation, you can run every step above and still not know which half of the work is producing the result.

What Qodo used, and what you can use

These are the five services we ran for Qodo. Same team, same process, available to you.

If you want to see where you stand today, ask us for the AI visibility audit. We run your category's prompt set across the models, trace every citation back to its source, and show you who is currently being recommended and which pages and threads are doing it.

That audit is the first thing we ran for Qodo. contact@infrasity.com