What changed after I stopped building features and started optimizing discoverability
Hey Indie Hackers đź‘‹
A small milestone from my FriendRank journey.
A few weeks ago I thought the next step was to keep adding more features.
Instead, I decided to slow down and focus on something much less exciting, but probably much more important.
Making it easier for search engines and AI assistants to understand what each page is actually about.
Rather than publishing dozens of new pages, I've been refining the ones that already exist.
Some of the work included:
• clarifying the purpose of individual landing pages
• reducing overlap between similar pages
• improving internal linking
• making each page answer one specific user intent instead of trying to rank for everything
One lesson surprised me.
It's tempting to constantly "do more".
But sometimes the better decision is to stop building and let the data tell you what actually needs improving.
For now I'm trying to follow a much simpler cycle:
→ improve one page
→ deploy
→ wait
→ measure
→ repeat
It feels slower, but it's also much more evidence-driven.
It would be nice to know how other founders approach this stage.
Do you keep shipping new features, or do you spend time improving discoverability before expanding the product further?
Give each page one query cluster and one business outcome, then freeze other changes long enough to read indexed impressions, clicks, signup, and activation. If impressions rise but activation does not, discoverability worked and intent or product fit did not. That separation keeps “wait and measure” from becoming an unbounded pause.
The interesting shift isn't optimizing for search engines or AI discoverability—it's recognizing that adding more features can reduce clarity instead of increasing value. I'd keep validating whether your biggest growth gains come from expanding the product or from making it easier for the right users to immediately understand why each page exists. That's a decision many founders delay making.
That's exactly the trade-off I'm trying to understand. It's surprisingly easy to mistake "more pages" or "more features" for progress, when sometimes the bigger win is making the existing product easier to understand, for both users and search engines. Thanks for sharing your perspective Aryan.
Exactly.
One thing I'd keep watching is whether each new page or feature creates a clearer path for the right user, or simply creates more places where users can get confused.
More surface area only helps when the underlying message stays coherent.