How we estimate the impact of fixes
Every "+X% SEO / +Y% AI" figure in a report comes from the model described here. It is an estimate under a published method, not a measurement of your site.
Impact model v1.0.0
This is a model, not a measurement
We have not measured what your traffic would do. We distribute a fixed, published budget of potential across the criteria that apply to your site, and weight each by how broken it currently is. Two sites with the same failures get the same numbers. Nothing here is a promise about outcomes.
Two channels, two budgets
A budget is the total upside the model will ever attribute to one channel, for a maximally broken site. Fixing everything cannot yield more than this, because the model never distributes more than it has.
The AI budget is roughly three times the SEO one. That is a modelling assumption, not a finding: AI-sourced traffic starts from a low base and is growing, so adapting for it yields a larger relative gain than further tuning of a mature search channel. These are calibration constants — revising them means issuing a new model version.
How the budget splits across categories
Each channel budget is divided between the 12 audit categories by fixed shares. Each column adds up to 100%.
| Category | Search traffic | AI referrals |
|---|---|---|
| AI Access & Crawlability | 20% | 13% |
| Entity Clarity | 9% | 11% |
| Service Structure | 11% | 9% |
| Proof Layer | 6% | 8% |
| Trust Signals | 9% | 6% |
| Schema.org / JSON-LD | 15% | 13% |
| AI Summary Readiness | 5% | 11% |
| FAQ Quality | 8% | 10% |
| Answer Readiness | 7% | 11% |
| External Consistency | 7% | 5% |
| Prompt Visibility | 1% | 2% |
| Conversion Trust | 2% | 1% |
| Total | 100% | 100% |
The formula
Within a category, a criterion takes a portion proportional to its weight in our methodology — the same weight that drives the score. We do not keep a second set of weights for impact, because two weightings would eventually disagree.
liveShare(K, ch) = SHARE(K, ch) / Σ SHARE(K', ch) potential(c, ch) = BUDGET(ch) × liveShare(K, ch) × Weight(c) / Σ Weight(K) impact(c, ch) = potential(c, ch) × statusFactor(c)
The normalizer matters when a whole category does not apply to your site. Its share is redistributed across the categories that do, so the budget stays the ceiling for a maximally broken site of your kind — rather than making some kinds of site structurally capable of less.
How the current verdict scales it
- Failed — the full potential is still on the table.
- Partial — half of it.
- Passed — nothing left to gain here.
- No verdict at all (not applicable, or the engine could not tell) — zero. No verdict, no promise.
Only what applies to you
The methodology comprises 132 checks.
Only a subset applies to any given site, chosen by its type. The rest are skipped: they take no share of the score and do not affect the final result. A personal site is never offered percentage points for product markup it has no reason to have.
What the model does not do
It does not account for your industry, your competition, or your current traffic. It is not calibrated against measured outcomes — doing that would require traffic telemetry we do not collect. Treat the figures as a way to rank fixes against each other, not as a forecast.
Estimate under the AIRA v1 methodology. Not a guarantee of results.