1
0 Comments

486 visitors. 36% bounce rate. Here is the month that finally clicked.

Some months you build. Some months you find out if the building worked.

July was the second kind.

The headline numbers

Visitors: 486, up 263% from the prior period.
Sessions: 782, up 212%.
Bounce rate: 36%, down from 43%.
Session duration: 12m 36s, up from 11m 46s.
Page views: 11K.

That bounce rate is the number I keep coming back to. A few months ago it was the metric I wasn't celebrating. Now people are staying almost 13 minutes on average. That's not a traffic spike. That's people actually finding what they came for.

Where the traffic is actually coming from

Direct traffic led everything, 290 visitors and 6,030 views. That tells me something simple and good. People are typing the URL in or coming back on their own. Not chasing a one time link.

Organic search brought in 189 visitors. Referral traffic was smaller at 15 visitors but drove 4,466 views, almost entirely from one source doing a lot of quiet heavy lifting.

What Search Console says

Search Console tells a different story than the direct and referral numbers, and it's worth sitting with. 45 clicks from 16,800 impressions, a 0.3% CTR, average position 25.5.

That position number is the real headline. 25.5 means FutureStack is showing up. Google knows the site exists and is surfacing it for real queries. But it's buried on page 3 for most of them. 16,800 impressions is solid visibility. 45 clicks off that is a signal the pages aren't winning the click yet, whether that's titles, descriptions, or just needing more authority to climb.

The single biggest driver was "opus 5 vs fable 5." That lines up with what I saw in the on-site data too, comparison content pulling real visitors with low bounce rates. That's the format to lean into. When people are choosing between AI tools, they want the comparison laid out for them, not a database entry.

The gap between 16,800 impressions and 45 clicks is the actual project for August. Not a traffic problem. A "make the click worth it" problem.

What people did once they landed

The homepage pulled 162 visitors and 817 views, the front door working the way a front door should.

The real story is in the individual pages. The Arcade tool page brought in 49 visitors on its own. Two blog posts, one on free AI tools for writing and research, one comparing Opus 5 vs Fable 5, pulled in 25 and 24 visitors with genuinely low bounce rates. People are reading, not bouncing.

And /submit had 34 visitors with an 8.8% bounce rate, one of the lowest on the entire site. People aren't landing there by accident. They're showing up ready to submit a tool.

The part that isn't a celebration

/submit also had 28 rage clicks this month, more than any other page on the site by a wide margin.

That's not a vanity metric problem. That's real friction. People want to submit tools and something in that flow is making them click the same thing over and over hoping it works. Fixing that form is priority one for August. Every rage click on that page is a tool maker who wanted to be part of FutureStack and hit a wall instead.

The vision, said plainly

Here's the region I want FutureStack to own. Not just another place to browse AI tools. The place where people find their AI stack.

Right now every builder, creator, and team is quietly assembling a stack of AI tools without any real place to talk about it. When a new product launches, the first thing I get curious about is what's actually running underneath it. What model. What tools. What stack. That curiosity is universal, and nothing today is built to answer it.

That's the gap FutureStack fills. Not a directory of tools sitting in isolation. A place where you can see someone's actual stack, tool by tool, the same way you'd check out someone's setup. Go to a profile, see their stack. Curious what a product is built on, check their stack.

For now the focus is deliberately narrow. AI stack only. Not the whole developer toolchain, not general SaaS, just AI. Narrow enough to actually own the space, wide enough to matter to anyone building with AI right now. Maybe later that widens into the full tech stack, or just stack in general. But that's a later problem. Right now, AI stack is the whole game.

What I'm carrying into August

The traffic story is starting to work. Direct and organic are both moving in the right direction, and the pages that matter, tool pages and comparison posts, are holding attention instead of losing it in five seconds.

The job now is turning single visits into a habit, closing the gap between impressions and clicks, and fixing the submit flow so tool makers don't fight the form to join something they're already excited about.

263% visitor growth feels good to write down. But the number I'll actually be watching in September is retention. That's the one that decides if this becomes a real business or stays a good month.

We're constantly working on FutureStack. Come see what stack you're running.

usefuturestack.com

posted toAvatar for product FutureStack
FutureStack