Classic search
Indexation, canonicals, structure, internal link graph, technical errors.
2026 search standards
Enter a domain. Get SEO, AEO, GEO and Performance scores from 0–100 with the exact issues behind them and how to fix each one.
Scoring model
Each score comes from its own group of checks and its own ranked fix list. A score is shown only where the data can be established reliably.
Indexation, canonicals, structure, internal link graph, technical errors.
Whether content fits answer blocks: answer-first structure, questions in headings, schema, clear facts.
Whether AI crawlers can reach the content: robots.txt rules, snippet directives, entity clarity, llms.txt.
Core Web Vitals from PageSpeed Insights and CrUX: LCP, INP, CLS on mobile and desktop.
What we check
From robots.txt to whether an AI crawler can read your content at all. Every check carries score weight and a concrete fix.
HTTP statuses, noindex, canonical errors, redirect chains, hreflang mismatches.
GPTBot, OAI-SearchBot, Claude-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and CCBot access in robots.txt.
Present, missing or invalid. Informational only: Google does not use it, so it never lowers the score.
LCP, INP, CLS field data, mobile and desktop separately. Google's data, not our estimate.
Whether a question in an H2/H3 is followed by a direct answer, list or table.
nosnippet, max-snippet, data-nosnippet — whether you block your own snippets.
Organization, Product, Article, FAQPage syntax and coverage validation.
Title, meta description, H1 structure, duplicates, image alt, semantic HTML.
How it works
A scan takes minutes because we really crawl the site URL by URL. The report is a backlog, not a PDF.
No signup. We read robots.txt, sitemap.xml and the internal link graph within the configured crawl budget.
HTTP statuses, canonicals, indexability, headings, links, schema and hreflang. Key pages also go through PageSpeed Insights.
SEO, AEO, GEO, Performance, each explaining what took points off. Anything we cannot establish reliably is shown as “Unable to verify”, never as an error.
Issues ranked by impact, each with the affected URLs and a fix step. Share the link with a client or a developer.
How we work
Next to the score you always see which check took it, how many URLs are affected and what to do.
If something cannot be established reliably we show “Unable to verify” instead of an invented number.
Technical checks are unambiguous. Content quality is a signal, so we never present it as a precise score.
The first scan is free and needs no account. The report stays available at its link.