Why Fridica Is Called Fridica: A Tool That Looks for Clues Instead of Guessing

The name Fridica did not come out of a branding meeting, and I was not looking for a name that sounded like another technology product.

Fridica is the name of my Cocker Spaniel.

If you know Cockers, you probably know that they experience a large part of the world through their noses. Clues are everywhere — you just have to find them. When I was thinking about how the SEO, AEO, and GEO analysis tool I was building should work, that association started to make more and more sense.

A website is full of clues.

Headings, page structure, internal and external links, canonical tags, metadata, structured data, content, relationships between pages, technical signals, search results...

The challenge is not simply finding them.

The challenge is understanding what they mean and what should happen next.

So the name stayed.

Over time, it also became a good metaphor for what I want Fridica to be.

I don't want another SEO traffic light

SEO tools can easily turn into collections of scores.

72/100.

Red.

Yellow.

Green.

Five more warnings.

Three more recommendations.

That information can be useful, but on its own it often fails to answer the most important question:

What should I actually do now?

More importantly, a score does not necessarily tell us whether we are solving the right problem.

We can technically optimize a page very well after choosing the wrong target keyword.

We can improve the title, H1, meta description, and content while the page is still not a good answer to the intent behind the search.

We can get an excellent result from a technical check and still not know whether we are trying to rank the right page for the right query.

That is why, while developing Fridica, I increasingly came to the conclusion that an audit cannot be the beginning of the whole story.

Before the audit comes the decision

One simple question significantly changed the direction of Fridica:

How do we actually know which keyword we should optimize for?

Not the one we happen to like.

Not the one that simply sounds logical.

Not the one AI suggested because it statistically looks like a good idea.

But one for which there are real signals that it makes sense for a particular page.

That is why Page Research became part of Fridica.

The tool first tries to understand the page itself: what purpose it serves, which topics it covers, and which services or information are actually present on it.

From that evidence, candidates for further research can emerge.

But that still isn't enough.

The next step is to look at the actual SERP and try to understand what the search engine is currently showing for that query.

Are people looking for a service?

A guide?

A product?

A comparison?

A local result?

Does our existing page even belong in that set?

Only then does it make sense to arrive at a decision such as:

optimize this page

or

research another keyword.

For me, that is much more important than trying to achieve a perfect SEO score at any cost.

A clue is not the same as a conclusion

This is especially important now that AI can explain almost anything very convincingly.

A convincing answer is not the same thing as good evidence.

That is why I wanted Fridica's core audit to be as transparent as possible.

If Fridica says that a canonical URL is missing, we should be able to see where the problem is.

If it says that six pages are affected, we should be able to see which six pages.

If it warns about a title, meta description, or structured data, the user should be able to see what was found and why it was flagged.

AI can help explain the result, suggest a next step, or turn technical information into understandable guidance.

But I don't want AI to become a substitute for the evidence itself.

So one of the ideas behind Fridica is very simple:

find the signal first, then explain it.

Not the other way around.

From “what's wrong” to “what next”

During development, a broader workflow emerged naturally:

Research → Understand → Audit → Fix → Verify

First, we research.

Then we try to understand what we found.

Next comes the audit.

After that, we need to help the user fix the problem.

And finally, we need to check again and see what changed.

Because SEO work does not end the moment a tool says that something is wrong.

If 14 pages are missing a meta description, it is not enough to tell the user:

“You have 14 problems.”

We need to show the pages.

Explain why the signal matters.

Suggest what should be changed.

And after the change, run the analysis again and verify the result.

Only then does an audit become part of real work rather than just another report we open once and forget.

SEO, AEO, and GEO are not three separate worlds

Fridica was conceived from the beginning as an SEO/AEO/GEO tool.

But I did not want three separate scores without context there either.

Traditional search, answer systems, and AI systems use different mechanisms, but all of them, in one way or another, try to understand content, structure, entities, sources, and relationships between information.

That is why Fridica checks different signals while trying to present them as parts of the same picture of a website.

It is also important to me that we are clear about what a particular check cannot claim.

A good GEO score is not a promise that an AI system will cite your website.

A good SEO score is not a promise of the number-one position on Google.

And a technically sound website is not automatically a relevant one.

A tool should show what it can actually verify — and be very careful about what it cannot.

Fridica should not make the decision for you

As the tool became more serious, it became increasingly important to me that it should not pretend to be the final authority.

The goal is not:

Fridica says you must do this.

I prefer something closer to:

Here's what we found. Here's the evidence. Here's why it may matter. Here's what you can do next.

In the end, a person still makes the decision.

An SEO professional may interpret some signals differently from a small website owner.

A developer will want to see the technical cause.

An agency will want to know how many pages are affected and how to verify the result after making changes.

Someone who is just getting started with SEO first needs to understand what is happening.

The same tool should be able to help all of them without hiding the evidence behind a single number.

That's why it's called Fridica

In the end, the name turned out to be much more fitting than I initially expected.

Fridica sniffs around.

She looks for clues.

She doesn't know in advance what she is going to find.

And that is exactly the approach I want from the tool that carries her name.

Not to come up with an answer first and then look for a way to justify it.

But to start with what is actually present on the page, across the website, and in the search results.

So today, I would describe Fridica's philosophy in one sentence:

Fridica shouldn't guess. It should find clues, show the evidence, and help people decide what to do next.

The first version of Fridica has now matured enough for me to start writing more about what we have learned while building it.

This blog will cover SEO, AEO, and GEO, the rapidly changing world of search, the development of Fridica itself, and practical problems I encounter while working on real websites.

And Fridica will, I hope, keep sniffing around. 🐾