Skip to content

Free dual-axis discoverability audit for any URL

Paste any URL. Get scored on Core Web Vitals performance AND LLM-citation-readiness in one 5-minute scan. Free until November 2026 — no signup, no credit card, no rate limit.

Free · no signup · ~5 minutes · returns Core Web Vitals + 10 GEO dimensions + prioritized fixes. Audit works on any public URL — homepage, product page, article, doc page, anywhere.

Axis 1 measures Core Web Vitals performance from real Chrome user data

Every audit pulls real-user 28-day p75 measurements from Google's Chrome UX Report (CrUX) — the same dataset Google's search algorithm uses for the page-experience signal. We report LCP, INP, CLS, FCP, and TTFB separately for mobile and desktop form factors, plus a rating (good · needs improvement · poor) on each metric.

Why field data and not Lighthouse?Field data reflects what real users on real devices experience. A site that scores 100 in Lighthouse can still rank poorly if its real-world users encounter slow LCP on flaky mobile networks. CrUX closes that gap — it's the source of truth for page experience.

Axis 2 scores LLM-citation-readiness across ten extractability characteristics

We fetch the URL server-side as a GPTBot or PerplexityBot would — single GET request, no JavaScript execution, generic User-Agent — then parse the static HTML and score 10 dimensions popularized by Aleyda Solis and widely referenced in Generative Engine Optimization literature: Accessible · Useful · Recognizable · Extractable · Consistent · Corroborated · Credible · Differentiated · Fresh · Transactable. Each is scored 0.0 — 1.0; we report per-dimension scores + rationales + top-6 prioritized fixes.

Why this matters in 2026: a meaningful slice of traffic now originates from LLM citations (ChatGPT, Claude, Perplexity, Gemini, Google AI Overview). A site invisible to those crawlers loses that channel entirely — and a poorly-extractable site gets cited less often than a competitor that ships the same data more cleanly.

Both axes scored in one scan with cross-axis prioritization

The single biggest reason VitalsLens exists: most teams audit either one or the other, fix the obvious gap, then ship and assume they're done. Optimizing only Axis 1 leaves half the available 2026 traffic on the table; optimizing only Axis 2 produces extractable slow pages that LLMs cite but humans bounce from.

The audit page ranks the top 6 fixes across both axes by (1 − dimension_score) × dimension_weight — high-severity LCP issues outrank low-severity GEO issues, and vice versa.Read the full methodology →

Examples: stripe.com · github.com · nytimes.com · developer.mozilla.org