A GEO checker that scores any page for AI search

GEO stands for generative engine optimization. It asks whether ChatGPT, Perplexity or an AI Overview can read your page, trust it and quote it, where SEO asks whether Google will rank it. The two overlap, which is why both tools ship in Hoverify and sit next to each other: the SEO panel covers Core Web Vitals, meta tags, headings and links, and GEO covers structured data, machine readability, citability, entity signals and the crawler files AI systems look for.

Each check lands as a pass, a warning or a fail, worth full points, half, or none. A fourth verdict covers tips that should not count either way, and those stay out of the arithmetic. The rest roll up into 16 categories, each carrying its own weight: structured data and machine readability count 1.5x, citability 1.3x, agent interactivity 0.2x. The 0 to 100 score is the weighted average of the ten technical categories, and the grade follows from it, with an A at 90, B at 80, C at 70 and D at 60. A category with nothing to score drops out of the average, so a page is never marked down for a standard it doesn't use.

llms.txt is a plain text file at the root of a site that points LLM crawlers at the pages worth reading, in the way robots.txt gives search crawlers their rules. It is a proposed convention rather than a settled standard, so nothing breaks without it. Hoverify checks whether you have one, along with llms-full.txt, your sitemap, an MCP server card, an A2A agent card and a handful of other emerging files, and treats the optional ones as tips rather than failures.

Open the panel on a page and it audits that page there and then. You get the score, the grade, the page type it detected and a ranked list of the weakest checks, so the answer arrives as a number and a to-do list. Scan again after a change and the History tab puts the new score next to the old one.

Yes, for everything read from the page: structured data, headings, links, images, text ratios and the rest run on whatever you have open, including a members area or a local build. The off-page probes are the exception. Checks for robots.txt, llms.txt, your sitemap and the agent card files need the origin to answer a request, so where it can't they report that they couldn't be fetched rather than counting against you.

Nowhere until you switch it on. The feature stays off until you add your own OpenRouter key and choose a model in settings. After that, an audit sends the page's address, its title and description, its visible text, the Schema.org types in its markup, a sample of its image alt text and a count of the images missing it, all to the model you picked by way of OpenRouter. That address is the full one from your URL bar, query string included, which is worth knowing if you audit a page behind a login. Your key is stored on that device and never synced, and none of it reaches us. With the feature off, the audit runs in your browser apart from the crawler file requests to your own origin.

Yes. Every tool runs in the Firefox build, and the same license covers it. Chrome, Edge, Brave and other Chromium browsers are supported too.

It comes with Hoverify, a paid extension with a 14-day refund behind it. Audit a few of your own pages and you'll know whether it stays, and you can get your money back if it doesn't. That stands in for a trial. One license runs in 3 browsers at a time, and nothing auto-renews. See the pricing.