Building Nozoni: an anime visual discovery hub

I’m building Nozoni, an anime visual discovery hub.

The idea came from a simple behavior I kept noticing: a lot of anime discovery starts with an image, not a title.

Someone sees a key visual, a character crop, a poster, a fan art style, or a screenshot on social media. They do not always know the anime name yet. They just know the visual looks interesting.

Most anime sites are still built the other way around. They work best when you already know what to search for.

That is the gap I want Nozoni to work on.

Why visual-first discovery

Anime databases are useful. I am not trying to replace them.

They are great for structured information: titles, studios, staff, release dates, episode counts, ratings, and franchise metadata.

But they are not always great for the moment before the user knows the title.

That moment is messy. The user might only have:

an image
a character design
a visual style
a franchise clue
a cropped poster
a memory of “that one anime with this look”

Nozoni is built around that entry point.

The image should not just be decoration on the page. It should be a way into the anime, the character, the franchise, and the surrounding context.

What I mean by an anime visual discovery hub

For me, this is not just an image gallery.

A gallery can be fun, but it becomes shallow if every image is disconnected. The useful part is the relationship between things.

A key visual should connect to the anime page.
A character image should connect to that character and franchise.
A news article should connect back to the official visual it is talking about.
A search result should help the user keep moving instead of ending at a dead thumbnail.

That is the product shape I am working toward.

Nozoni has to be part visual search, part anime hub, part media graph, and part editorial layer. It is a weird mix, but that is also why I think it is interesting.

Why I added articles

At first, I thought the product could mostly be visual pages.

Then I hit a very obvious problem: visuals need context.

A page can look good to a human and still be thin for search. Google also needs text that explains what the page is about, why the image matters, and how it connects to the topic.

So I started adding a small editorial layer around Nozoni.

A few examples:

These are not meant to be random blog posts. They are category-definition pages.

They help explain what Nozoni is about before the product is big enough to explain itself through usage alone.

I also wrote a longer product note here:

Building Nozoni: An Anime Visual Discovery Hub

The SEO side of this

One lesson so far: for a niche product, homepage copy is not enough.

If you are building something slightly new, you need pages that explain the idea from multiple angles. Not keyword-stuffed pages, but useful pages that make the product category easier to understand.

For Nozoni, that means writing around topics like:

anime visual discovery
finding anime by image
anime key visuals
visual-first anime browsing
how Nozoni differs from database-first anime sites

This is partly SEO, but it is also product positioning.

If people cannot understand the category, they will not understand why the product should exist.

What I am focusing on next

Right now, I am trying to make the connections stronger.

The work is less about adding more pages and more about making each page lead somewhere useful.

If someone lands on an image, where should they go next?
If someone reads a news article, can they get to the related anime or visual?
If someone searches by style, can the product suggest a useful path instead of just returning a random grid?

That is the main challenge.

The long-term version of Nozoni is not just “anime pictures on a website.” I want it to become a better way to move through anime visuals, characters, franchises, and official updates.

Still early, but the direction feels clear enough to keep building.

You can check it out here: Nozoni

And if you want the more detailed product note:
Building Nozoni: An Anime Visual Discovery Hub

I’d be curious how other builders would prioritize this: image search first, franchise pages first, character pages first, or editorial/news context first?

推荐订阅源