Skip to content
AICOT

How does AICOT score a website?

AICOT opens the pages of a site in a real browser, runs a fixed list of checks on them, and turns the failed checks into a score from 0 to 100 for each of seven areas and for the site as a whole. This page describes exactly how.

Scoring version 4 · Last updated

What is measured?

Each audit covers seven areas. The overall score is their weighted average.

AreaWhat it coversWeight
SEOTitles, descriptions, headings, structured data, thin and duplicate content.20%
ContentThe text of up to five pages, reviewed by an AI model for clarity, direct answers, concrete facts and trust signals.15%
TechnicalHTTPS, robots.txt, sitemap, broken links, redirects, indexing rules and security headers.15%
PerformanceLoading speed and Core Web Vitals, measured with Lighthouse on a simulated mobile phone.15%
AI visibilityWhether AI assistants can read and quote the site, and whether they name or cite it when asked customer questions.15%
AccessibilityWCAG 2.2 level AA rules, tested with axe-core.10%
ConversionA call to action on the first screen, a way to get in touch, and forms short enough to finish.10%

How is an area's score calculated?

An area starts at 100 and loses points for each failed check. A check costs more the more severe it is and the larger the share of pages it fails on:

score = 100 × (1 − Σ weight × share of pages failing ÷ Σ weight of all the area's checks)

The weight of a check comes from its severity: critical 10, high 5, medium 2, low 1. A critical problem on every page therefore costs ten times as much as a low one.

Which areas are scored differently?

What happens when an area is not measured?

An area that could not be measured, such as content without AI analysis, is left out, and the remaining weights are scaled up to 100%. An unmeasured area never counts as zero.

Can two audits be compared?

Yes, when they were scored with the same scoring version. Every report states its version. When checks or weights change, the version number goes up, and reports stop comparing scores across versions.

What are the limits of the method?