# GEO keyword research: how we pick topics that rank and convert

*How we pick topics for AI search: start from your market, find topics from competitors or buyer journeys, check them in Ahrefs, then fill the gaps.*

By Naman Bansal, CEO and co-founder · November 19, 2026

Picking topics to write about in the AEO age is an interesting topic.

Most of it is still SEO. Good SEO is good GEO, and there's nothing in our topic research that a good SEO wouldn't do. What's changed is that whipping up Ahrefs and pulling a bunch of high-volume, low-difficulty keywords isn't enough anymore. If you want to rank quickly and drive conversions, you have to start from the market and the buyer.

This blog post breaks down our process for finding topics that help us rank quickly in AI search and drive conversions and signups for our customers.

For context, we do DevRel and GEO for AI companies like Greptile, Mastra, and Agentmail, and this is the playbook we use at the start of every customer engagement.

## Start with your market

The first thing we figure out for any customer is what kind of market they're in, because that decides where the first list of topics comes from.

![How we pick topics in an established market versus an emerging one](/blog/geo-keyword-research/market-diagram.png)

In an established market, buyers already search for the category and competitors already rank for it. Alexis Fournier, our head of GEO, starts there: "It's always better to start where others are succeeding. They already put in the research, and you already have data from the market."

Mastra is a good example. Mastra is an open-source TypeScript framework for building AI agents. Agent frameworks were already an established category when we started working with them, and LangChain and other frameworks had pages ranking on Google for the searches Mastra's buyers make. So Alexis started by looking at what those frameworks wrote about and which of their pages ranked, and used that to decide what Mastra should cover.

In an emerging market, there isn't much to copy. Few people search for the category by name, and nobody ranks for it yet. Here Alexis works from the buyer instead: "It's more focused on first principles, helping the buyer buy." You figure out the pain points on the buyer's journey that would lead them to a product like yours, and write for those.

The best source for those pain points is the customer's own calls. We ask every customer for the questions and objections that come up most in their sales and customer calls. It's a goldmine for topics, and one of the best uses of LLMs we've found: Claude can go through hundreds of hours of call transcripts and pull out what buyers keep asking.

Supermemory is a memory API that gives AI apps long-term memory. When we started writing for them, AI memory was a new idea and almost nobody searched for it by name. But developers who needed memory were already searching for the things around it, like vector databases and RAG, and those areas had real search volume and competitors ranking. So we picked seven topic areas for Supermemory, and only one of them was AI memory itself. The other six were the areas around it: vector databases, RAG, context windows, MCPs, LLMs and AI agents.

![Supermemory content map: seven topic areas fanning out into pillar posts and related searches](/case-studies/devrel/content-map.webp)

Either way, you need to know your ICP well: who they are, what they're building, and what they're stuck on. In an established market, that tells you which of your competitors' pages are worth copying. In an emerging one, it's where you start.

## If your market is established

When competitors already rank, we start with what they rank for. These are the five steps we follow, in Ahrefs and Claude.

### 1. See which pages bring your competitors traffic

In Ahrefs, enter a competitor's domain in Site Explorer and open **Top pages**. It lists their pages by estimated organic traffic, and the Page type column shows which ones are landing pages, guides, or blog posts. The **Organic keywords** report next to it lists every search they rank for.

![Ahrefs Top pages report for langchain.com](/blog/geo-keyword-research/ahrefs-top-pages-langchain.png)

### 2. Find the searches they rank for, and you don't

Ahrefs' **Content gap** report does this in one step. Enter your domain, add two or three competitors, and it lists the searches where at least one competitor ranks in the top 10, and you don't rank at all. For instance, this is what it shows for manicule.com against Profound and Peec AI:

![Ahrefs Content gap report for manicule.com against tryprofound.com and peec.ai](/blog/geo-keyword-research/ahrefs-content-gap-manicule.png)

### 3. Move the top-of-funnel searches down the list

A lot of that list will be top-of-funnel. In ours, "aeo meaning" and "what is aeo" are searches from people learning what the term means, and they're rarely about to buy anything. Alexis moves those down first: "You try to map that to revenue, so you ideally want to filter out what is very top of funnel."

They don't come off the list. Top-of-funnel pages earn the links and mentions that build topical authority, so we still write some of them. They just don't go first.

### 4. Keep what fits your product

Then we compare what's left against our customer's product. Some of what a competitor ranks for won't fit what our customer sells. And some of what our customer sells, no competitor covers at all.

We call the second group **blind spots**: topics close to the product that nobody in the category has written about well. Those go to the top of our list.

### 5. Widen the list with Claude

A competitor's list only shows what they thought to write about. To widen it, we give Claude everything we know about the customer: their call transcripts, the ICPs and positioning we've validated with them, their landing pages and website, and their G2 reviews if they have any. Then we add the competitor topics we kept and ask for every topic and subtopic around them.

Claude with a one-line ICP gives you generic topics. Claude with that context gives you the topics your buyers actually ask about.

Then we turn those topics into searches and check each one in Ahrefs.

These are the two prompts we use with the Ahrefs MCP in Claude:

```text
Pull the organic keywords [competitor.com] ranks for in the top 10 with a keyword
difficulty of 20 or below. Group them by topic, drop the top-of-funnel ones, and
show which topics we have no page for on [yourdomain.com].
```

```text
Here is what we know about our buyers: [call transcripts, validated ICPs and
positioning, landing page copy, G2 reviews].
Here are the topics our competitors rank for: [list].
List every topic and subtopic this person would want to read about on the way to
choosing a product like ours, grouped by theme. For each one, give two or three
searches they might type.
```

## If your market is emerging

When nobody ranks for your category yet, there's no competitor list to start from, so we start from the buyer.

### 1. Pick the topic areas around your product

List the subjects your ICP already reads and searches about. A few will be about your category, but most should be the subjects next to it, because that's where your buyers search today.

For Supermemory, the ICP was developers building AI apps. A developer who needs memory in their app is already working with embeddings, so they read about vector databases, RAG and context windows. That's how we got to the six areas around AI memory. Those areas turned into Supermemory's blog:

![The Supermemory blog index](/case-studies/devrel/blog-index.webp)

### 2. Map the jobs your buyer is trying to get done

Inside each topic area, list the jobs the buyer is trying to get done and the searches they make along the way.

In vector databases, two of those jobs were:

- Connecting a vector database to an LLM
- Checking whether a vector database is good enough for their app

We wrote guides and benchmarks for each job, and showed where Supermemory solved part of it.

For example, this benchmark of open-source embedding models:

![Supermemory's benchmark of open-source embedding models](/case-studies/devrel/blog-embeddings.webp)

We built buyer journeys into Manicule so you don't have to map these by hand. Manicule suggests the situations your buyers are in, based on what you sell, then maps the steps they go through and the searches they make at each step, with monthly volume from Ahrefs.

Borrowell is a Canadian fintech app that gives people their credit score for free and recommends loans and credit cards they're likely to be approved for. One of the journeys Manicule generated for them starts with a parent who owes $12,000 on credit cards at 22% interest:

![Buyer journey in Manicule for a parent carrying credit card debt, with searches and monthly volume at each step](/blog/geo-keyword-research/manicule-buyer-journey.png)

Before they look at a single loan, they search "credit card interest calculator" (3,000 searches a month) to see what the debt costs them, then "how to pay off debt fast". Only after that do they search "how to get a debt consolidation loan". That's three pages for Borrowell, and two of them are for someone who isn't shopping for a loan yet.

### 3. Generate topics with Claude before you open Ahrefs

Alexis builds the rest of the list with Claude before he opens a keyword tool: "I like to ignore keywords first. Here's the ICP, here are the pain points: generate as many topics and subtopics as you can."

What makes that work is what goes in first: the customer's call transcripts, their validated ICPs and positioning, their website, and the buyer journeys from the last step. A few lines of ICP isn't enough context to get relevant topics.

Then he turns those topics into searches and checks them in Ahrefs. In a new category, starting in Ahrefs only shows you the few searches that already have volume.

This is the prompt we use:

```text
Here is what we know about our buyers: [call transcripts, validated ICPs and
positioning, website copy, buyer journeys].
Act as [ICP]. List 20 questions you'd ask Google or ChatGPT while trying to solve
[pain point], from the moment you notice the problem to the moment you choose a product.
```

## Check every topic in Ahrefs

Both paths end with a list of topics and the searches behind them. Before we write anything, we check each search in Ahrefs.

### 1. Connect Ahrefs to Claude

We run these checks from Claude through Ahrefs' MCP server, so we can check a whole list at once instead of pasting searches into Keywords Explorer one by one. In Claude Code, run:

```bash
claude mcp add ahrefs https://api.ahrefs.com/mcp/mcp -t http
```

Then run `/mcp` in Claude Code, pick ahrefs, and sign in to your Ahrefs account.

In the Claude desktop app or claude.ai, add `https://api.ahrefs.com/mcp/mcp` as a custom connector instead. You need a paid Ahrefs plan.

### 2. Find the long-tail searches under each topic

For each topic, take its head term and open **Matching terms** in Keywords Explorer.

The long-tail searches are there: the specific questions people ask on their way to a product. These are the questions under "ai visibility", for example:

![Ahrefs Matching terms, questions for "ai visibility"](/blog/geo-keyword-research/ahrefs-matching-terms.png)

We give long-tail searches more weight for AI search than we would for Google. AI assistants tailor their answers to the person asking, so a page that answers one specific question well is the page they pick for that question.

### 3. Don't take volume or difficulty at face value

Search volume and keyword difficulty are good context to have, but they shouldn't drive your decisions.

Ahrefs is estimating, like every other keyword research tool, and the estimate can be off in both directions.

Rank trackers and scrapers run Google searches too, so volume can be inflated. One of our browser automation customers saw around 100,000 Google impressions for "browser automation" over three days in September, and none of them came from people.

It can also miss real searches. Ahrefs shows no volume for "playwright in rust", but the same customer's post about a Rust version of Playwright gets impressions and clicks for it in Search Console. Your own Search Console is the closest thing to real demand you have.

These are the two prompts we use with the Ahrefs MCP at this step:

```text
Using Ahrefs, get US volume, KD, traffic potential and parent topic for these
searches: [list]. Then find matching terms and questions for [head term] with a KD of 40 or below. Return a table sorted by volume.
```

```text
For [search], list who ranks in the top 10, what format and angle each page uses,
what the Google AI Overview cites, and how beatable it is for a site with DR [x].
Then suggest one thing we could publish that none of the ranking pages have.
```

## Fill the gaps with what keyword tools can't see

### SME and customer interviews

This one isn't optional. As Alexis puts it: "SME interviews are mandatory. Otherwise you get slop."

Alexis generates topics after calls with a customer's team, on top of the sales and customer calls they share with us. We also read their support tickets, Discord and GitHub issues.

### Reddit

Read the threads in your ICP's subreddits. For Supermemory, developers were already discussing AI memory in r/LangChain, r/LocalLLaMA and smaller subreddits, and the same questions kept coming up: how do I manage memory in agents, which vector database should I use for a chat app, how does Mem0 compare to Supermemory.

Each recurring question became a brief.

![Map of Reddit threads about AI memory, Mem0, vector databases and RAG](/case-studies/devrel/reddit-map.webp)

### X

In developer tools, topics often trend on X before they show up in keyword tools.

"Software factories" was trending on X while Ahrefs showed no volume for it, so we targeted "ai software factory" for Mastra and wrote [What is an AI software factory?](https://mastra.ai/articles/what-is-ai-software-factory) and [How to Build an AI Software Factory with AI Agents in TypeScript](https://mastra.ai/blog/software-factory).

The first one now ranks on the first page of Google for "ai software factory", and Google's AI Overview cites it. Ahrefs now shows 250 searches a month for "ai software factory" and 1,100 for "software factory".

### Your own Search Console

Look for searches where you already rank between positions 3 and 20. Those are the cheapest wins: improve the page that ranks, or write the page the search is asking for.

### SparkToro

[SparkToro](https://sparktoro.com) shows where your audience spends time online and who they follow. We use it to find topics and people we wouldn't have thought of. As Alexis puts it: "Then you don't just look at the competitors to get keywords and topic ideas. You can also look at what those people are talking about."

### What AI already cites

Manicule's Sources view shows which pages and sites AI assistants cite for the questions you track.

Across the 15 questions we track for Manicule, Reddit is the most-cited site so far, with 183 of 1,262 citations, ahead of every company in our category.

That tells you where to publish as well as what to write about.

![Manicule Sources: the sites AI assistants cite most for Manicule's tracked questions](/blog/geo-keyword-research/manicule-sources.png)

## Prioritize

By now you have more topics and searches than you can write. This is how we decide what goes first.

### Bottom of the funnel, when it serves the core business

Comparisons ("X vs Y"), alternatives ("X alternatives") and best-of lists ("best X tools") are what people search for, and ask AI assistants, right before they pick a product. They go first when they're about what the customer actually sells, for the ICP that buys it. A comparison page that ranks but brings in the wrong buyers doesn't help.

For Supermemory, we posted a benchmark of Mem0 against Supermemory to r/LangChain, with the numbers up front. It ranks second on Google for "mem0 vs supermemory", right behind Mem0's own comparison page, and Google's AI Overview cites it:

![Google results for "mem0 vs supermemory", with the AI Overview citing the r/LangChain benchmark](/blog/geo-keyword-research/google-mem0-vs-supermemory.png)

These pages are easy to mass-produce, and Google treats that as spam. Its [spam policies](https://developers.google.com/search/docs/essentials/spam-policies) call it scaled content abuse: many pages made mainly to rank, with little value for readers. Each page needs a real comparison and real numbers, which is why we lean on benchmarks (we work with devtools, and their audience really likes benchmarks).

### Core topics first

A good topic lines up with the product, the positioning, and the ICP's pain points and the triggers that send them looking. Those go ahead of topics that only have search volume going for them. The blind spots from earlier usually land here.

### One to three topic areas at a time

We work topic by topic. Covering one area thoroughly is what builds topical authority: search engines and AI assistants start treating the site as a reliable source on that subject. The same number of pages spread across ten areas doesn't get you there.

Here's how Supermemory's vector database area came together, using the jobs from earlier:

![Topical authority: a pillar guide on vector databases, the specific guides under it, and a bottom-of-funnel comparison page](/blog/geo-keyword-research/topical-authority-diagram.png)

### Let intent decide the format

A pillar guide with specific guides and comparison pages under it is a common shape, not a recipe. What the searches in an area are asking for decides the format: some need a benchmark, some a tutorial, some a single reference page.

This is the prompt we use to turn the list into a plan:

```text
Here is our list of topics and searches: [list]. Here is the product, its
positioning and its ICP: [context]. Group the searches into topic areas and rank
the areas by how closely they match the product and the ICP's pain points.
For the top three areas, say what each search is asking for and which format
answers it best, mark the bottom-of-funnel pages, and say which pages should
link to which.
```

## Putting it together

This is the whole process as a checklist:

1. Work out whether your market is established or emerging.
2. If it's established, pull your competitors' top pages, find the content gap, move the top-of-funnel searches down, keep what fits your product, and widen the list with Claude and the customer's context.
3. If it's emerging, collect the questions from your customer's sales and customer calls, pick the topic areas around your product, map your buyer's jobs and journeys, and generate topics with Claude.
4. Check every search in Ahrefs, and treat volume and difficulty as estimates.
5. Fill the gaps with customer interviews, Reddit, X, Search Console, SparkToro, and what AI assistants already cite.
6. Prioritize: bottom-of-funnel pages that serve the core business, core topics first, one to three topic areas at a time.
7. Pick each page's format from what its searches are asking for.

Once the pages are live, track the questions behind them in AI assistants. That shows whether assistants start recommending you, and which pages they cite when they do.

Manicule does that tracking, along with the buyer journeys and Sources views shown above. You can [start tracking your own questions](/agent-visibility), or [have our team run this process for you](/services).
