how FlowIntent built its own SEO presence from zero — and what we learned doing it

we built FlowIntent to help founders and content teams win at SEO and AI search. the uncomfortable truth: when we launched, we had no organic presence of our own. zero. the cobbler's children problem, applied to AEO.

this case study is the honest account of how we built FlowIntent's own SEO and AI search presence over 6 months — the strategy, the tools, the mistakes, and the numbers.

we're sharing it because our clients deserve to see that we practice what we advise. and because the process of doing it for ourselves taught us things we couldn't have learned any other way.

where we started

month 0 state:

• domain age: 4 months
• published content: 1 blog post, 1 case study
• organic sessions: 180/month (mostly branded)
• AI engine mentions: 0 across all tracked queries
• keywords ranking: 0 in top 100
• backlinks: 12 (all from launch announcements)

we knew the strategy. we'd built the tools. we had keyword data, content frameworks, the AI presence audit workflow, the full stack. what we needed to do was run it on ourselves — consistently, over time, with the same discipline we ask clients to apply.

month 1–2: topical foundation

we ran FlowIntent's own content gap analysis against r/SEO, r/juststart, r/digitalnomad, r/founderslack, and r/Entrepreneur. the queries that kept appearing:

• "what is AEO and does it actually work"
• "how to get your site cited in Perplexity"
• "SEO for founders who aren't SEO experts"
• "do AI overviews hurt traffic"
• "topical authority — how long does it actually take"

we published 8 pieces in months 1–2, each targeting one of these question clusters. answer-first structure, question headers, FAQ schema, 800–1,600 words. no fluff, no padding.

results by end of month 2: 3 pieces appeared in Perplexity answers. zero top-10 rankings (domain too new). but AI citation doesn't require domain authority — it requires the right structure and the right answer.

month 3–4: building the cluster

months 3 and 4 were about depth. we identified 3 topical clusters where we wanted to own the conversation: AEO (answer engine optimisation), AI brand visibility, and topical authority strategy.

for each cluster, we published a pillar piece (2,500–3,500 words) and 4–6 supporting pieces (800–1,200 words). the supporting pieces answered the specific questions the pillar couldn't cover in depth without becoming unwieldy.

total content output months 3–4: 22 pieces. average time per piece with the FlowIntent plugin workflow: 90 minutes to 2.5 hours.

the clusters started showing topical authority signals in month 4: Google began ranking supporting pieces for queries we hadn't explicitly targeted but that were semantically adjacent to our core topics.

month 5–6: the AI visibility push

by month 5, we had enough content indexed to run a meaningful AI presence audit. the results:

• FlowIntent mentioned in 14/40 tracked queries (35%) — up from 0
• Perplexity was citing us most frequently (9 queries)
• ChatGPT and Gemini: 3 queries each
• Grok: 2 queries, one with an inaccurate description

months 5–6 focused on the gaps. we built definitional content for the queries where we weren't appearing — and corrected the Grok misattribution with a clear "what is FlowIntent" piece that left no ambiguity about our category.

we also published 3 original research pieces in month 6 — data from our own AI monitoring across 50 client accounts, anonymised and aggregated. original data earns citations. these 3 pieces generated more backlinks in 6 weeks than all previous content combined.

results at 6 months

organic sessions (month 0): 180/month → (month 6): 11,200/month keywords in top 10: 0 → 47 AI engine mentions: 0/40 queries → 28/40 queries (70%) engines citing FlowIntent: 0 → 6 backlinks: 12 → 340 inbound trial signups from organic: 0 → 280/month paid conversions from organic: 0 → 34/month

what we got wrong

three honest mistakes:

mistake 1: publishing too broadly at first. our first 8 pieces covered too many topics. we should have gone deep on one cluster first, built the topical authority signal, then expanded. we lost 4–6 weeks of compounding by spreading too thin initially.

mistake 2: underestimating the link gap. domain authority matters more than we expected for competitive queries. we had the right content but were outranked by older domains with weaker pieces purely on authority. the original research push in month 6 was what broke through — it earned links that moved our DR from 12 to 34.

mistake 3: not tracking AI mentions from day 1. we started systematic AI monitoring in month 3. we should have had it running from launch. we couldn't measure what was or wasn't working for the first 8 weeks.

what we'd do differently

if we were starting FlowIntent's SEO from zero again:

1. pick one topical cluster and go 10 pieces deep before touching anything else
2. set up AI mention monitoring on day 1 — not month 3
3. publish one original data piece in month 1 to start link earning early
4. write the definitional content (what is FlowIntent, what does FlowIntent do) before writing anything else — AI engines need to know what you are before they'll recommend you

the honest version of how long it takes

6 months to 11,200 monthly organic sessions and 70% AI query coverage. that's with a consistent 3–4 pieces per week publishing cadence, the full FlowIntent tool stack, and a founder (me) who knew the strategy before we started.

without the tool stack, I'd estimate 9–12 months for similar results. without the systematic AI monitoring, we'd have been flying blind for most of it.

SEO and AI search visibility compound. the first 3 months feel slow. months 4–6 feel fast. the compounding is real — but only if you're consistent.

related reading: Topical Authority in 2026 — the strategy behind the cluster approach we used and why it still works. | How We Track AI Brand Visibility — the monitoring setup we should have built from day 1.