Why we built an in-app community for AI search visibility (and what we're hoping to learn)

Last week a founder emailed me three sentences. "ChatGPT thinks my SaaS is a 2019 social-analytics startup that got acqui-hired. It's not. What do I actually do?"

I started typing a reply — schema this, llms.txt that, disambiguation paragraph here, file a feedback report on the wrong Wikidata entry. Halfway through I stopped. This wasn't a one-off email. It was the same five questions I'd answered in twelve different inboxes that month. Different domains. Different verticals. Same shape.

That's when I gave up on "I'll write a better blog post" and started building the thing you can now use: an in-app community for founders shipping in the age of AI search. It's live at /community with 22 seed threads across 6 categories and the room is open.

This post is the honest version of why it exists, what it does for GEO (and yes, also for SEO — they share more than the discourse admits), and what I'm hoping you'll teach me.

1. The five questions, over and over

Before I describe the room, here are the questions I keep getting. If you've emailed me in the last six months, you wrote one of these:

1. "ChatGPT is confusing my brand with another company. How do I disambiguate?"
2. "I shipped llms.txt. Nothing happened. Was that a waste?"
3. "My GSC clicks dropped in March and never came back. Is AI Mode eating my organic traffic?"
4. "Should I block GPTBot? Should I block OAI-SearchBot? Are they the same? They are not the same."
5. "I'm not in any of the answers. Where do I even start?"

None of these are answerable in a one-way blog post. They're conversations. They depend on your vertical, your domain age, what Wikipedia says (or doesn't say) about your category, whether Reddit has indexed your brand at all, and how Perplexity's recrawl lag is treating you this week.

A blog gives you my answer. A community gives you ten founders' answers — including the ones who tried what I suggested and found it didn't work for their case.

2. Why a community, not another blog

I'll be direct about the competitive landscape. The funded players in this space — Profound (Series C, $96M), AthenaHQ, Otterly, Peec — do not have open communities. Profound runs marketing content and gated webinars. Peec has an invite-only Slack. Athena has a customer-only forum. The independent founder shipping their first SaaS into AI search has nowhere to go that isn't either (a) generic r/SEO threads still arguing about TF-IDF, or (b) a paid agency newsletter.

That's the niche we're stepping into. Not because we're more clever than Profound — we are not — but because an open room is a different product than a closed one, and nobody has built it yet for this audience.

The honest second reason: I want to learn too.

I cannot index, alone, the patterns that 10 founders shipping in this space see every week. I see what my customers see. They see what their verticals see. A B2B legal-tech founder watching Perplexity cite a 2017 ABA Journal article instead of their post is data I do not have. A SaaS founder watching ChatGPT recrawl after three llms.txt iterations is data I do not have. The community is, transparently, a way for me to find out what I don't know.

TL;DR for skeptics: This isn't a "build a community" growth-hack. It's a "the questions I receive are conversations, and conversations don't fit in blog posts" decision.

3. What's already in the room

I didn't want to open an empty room. So before launch, I seeded the place.

The architecture:

• 6 categories: Citations & Mentions · Crawlability & Schema · GEO vs SEO · Tools & Workflows · Wins & Losses · Meta / Feature requests
• 22 seed threads drafted from real questions I'd been emailed plus 40 hours of research across Reddit's r/SEO, r/Entrepreneur, r/SaaS, and the indie-hacker spaces where these conversations were already happening
• 10 personas (1 is me, 9 are AI-generated archetypes labeled clearly as community-seed accounts so the room isn't a ghost town on day one)
• Daily cron drip that publishes 1-2 new seed threads per day for the first 30 days so the room feels alive while real founders post under their own profiles
• Reddit-style functional surface: replies, mentions, bookmarks, notifications, markdown support, anonymous-by-default posting if you want it

What the seed threads actually cover (in case you want to know what's there):

• A name-collision case study (founder vs. defunct 2019 startup with the same brand)
• Three llms.txt experiments — what moved, what didn't, what got recrawled
• A "9 months of nothing then broke through" thread about delayed AI citation onset
• GPTBot vs. OAI-SearchBot vs. ChatGPT-User: which one matters when
• Perplexity's recrawl lag vs. ChatGPT's — actual timing data from 4 domains
• Schema.org sameAs and foundingDate experiments (what made it into AI answers, what didn't)
• A GSC overlap drop in March 2026 — three founders comparing notes

Async by default. I reply on weekdays. No "active member" pressure.

Browse the threads now → — you don't need an account to read; you do to post. Read the community rules before your first post.

4. The SEO + GEO crossover (the part most people get wrong)

Here's the section I most wanted to write, because the public discourse on this is bad.

The reigning framing: "SEO and GEO are different disciplines. SEO is for Google's blue links. GEO is for AI engines. Throw out the playbook."

Reality: SEO and GEO share roughly 60% of their technical fundamentals and diverge sharply on the signals that actually move the needle.

Where they overlap (most of the technical layer)

If you've ever shipped a real SEO program, you already have these:

• Crawlable HTML semantic structure (<article>, <main>, <nav>, <section> with proper headings) — AI engines parse the same DOM tree Googlebot does
• Schema.org Organization markup with sameAs, foundingDate, description, sameAs to Wikipedia/Wikidata/Crunchbase — useful for both the Knowledge Graph AND for AI engines doing entity resolution
• sitemap.xml + correctly configured robots.txt — both Googlebot and OAI-SearchBot / PerplexityBot consume these
• Indexability (no accidental noindex, no JavaScript-only rendering where text matters) — same blocker for both
• Site speed and Core Web Vitals — AI engines weight freshness and crawl frequency, and slow sites get crawled less
• Internal linking density — context propagation works for both retrievers and crawlers

If your site is already SEO-clean, you are 60% of the way to GEO-clean. This is the under-told story.

Where they sharply diverge

This is where the playbooks split:

The Reddit story alone is worth a paragraph. In May 2026 Google's VP of Search confirmed AI Mode now surfaces "Community Perspectives" and "Expert Advice" labeled with creator name and source — that is, Reddit threads are no longer training data, they are visible labelled citations. The Tinuiti Q1 2026 data showed Reddit at ~40% of citation share for certain Perplexity queries. SparkToro's research has shown similar patterns for years on the human-discovery side. The implication: your category's Reddit threads are now part of your brand's AI surface area, and you can't backlink your way out of that.

What a community does for GEO, specifically

This is the load-bearing part. A community is not generic content. A community is a structured signal AI engines understand:

• DiscussionForumPosting is a recognized Schema.org type. Threads parse cleanly into AI engines' graph extractors.
• Comment[] sub-graphs are parseable. Multiple voices on the same topic = "expertise diversity" — a signal AI engines weight more than monologue blog posts.
• Real threads on specific narrow questions build topical authority faster than 5,000-word pillar pages. Especially if those questions match how people actually phrase prompts.
• Cross-domain mentions accumulate slowly but compound. A founder posts "we shipped llms.txt and saw X" in a thread → that thread shows up in cited_domains on a Perplexity scan six months later → that's a citation you didn't pay for.

What it does for the legacy SEO side

In case you still care about the blue links (you should):

• Long-tail keywords from real founder questions — every thread title is something a real person searched for
• High-quality UGC, not spam — moderated, real accounts, real domains
• Internal linking density boost — every thread links to its category; every reply links to its parent; mentions link to user profiles
• Topical clustering — six narrow categories instead of one generic "Forum" bucket

This is the deepest argument for building a community right now: SEO and GEO finally agree on what good looks like. Both reward real expertise, real discussion, real entity disambiguation. Both penalize content farms. Building a place where real founders talk about real problems is the rare move that wins on both fronts.

5. Technique vs. authority — the duality nobody quite names

A second pattern I want to flag, because it explains why most AI visibility tools (ours included, until recently) feel a little hollow:

There are two kinds of moves you can make in this space:

Technique — schema markup, llms.txt files, disambiguation paragraphs, query strategy, sitemap discipline, robot directives, OpenGraph metadata. Measurable. Optimizable. Mostly deterministic.

Authority — mentions in places AI engines trust. Citation density. Brand consistency across the web. "This domain shows up in conversations about this category." Built slow. Hard to measure. Compounds.

Most tools, ours included, focus heavily on technique because it's tractable. You can audit a robots.txt in 200 milliseconds. You can't audit "is your brand part of the conversation."

But AI engines increasingly weight authority signals — citation-of-citation patterns, expert recognition, recency of trusted mentions. A perfectly schema-optimized site with zero authority will lose to a messy WordPress blog with three years of Reddit threads citing it.

Honest read: I don't think anyone — not me, not Profound, not the 16 competitors I just audited — knows exactly which signals AI engines will weight in 6 months. The models change. The training cutoffs shift. The RAG configurations get re-tuned quarterly.

A community is partly a hedge against that uncertainty. Whatever AI engines weight more next year, real discussions among real practitioners are probably going to count. They're hard to game. They're slow to fake. They're the kind of signal that's expensive for spammers and free for legitimate operators.

6. Brand strengthening — yes, also for us. I'm not going to pretend otherwise.

I'd rather be transparent about the symmetry than pretend it's pure goodwill.

The community is good for users. It's also good for us. Here's the honest decomposition:

For users:

• A place to ask the actual questions, not the questions the blog post template wanted to answer
• Multiple perspectives — I am one founder, my answers are one data point
• Async, no pressure, no DMs, no LinkedIn-grade performance
• Direct line to me on weekdays

For us (GEO Tracker):

1. Better roadmap input. The 22 seed threads are already showing me three feature requests I would not have predicted from support tickets alone.
2. Distribution beyond cold outreach. My expert voice gets read by people who would never open a cold email from support@geotrackerai.com.
3. A moat that compounds. Funded competitors can ship features faster than us. They cannot fast-forward two years of accumulated founder discussions. Community is one of the few moats indie SaaS can actually build.

I'm telling you this because the "we built this for you, no really, no other reason" framing is what every brand says, and it's almost never true. The healthier dynamic is: this serves you, and it serves us, and those incentives are aligned, not opposed. A community that fails for users fails for me too. That keeps me honest about not turning it into a sales channel.

If at any point the room feels like it's drifting toward "thinly veiled marketing forum" — call it out in the Meta / Feature requests category. Publicly. I'll fix it.

7. What I'd love feedback on

Specific asks, in order of how much they'd help me:

• Post a real case study, even a failed one. "I shipped X, expected Y, got Z." Failed experiments are worth more than success theater. Especially welcome: things you tried after reading our blog that didn't work for your case.
• Push back when our advice doesn't match your data. If our GEO vs SEO 2026 post got something wrong for your vertical, say so. I will update the post and credit you.
• Tell me what the community needs that I missed. Bookmarks ship. Mentions ship. Notifications ship. What's missing? Saved searches? Per-category email digests? A "show me threads in my vertical" filter?
• Share what AI engines are doing that I haven't predicted. Google AI Mode is weird this month. Claude's web-search citations behave differently than Perplexity's. Surface the patterns you see. I'll aggregate them and publish back to the community.

If you'd rather email instead of post publicly, support@geotrackerai.com is open (it lands in my inbox — I read every founder mail). But honestly — a public thread is more useful, because the next founder googling the same question will find your answer.

FAQ

The questions I keep getting before people post their first thread. The same Q&A pairs ship as FAQPage JSON-LD on this post — same trick we're teaching.

Frequently asked questions

The same Q&A pairs ship as FAQPage structured data so AI engines can quote them verbatim.

Is this just another SEO forum?

+

No. It is scoped to AI search visibility — ChatGPT, Perplexity, Google AI Mode, Claude. Classic SEO topics (link building, keyword density, TF-IDF) are out of scope. Schema and llms.txt come up here because of how AI engines actually parse them for citation eligibility, not because they move blue-link rank.

Do I need a paid account to read or post?

+

No. Reading is fully public and unauthenticated. Posting requires a free signup — only to keep the spam floor at zero. No paid tier is gated behind the community itself, and there is no plan to introduce one.

Will Petr personally reply?

+

Yes, on weekdays. Asynchronously — usually within 24 hours, sometimes faster. This is not a synchronous chat or a Discord with presence indicators. You post, I reply, the next founder reading the thread benefits more than if it were a DM.

How is this different from Indie Hackers, r/SEO or Twitter?

+

Niche-specific (AI search visibility, not general marketing or general SEO), tactical receipts rather than theory ('we shipped X, here is the diff in our citations'), and founder-plus-peer led — not influencer-driven. The funded competitors in this space all run closed or invite-only communities; this one is open by default.

What is the deal with the seeded synthetic personas (ada.k, milan-novak, etc.)?

+

Honest disclosure: 10 personas seed the empty-room phase with threads drafted from 40 hours of Reddit research on real questions founders are already asking. They are marked as synthetic in the database, never auth-linked to a real account, and clearly labelled in the UI. Real users post under their own profiles. The seed drip ends at 30 days.

Can I post about my product?

+

Yes, if it is tied to a real story or a real fix — 'we shipped this and the citation rate moved' or 'this broke for us, here is what we learned.' What is not allowed: drive-by 'check out my tool' promotion, signature spam, or threads that exist only to link out. Full rules at /community/rules.

Will my posts get indexed by Google and cited by ChatGPT?

+

Yes. Every thread is server-rendered HTML with DiscussionForumPosting JSON-LD, included in the sitemap and surfaced in llms.txt. That is the same trick we teach across the rest of the blog — apply it to the community itself rather than hand-waving about it. Threads on narrow specific questions are exactly the shape AI engines prefer to cite.

How do you handle privacy?

+

Real users get a generic 'Founder' label by default — your handle and profile are not public until you opt in. Public Profile is a toggle in Settings; once enabled your handle is visible at /community/u/<handle>. Email is never shown. You can post anonymously per-thread if you prefer to keep your identity off-record entirely.

8. How to start

Three minutes, three links:

1. Browse the threads — start in the category that matches your current pain
2. Read the rules — they're short, the most important one is "no thinly disguised promotion"
3. Run our free Grader if you don't yet know your AI visibility baseline — most useful before your first community post, so you can describe your starting point
4. Optional: read the About page if you want to know who's on the other side

If you've got a question that's been bugging you for weeks — the one you've half-typed into ChatGPT and half-googled and gotten nowhere — that's the post. Go write it. Even if it's three sentences. Especially if it's three sentences.

I'll see you in the room.

— Petr

P.S. If you're reading this and thinking "should I really post the embarrassing version of my AI visibility problem in public?" — yes. That's the version that gets useful replies. The polished version gets nothing. We all started at GEO Score 0 (literally, in our case — here's the unflattering post about it).