Found in AI

How to Make Your Content Show Up in AI Search (with SEOforge’s Alex)

Cassie Clark Episode 4

Send us a text

📬 You like this podcast? You’ll love the newsletter.
Join the weekly 3-2-1 on AI search + marketing: subscribe

In this episode of Found in AI, I sit down with Alex, co-founder of SEOforge, to dig into what’s actually working in AI search right now. We cover:

  • How to track and attribute high-intent traffic from ChatGPT.
  • Why unique insights matter more than keyword targeting in LLM answers.
  • The surprising differences between what ranks on Google vs. ChatGPT.
  • How to structure Help Centers (one question per article) so AI search engines cite your brand.
  • Why hosting FAQs on your main domain — not a subdomain — is critical for conversions.

If you’ve been wondering how to build content that gets cited in AI search results — and where to start — this episode is for you.

📌 Mentioned in this episode:

  • ChatGPT vs. Google search differences
  • High-intent traffic from AI engines
  • Help Center SEO/AEO structure
  • Unique insights and proprietary data in content
  • llms.txt and crawler behavior

💬 Let’s connect:
LinkedIn → Cassie Clark | Content Strategist
Website → cassieclarkmarketing.com

Keywords: AI Search, ChatGPT Traffic, SEOforge, AEO, Answer Engine Optimization, Help Center SEO, FAQ Schema, Unique Insights, AI Content Optimization, Startup Marketing, B2B Content Marketing, Digital Marketing Trends

Find the show notes and transcript here.

(Transcribed by TurboScribe.ai. Go Unlimited to remove this message.) Every content marketer is asking the same question right now. What actually works in AI Search? If we haven't met yet, I'm Cassie Clark. I'm a content strategist who helps startups and B2B brands get seen. And now that AI engines are part of how people search, that means creating content that shows up in AI-generated answers. In today's episode of Found in AI, I'm joined by Alex, co-founder of SEO Forge. He's been deep in the trenches testing how chat GPT, perplexity, and other LLMs serve as content, and what startups can do to actually earn that high intent traffic. We dig into what's different about AI Search, why unique insight matters more than keywords, and how to structure help centers so LLMs pick up and cite your brand. Here's part of that conversation. So I've seen a lot of people talking about like the traffic that comes from these AI search engines, I guess is the right way to call them, that those are like your high intent customers, like the ones that will convert. Did you just flat out ask them how they found your brand? Like, how did you know that they came from chat GPT and not from Google or wherever else? Yeah, so we did two things. So at first, we just saw in Google Analytics, we had first analytics as well. So we could see people directly coming from chat GPT. And we had pretty good tracking setup. So we could see, you know, if someone came from this source, would they sign up? Would they convert? So we directly saw who those people were. But secondly, we also added a question in our onboarding, where we asked people, how did you hear about us? And we just added an option immediately that said, chat GPT. Honestly, we thought about saying just like LLM, AI search, but we saw only traffic from chat GPT at that time. So we just added an option for chat GPT. And that's how we knew they're coming from chat GPT. Yeah, so chat GPT seems to be the one that I use the most. Are you seeing traffic from Perplexity and all the other places? I would say Perplexity is the second one, but it's still very far away from chat GPT in terms of just quantity of traffic. And then I've seen Gemini as well. And when it comes to Cloud from Anthropic, I have seen traffic from it too, but only really towards deep tech startups and companies. So not really like, let's say, a healthcare company. I haven't really seen Cloud traffic to them. So that must be industry specific. Exactly. Yeah, yeah. So tell me about how SEO Forge works. Like, I know Google Analytics, it seems similar, but this is with AI search and not just Google. So tell me how it works. Yeah, so what we've done, you know, is we've taken the experience we've gathered over the past seven months into understanding, like, just outside any platform, like what strategy works, what kind of content do you need to push? Is it different from just normal SEO and so on? And we took that and then we combined it with the fact that we had a few platforms that we've developed before, where basically people, you know, they can talk with multiple LLMs at the same time. So like chat GPT, Gemini, and so on. And we kind of understood how people use LLMs to get their questions answered. We could see whether they click citations or whether, you know, they just copy the name of the company and then they paste them to Google. So we had some insights into that. And the platform that we came up with is basically we create a set of prompts for you. And we do that by, you know, scraping Reddit. So, you know, finding user generated prompts. We look at LLM conversations and try to get actual prompts and questions that people ask from there. And we also try to tie it in with, you know, keywords from Ahrefs and long tail keywords and so on. And we track those on a weekly basis. And the way we do this, we don't do it through the APIs. We actually try to, you know, see how a user would see it on the interface. And then when we give you the responses back, we actually try to analyze the responses and tell you there's, you know, maybe you have a content gap, like why is this competitor mentioned and you're not mentioned here? Or why is this competitor citing or not? So that's kind of the initial thing we do. And once you ramp up content, if you don't have any content or if you already have content, we actually try to create a set of prompts just around that piece of content to try and understand what's driving traffic to that piece of content specifically. And we try to adjust the content based on responses from LLMs and best practices. We just wrapped up a study on about 500,000 user queries and we executed them on ChatGPT and Google Search as well. So we found some differences between what ranks on Google and what ranks on ChatGPT. So we usually give our users just the list of instructions where, hey, those are the things you need to do. We want to get more traffic from ChatGPT, so we just try to help them using the platform to try and get more traffic using those strategies. So are you seeing a big difference in what's working for Google and what's working for ChatGPT or the other LLMs? There are differences, I would say. What's interesting to me is, and this has been circulated around a lot, but on Google you see 10 blue links, right? And then on ChatGPT, you just see a long piece of content. Sometimes there could be 16 citations, sometimes I see five, so it's really different. But most of the people, I would say they get what they're looking for directly within the content from ChatGPT, so they don't need to go beyond it. And what we found works best when it comes to getting more traffic from ChatGPT, but not necessarily from Google, is having unique insight. So imagine on Google, someone could ask a very broad question or just type in a keyword that's quite broad, and then you have a bunch of pages ranking just because they've optimized for so long directly towards that keyword. But in ChatGPT, we've noticed that the longer a conversation goes, the more specific the questions get. So if someone asks very, very specific questions, that could mean they have very high intent in finding a solution. And if you have that insight that could help them, it doesn't matter if you've optimized towards that keyword. If ChatGPT crawled you, you know, if the crawlers from OpenAI crawled your content, ChatGPT is very likely to cite you. So we usually push people to really have unique content and to bring unique perspective to content, so we don't advertise or push for AI slop or nothing like that generic content. And apart from that, there's also, but this has been circulating in the SEO world for a long time, but doing technical SEO properly, so using schema, having proper H1, H2, H3 headings, having an FAQ, I saw your post, by the way, that mentioned that. We also push for, you know, a larger FAQ is just the help center. So we've seen great results from help centers too. So we push people to do those things and to bring unique data and insights forward. And if they don't have it, to go and try and get it from their users or carry out surveys, you know, things like that. And that's been working really well for ChatGPT. But of course, for Google, it takes a bit longer to rank just because, you know, you can't just have a one day old domain that just does really well on Google. Right. So there's a couple of different things I want to hit on there. So I read a post, I don't remember who posted about it, where they were changing the name of their blog from just linking the blog at the top to like content hub or knowledge user base or something like that. So that's interesting, but it's still linked to their blog. So you would suggest just having a whole separate entity on your website that was just FAQ with like deeper things, like here's one article on, I don't know, how to use our product. And then you go into another one. So it's almost, in my mind, it's almost like you have two blogs, but one is just dedicated straight to just how to. Am I thinking about that correctly? Yes, you are. So basically, the way the Help Center is structured differently to just the blog, let's say, is that in the Help Center, all of the titles are just questions. And there's only one question per article. So there's no like, we don't have, we haven't incorporated H2s or H3s. It's literally just that one long form answer. And it's basically things that you wouldn't normally answer within a blog post. So if you want to dive deep into what your platform is capable of, or if you want to, let's say, talk about the user pain point in detail, and let's say you don't really cover that on a blog post already, but you want to have that content quickly, we recommend adding it to the Help Center. That's a really neat idea. And I'm thinking about how I can do that for my own website. I'm not sure that'll take some more planning. But you're seeing like the clients that you work with who are doing this, they're seeing results from that already? Yeah, that's been working really, really well. The only thing that I would say to keep in mind, for you and for anyone who will watch this, is there's lots of tools out there and platforms that allow you to build Help Centers. But most of those tools force you to host the Help Center on a subdomain. So like help.domain.com. And that actually, while the Help Center leads to quite a bit of tragedy traffic, that traffic is not as useful because you can't really convert people from going to the Help Center to your website or to your intended button or action. So we usually recommend, even if it takes a bit more time, having that Help Center directly on your website, similar to how you want to have a blog deeply integrated into your website to convert more people. That conversation gave me a lot to think about. Especially the way Help Centers can pull in high intent traffic if you structure them the right way. Over the next few weeks, I'll be adding in some of those help desk style articles to my own website and testing how they perform an AI search. I'm Cassie Clark, a fractional content strategist who builds AI search ready content systems for startups and B2B companies. If you want to talk about how we can make your content work harder in this new search landscape, connect with me on LinkedIn or visit cassieclarkmarketing.com. Next week, I'll share what I know about how AI search picks the answers to service. Stay tuned, I'll see you then.