1
5 Comments

Is building an AI tools directory in 2026 just a terrible idea? I'm 4 months in and I genuinely don't know anymore.

I need to say something out loud because it's been sitting in my head for weeks.

I'm building YourAIFinder — an AI tools directory with a comparison feature, a price explorer, and a daily curated picks page. I work full time at an HRMS company in Mumbai and I build this on evenings and weekends. Two months in, 13,000+ impressions, 25+ real clicks from actual humans.

And lately, every time I open my laptop to work on it, I have this quiet voice asking: is this actually a good idea?

Here are the three doubts I can't shake. Tell me if I'm wrong.


Doubt 1: Google is going to answer this query itself and make me irrelevant.

Someone types "best AI tool for writing Instagram captions." Right now, Google shows a mix of blog posts and directories. Now AI Overview that just answers the question directly, with no click required.

Every directory — not just AI directories, all directories — is sitting on a ticking clock. The more useful Google's AI answers get, the less reason anyone has to visit a curated list made by a human.

Am I building something that's already being automated out of existence?


Doubt 2: I'm 3-4 years too late.

Futurepedia launched in 2022. There Are No Alternatives launched in 2022. Toolify, AI Tool Hunt, every major player — all 2022-2023. They have millions of backlinks, hundreds of thousands of indexed pages, and brand recognition I will never catch up to.

The SEO window for "AI tools directory" as a category might already be closed. The people who got in early captured the domain authority and the links. The rest of us are fighting for scraps.

Is there even a second-mover advantage in directories, or did I just miss the bus entirely?


Doubt 3: Nobody actually uses directories to make decisions.

When you personally need to choose between two AI tools — do you go to a directory? Or do you Google "[Tool A] vs [Tool B]", land on a Reddit thread, read three opinions from strangers, and make your call?

I do the second thing. Every time. And I'm the person building the directory.

If even I don't use directories to make decisions, why would anyone else?


Here's where I land, at least today:

I think Doubt 1 is real but slow. AI Overviews are getting better but they're not killing niche, structured comparison content yet — and maybe won't for a while.

I think Doubt 2 is mostly wrong. The big directories are bloated and generic. There's room for something more specific and better structured — I just haven't proven it yet.

Doubt 3 is the one that keeps me up. I don't have a good answer to it.

I'm still building. But I'm building with this knot in my stomach that I can't quite untie.

Has anyone here actually cracked a directory in a crowded space after 2023? Or successfully pivoted a directory into something that isn't purely SEO-dependent? I'd genuinely love to hear it — not for motivation, but because I'm trying to figure out if there's a path here that I'm not seeing yet.

on July 13, 2026
  1. 1

    Honestly, "is this a bad idea" was the question I had to answer
    for myself when I started saas.pet. I run a review site (245
    hand-tested reviews now) and the answer I came to isn't "is
    AI tools directory a good idea" — it's "what specifically is
    your wedge."
    The thing that made the difference for me wasn't pSEO or
    traffic strategy. It was: when someone reads my review, do they
    get something they can't get anywhere else? Concretely:

    • Honest numbers (GitHub stars, last commit date, official-site
      reachability — and explicitly saying "I do not cite GitHub
      stars as quality because they can be inflated")
    • An alternatives page for every review (which is how Perplexity
      cites me — I went from 0 to first-cited within a few weeks)
    • A "Tested by Alex" stamp with how many days I actually used it
      Those three things together are not pSEO. They're just:
      "this review took me work to write and it's specific to me."
      The day I started doing that instead of scraping the same 500
      tools with the same "10 best AI X" titles, traffic started.
      Re: Google AI Overviews eating the query — you're right, the
      "best X" queries are getting absorbed. The queries that aren't
      absorbed are the long-tail ones with real intent ("X for Y"
      where Y is a specific job-to-be-done). I now write 70% of
      new content as "X for Y" instead of "best X" and the AI
      Overview can absorb the broad query all it wants — the
      specific one still needs a real source.
      To your Doubt 3 specifically: I'd flip the question. Don't
      ask "is directory a good idea." Ask "if I do it differently
      than the bloated ones, do I have evidence yet?" If not, keep
      running the experiment. The signal shows up in the data, not
      in the fear.
  2. 1

    Focusing on head-to-head verdicts is the right move, especially since AI math struggles with the messy, subjective trade-offs in real tool comparisons. For deeper reasoning on why some comparisons resist automation, I’ve found ai math from Logical Intelligence useful for understanding how such tasks require more than surface-level logic.

  3. 1

    I’d focus on those head-to-head comparisons you can only get from hands-on testing. That’s where real value lives.

  4. 1

    your own numbers already answer doubt 1. 13k impressions and 25 clicks means you're ranking on queries the SERP finishes without you, which is exactly what a catalog page is for.

    doubt 3 isn't the flaw, it's the spec. you reach for the reddit thread because you want someone who used both and will say which one broke. a feature table is what an AI overview can regenerate for free. a verdict with receipts is not. i'd take the 20 "a vs b" queries you'd actually bet on, use both tools properly, and publish the loser.

    1. 1

      This reframe actually helped.

      The 13k/25 split I read as failure — you're reading it as a signal about what type of content I'm building. Catalog pages serve a different job than verdict pages, and I've been trying to make one do the work of both.

      On doubt 3 — "a verdict with receipts" is the exact gap I've been circling without naming it. My compare pages right now are feature tables. Useful for scanning, but easy for any AI to regenerate. What I can't outsource is actually using both tools under real conditions and publishing what broke.

      I've been avoiding that because it sounds like a lot of work per post. But if 20 head-to-heads I actually believe in convert better than 200 catalog pages, the math might still work.

      Going to pull my top a-vs-b queries from GSC this week and see which ones I can actually go deep on. Will report back.