What does my website actually say I do?

To find out what your website actually says you do, read it the way a stranger would: with no context, no product knowledge, and no patience. This tool does that. It fetches your homepage, reports how much readable text it actually contains, and says in plain language what you appear to sell, who you appear to sell it to, and what problem you appear to solve. Where it could not work something out, it says so, and that is usually the most useful line it produces.

No signup. The result is yours before we ask for anything.

Run it on your own domain

How this works

1We fetch your homepage and extract the readable text, reporting whether it came from the page body, the page data, or only the title and description.
2We report the character count of what was readable, which is often the finding on its own.
3We state what you appear to sell, who for, and what problem you solve.
4Where any of those could not be determined, we say so rather than guessing.
5We quote the text the reading rests on, so you can check it against your own page.

What it cannot tell you

We read one page. A site can explain itself well on a page we did not read.
We are not judging whether your positioning is good, only reporting what a stranger would take from it.
A page that renders after JavaScript may show more to a human browser than we could read.

Questions people ask

Why does nobody understand what my company does?

Usually because the homepage describes a product without naming a reader. The founder cannot see it because they know who it is for, and the page never has to say. A stranger reading the same words has no way to place themselves in it.

How much text should a homepage have?

Enough that somebody who has never heard of you can say what you sell and who for. In practice that is more than a headline and a screenshot. A page returning under two hundred characters of readable text cannot be summarised by a person or a crawler.

Does it matter if my site needs JavaScript to render?

It matters for anything that reads without running it, which includes some crawlers and most automated readers. If your words only exist after hydration, what you say about yourself becomes a coin flip.

The short version, if you would rather not run it

The most common problem with a homepage is not that it is badly written. It is that it never names a reader. A page that describes a product in careful detail and never says who it is for leaves every visitor to work out whether it is for them, and most will not bother.

The second most common problem is that there is nothing to read at all. Modern sites can render a headline, a screenshot and a call to action, and contain almost no text. That reads fine to a human who already knows what you do and is invisible to anything that does not.

The test worth running is simple: hand your homepage to somebody outside your industry and ask them who it is for. If they hesitate, the page has a naming problem rather than a writing problem, and it is fixable in a sentence.