How the Found Score is calculated.
Every check, every point, every source — published in full, because an instrument you can’t inspect is an instrument you shouldn’t trust.
What this score is: a findability-hygiene instrument — how readable, credible and quotable your site is to search and AI engines, measured with evidence you can verify.
What it is not: a ranking prediction. Nobody can promise positions — anyone who does is selling you weather control. The score measures what is in your control; rankings follow many factors including ones that aren’t.
Technical
15 ptssensor liveFetches the homepage like a crawler. Checks status, content type, and server-rendered text. Note: Google renders JavaScript (with delay); most AI crawlers do not — thin raw HTML is scored as a warning for exactly that reason, not as a Google problem.
Parses robots.txt with longest-match rules. Distinguishes answer-engine bots (OAI-SearchBot, ChatGPT-User, PerplexityBot, Claude-SearchBot, Bingbot — blocking these removes you from live AI answers, penalised) from training bots (GPTBot, ClaudeBot, CCBot — blocking these is a legitimate licensing choice, noted but never penalised).
Fetches the declared or conventional sitemap, validates the urlset, reads the newest lastmod (treated as a hint, as engines do). Warns past 183 days.
Checks meta robots and X-Robots-Tag headers for accidental noindex.
Probes www and http variants; expects single-hop redirects to one canonical origin. Unresolvable variants are acceptable.
Entity
15 ptssensor liveParses JSON-LD for Organization/LocalBusiness + WebSite with name, url, logo. Framed as entity clarity (site names, knowledge panels, AI identity-matching) — not as a ranking factor, because it isn’t one.
Detects the brand from schema, checks homepage and sampled page titles carry it.
Discovers the about page via sitemap + link inventory (soft-404s rejected), measures visible text. Engines resolve “who is this business” largely here.
Planned — Places API.
Planned — site vs Places listing.
AI Visibility
20 ptscoming onlinePlanned: monthly prompt runs against ChatGPT and Perplexity APIs using customer-question archetypes; records whether the brand is named or cited, and by whom instead.
Evidence
20 ptssensor liveLLM-judged (Claude, versioned prompt, cached by content hash for consistency): counts sourced statistics, named quotations, citations; flags keyword stuffing. The point mapping from counts is deterministic code, not model whim. Basis: Aggarwal et al., “GEO: Generative Engine Optimization”, KDD 2024 — sourced statistics, quotations and citations raised generative-engine visibility 30–40%.
Word counts across sampled pages plus 5-word-shingle similarity to catch near-duplicate template pages. Framed as substance and duplication risk — not “word count is a ranking factor”, which it isn’t.
Structure
15 ptssensor liveLLM-judged: definitions, procedures, comparisons, lists/tables, modular headings — five subscores of 2. Explicitly not “has an FAQ block”. Google states no special formatting is needed for its AI features; this check targets the other engines, which demonstrably lift structured passages.
One clear h1 (multiple h1s are valid HTML5 and fine for Google — docked one point only for outline ambiguity, never called an error), no skipped levels, descriptive text.
Off-site
15 ptscoming onlinePlanned — referring-domain summary.
Planned — Reddit/UGC/directory mentions. Brands are cited via third-party sources far more than via their own domains.
Sources
- Google Search Central — JavaScript rendering, robots.txt, sitemaps, titles, structured data, AI-features guidance — developers.google.com/search
- Aggarwal et al., “GEO: Generative Engine Optimization”, KDD 2024 — arxiv.org/abs/2311.09735
- OpenAI crawler documentation (GPTBot, OAI-SearchBot, ChatGPT-User) — platform.openai.com/docs/bots
- Anthropic crawler documentation (ClaudeBot, Claude-User, Claude-SearchBot) — support.anthropic.com
- Perplexity crawler documentation (PerplexityBot, Perplexity-User) — docs.perplexity.ai
LLM-judged checks use a versioned rubric with deterministic point mapping; identical content always receives the identical judgment (content-hash cached). Rubric version changes re-judge history — scores never wobble for no reason. Found a check you disagree with? Tell us — the rubric improves in public.