What the score is—and is not
The overall score is the average of five category scores. Each category is calculated from point-weighted checks in the documented scan. A higher score means more of the measured website signals were observed at the scan time. It does not predict traffic, rankings, revenue, inclusion in any AI answer, or the accuracy of external listings.
Every paid report retains a category ledger with the rule label, points awarded, maximum available points, observed evidence, source URL, and capture time. Checks that could not be run are marked unavailable rather than silently treated as a failed check.
Readiness grade
Each report pairs the numeric score with a plain-language grade to make the starting point easier to understand: A (85–100, Strong foundation), B (70–84, Established foundation), C (50–69, Developing foundation), D (30–49, Needs attention), and F (0–29, Priority foundation work). The grade summarizes only the documented website signals in that assessment; it is not a prediction of rankings, revenue, or AI-provider visibility.
The five score categories
| Category | Website signals checked |
|---|---|
| Schema Markup | Machine-readable entity and page information, including detected JSON-LD, entity, FAQ, Service, BreadcrumbList, review, WebSite, and sameAs signals. |
| AI-Optimized Content | Visible page depth, question-led headings, answer structure, explanatory language, lists, authorship patterns, and About or team context. |
| E-E-A-T Signals | Website-visible contact, address, profile-link, review-language, credential, experience, About-link, policy, and media or press signals. |
| Citation Readiness | Website-side identity, map and profile links, referenceable local details, and proof signals. This is not an external directory or provider-verification score. |
| Technical Structure | HTTPS, page title, description, canonical, Open Graph, viewport, robots.txt, sitemap.xml, and mobile PageSpeed when the check is available. Initial HTML response time is retained as scan context, not a score-changing one-time measurement. |
What the current scan includes
Documented website checks
The AIR-1.2 baseline fetches the submitted public website page, then checks the site’s robots.txt and sitemap.xml endpoints. When configured and available, it records Google PageSpeed mobile performance as supplemental context; PageSpeed availability does not change the core AIR score. The individual report lists every completed, unavailable, or not-configured check.
Evidence, not assumptions
The engine records observed page patterns such as detected JSON-LD, question headings, metadata, contact signals, and website links. Recommendations are generated from the specific rule that did not receive full credit, rather than invented competitor counts or unverified citation claims.
Citation Readiness: the important boundary
Citation Readiness in the $29 report is deliberately limited to website-based signals. It can identify whether the submitted site contains a declared entity reference, a map or profile link, visible local identity details, and selected proof signals. It cannot establish whether a third-party directory listing exists, whether its information is accurate, whether a linked social profile is active, or whether an AI provider has cited the business.
Third-party directory crawling, live AI-provider prompt checks, external citation verification, competitor comparison, and review validation are separate full-service verification activities. They are not represented as completed in AIR-1.2 unless Click Elevate runs and stores that separate module.
Why a re-scan can change a score
A new assessment may produce a different result if the site’s observable content, markup, metadata, redirects, robots.txt, sitemap, or other documented website signals have changed. AIR-1.2 records initial response time and PageSpeed as scan context, not core-score inputs, so a transient response or PageSpeed availability alone does not change the core score. The assessment and methodology versions are stored with every run so results can be interpreted in their original context.
Re-scan guidance
Re-scan after the documented technical or content changes are live and publicly reachable. Compare like-for-like runs only when the same methodology version and scan scope apply.
Assessment version history
AIR-1.0 scored a one-time initial response measurement. AIR-1.1 retained that timing as scan context instead. AIR-1.2 additionally treats Google PageSpeed as supplemental context, so temporary PageSpeed availability does not change the core readiness score. Historic reports keep their original version labels; do not compare different versions as though they used the same rule set.
How to use the paid report
Start with the highest-priority evidence-backed findings, then use the roadmap to assign ownership across the first 14, 45, and 90 days. If your objective requires verified listings or actual AI-provider answer testing, request implementation help so that work can be scoped separately from the website-only baseline.
Get an AI Search Readiness assessment