3
9 Comments

I found a niche on Google Trends and built a product around it

Hello Indie Hackers,

Recently, I started spending some time looking through Google Trends to find topics that were suddenly getting more attention.

I wasn't looking for the next big startup idea. I just wanted to see if I could find a small topic that was growing and where people were starting to look for information.

That's when I came across WoW Forever.

WoW Forever is a newly launched game, and I noticed that searches for it were starting to increase after its beta launch.

That made me curious, so I started digging into what people were actually searching for.

I found that people were looking for things around the game's talent system.

For anyone who doesn't play the game, talents are basically choices that let players customise how their character develops. Players can choose different abilities and bonuses depending on how they want to play.

I found people searching for tools that could help them understand these choices and plan them before playing.

So I thought:

Why not build one?

That's how I started working on WoW Forever Talent Calculator.

What I built

The product is a simple tool where players can explore the available talent choices for all 9 character classes in the game and plan their choices in one place.

The goal isn't to build another massive gaming database.

I wanted to solve one small problem:

Make it easier for someone to understand their options and plan their character.

I started with the trend, not the product idea

This was the part I found most interesting.

Usually, I would start with a product idea and then try to find people who need it.

This time I did the opposite.

I started with something that was already gaining attention.

I looked at Google Trends, found WoW Forever, then went deeper into related searches to understand what people were looking for.

Once I saw that people were searching for talent planners and related information, I started thinking about what a useful product around that search behaviour could look like.

I don't know yet if this will become a big website.

That's not really the point of the experiment.

I want to see if starting with a growing topic and solving a very specific problem can be a repeatable way to find small product opportunities.

How I built it with AI

I also wanted to test how quickly I could take an idea like this from research to a working product.

I used AI coding agents for most of the development.

But I didn't just tell the AI to Build me a site directly. I first created the blueprint myself.

I worked out:

  • What pages the website needed
  • What information each page should contain
  • How the pages should connect
  • How users should move around the site
  • What the overall design should look like
  • How the talent planner should work

I then gave that blueprint and detailed instructions to the AI coding agent.

The AI handled a lot of the implementation, but I still had to review the output, test everything, find problems and keep refining the instructions.

The biggest thing I learned from this is that AI makes building faster, but it doesn't replace product thinking.

The clearer I was about what I wanted, the better the result was.

The SEO experiment

I'm also using this project to experiment with search intent and topical structure.

Instead of putting all the information on one huge page, I'm creating smaller pages around specific things people might search for.

For example, someone searching for a particular talent can land directly on that page, understand what it does, see its requirements and then explore related information.

Those pages are connected to each other, so users can continue exploring without having to start another search.

I'm interested to see whether this approach works better than simply creating a few large pages and trying to cover everything at once.

The goal is not just to create pages for Google.

If someone arrives from search, I want them to actually find what they were looking for.

What I'm learning so far

1. You don't always need a huge market.

A small audience can still have very specific problems that are worth solving.

2. Trends can be a useful starting point.

Instead of trying to guess what people might want, I started with something people were already showing interest in.

3. Follow the problem, not just the keyword.

Finding a growing keyword was only the starting point. The useful part was digging deeper to understand what people wanted to do.

4. AI makes small experiments much cheaper.

I could go from an idea to a working product much faster than I could have before AI coding tools became this capable.

5. The structure of information matters.

If you have a lot of related information, simply putting everything on one page isn't always the best experience. Breaking it into smaller, connected pieces can make it much easier to use.

6. Building is still easier than distribution.

The website is live now.

Getting the right people to discover it is the next challenge.

What's next?

I'm keeping the site free and ad-free for now.

I'm going to focus on improving the existing pages, watching how people use the product and seeing whether the search traffic turns into actual users.

I also want to see how far I can take this experiment without trying to turn it into a huge website.

For me, this is becoming less about WoW and more about a simple question:

Can you find small opportunities by watching what people are suddenly searching for, then build a focused product around a specific problem?

That's what I'm testing with this project.

I'd love to hear from other Indie Hackers:

Have you ever found a product idea by starting with search trends rather than an idea you already had?

What worked for you, and what didn't?

on September 23, 2026
  1. 1

    Nice work shipping it. What has been the biggest challenge since launch?

  2. 1

    As traffic arrives, what behavior would validate the opportunity beyond search demand—players repeatedly planning builds, returning before gameplay, or sharing the calculator with others?

  3. 1

    Nice work shipping it. What has been the biggest challenge since launch?

  4. 1

    Nice work shipping it. What has been the biggest challenge since launch?

  5. 1

    Really solid approach — curious how you're thinking about this, what's been the hardest part to figure out so far?

    1. 1

      I think marketing is hardest part

  6. 1

    Nice work shipping it. What has been the biggest challenge since launch?

    1. 1

      Honestly, telling AI Agent to do work properly

  7. 1

    This is great work — reminds me of some of the calls I've had to make building Xstream4K. What would you do differently if you started over?