The GEO Score is computed by running a series of checks against a live website URL. Each check maps to a signal that AI search systems use when deciding whether to crawl, index, and cite a page. The total score is derived from eight scoring categories, capped at 100. The first six categories contribute up to 100 points; the two AI-specific categories (Google AI Mode Readiness and Agent Readiness) each add up to 10 bonus points, with the total always capped at 100.
Data sources
Each scan draws from three sources:
- Live HTTP requests — fetches
robots.txt, sitemap, and the page<head>directly - Google PageSpeed Insights API — provides Core Web Vitals (LCP, CLS, FCP, TTFB) and Lighthouse scores
- HTML parsing — extracts JSON-LD, Open Graph tags, and security headers from the response
Scoring model
Points are awarded per category. Within each category, individual checks contribute a fixed number of points — there is no partial scoring on binary checks (e.g. HTTPS is either present or not). Continuous metrics like Core Web Vitals are scored on a sliding scale based on Google's thresholds.
The maximum raw score is 100 points. The GEO Score displayed is the raw score rounded to the nearest integer.
Rate limits and caching
- Per-IP limit: 20 scans per IP address per 24 hours
- Domain cache: scan results are cached for 24 hours per domain to avoid redundant PageSpeed API calls
- PageSpeed API global cap: Indexora enforces a 20,000 PageSpeed requests per day cap globally
GEO Monitor subscriptions run scheduled scans outside of the per-IP limit and use a dedicated queue.
Known limitations
- JavaScript-rendered content is not evaluated — only the initial HTML response is parsed
- Password-protected or IP-restricted pages cannot be scanned
- PageSpeed scores can vary by ~3–5 points between scans due to server variance
- The GEO Score reflects technical discoverability, not content quality or domain authority
For the full category breakdown, see The 8 Categories.