About us
A small project with one concrete thesis: visibility in AI starts with a technical requirement that can actually be checked. How we work, and what we don't do.
Why it exists
When AI assistants started sending traffic, a whole industry appeared overnight promising to «rank you in ChatGPT». Almost everything on sale was an estimate presented as a measurement: share-of-voice figures worked out from a handful of questions the vendor picked, which shift on their own whenever the model is updated.
Meanwhile, a huge share of websites in Spain and Portugal fail at something far more basic and far cheaper to fix: AI crawlers cannot get in, or they get in and find no text to read. A Disallow left over from the development phase. Content that only exists once JavaScript has run. A firewall that hands a challenge to anything it doesn't recognise.
That much can be checked. It isn't an estimate, it doesn't depend on the sample and it doesn't change between runs. It is dull, and it is the prerequisite for everything else: however good your content strategy is, none of it matters if the crawler hits a 403.
This project does only that, and it does it for the Spanish and Portuguese markets, where nearly every tool in the field arrives half-translated or never arrives at all.
How we work
Every one of them can be verified: look at the user agent we request with, at how the score is calculated, or at the list of pages that shows up in your report.
Our requests identify themselves with their own user agent and a page explaining who we are and how to block us. To find out whether GPTBot can get into your site we don't pretend to be GPTBot: we evaluate your robots.txt with the same rules they apply.
Our crawlerIf your server doesn't return the HTML, we don't invent a verdict about something we haven't seen. That item is declared inconclusive and drops out of the calculation. Rounding it up would be lying with a number.
If the crawlers can't get in, it makes no difference how good the rest is: the score keeps a ceiling. An arithmetic mean would hide one fatal problem behind fifteen minor wins.
How it's calculatedThe home page tends to be the least representative page of a site: static and polished, while the real content lives elsewhere. We walk through pages from different sections and tell you how many of them each problem shows up on.
If the connection drops, if we run out of time or if something breaks at our end, we say so plainly. What we don't do is write it into your report as though it were a problem with your site.
When choosing which pages to visit we respect your own crawl rules, and we cap how many consecutive requests go to the same domain. It would be incoherent to ask you to let bots in and then behave like a rude one.
What we don't do
Nobody can do that reliably from the outside. It depends on your brand, your authority and your competition, and none of those three things can be measured with an HTTP request.
Those numbers depend on the questions you pick, they change between runs and they drift on their own when the model is updated. They can be measured; what they can't be is presented as hard data.
Analysing your site requires no sign-up, no email and no accepting anything. Analytics and advertising cookies load only if you accept them, and turning them down costs one click — the same as accepting them.
It is used to send you what you asked for and, if you tick the separate box, for content of our own. Nothing else, and you can unsubscribe in one click.
Your data
Analyse your site and judge it by the result. Free, no sign-up, and it takes seconds.