Alesta separates what a source directly reported from what the system calculated or inferred. It also separates missing evidence from a real measured zero.
Evidence states
Availability states
Unavailable is not zero
This is the most important reading rule in the product.
If Google does not have enough eligible Chrome UX samples, Alesta cannot report real-visitor Core Web Vitals for that domain. That does not mean the site had zero visitors or perfect vitals.
If a backlink provider returns no usable record, the panel can be unavailable. That does not prove the site has zero backlinks.
If an AI-visibility run did not execute, Alesta must not display zero mentions. It should say not measured or unavailable.
Never copy an unavailable value into a report as 0. Preserve the state and
the source limitation.
Lab data and field data
PageSpeed scores come from Lighthouse lab runs. Core Web Vitals in Alesta are real-visitor field data when eligible data exists. The two can disagree because they answer different questions.
- Use lab data to reproduce and diagnose a controlled page load.
- Use field data to understand eligible real-user experience over the provider’s reporting window.
- Do not substitute lab values when the field-data panel is unavailable.
Plan state and data state are separate
An upgrade can unlock a run or panel, but it cannot guarantee that a provider has data for a particular domain. Read the sequence this way:
- Access: Does the plan include the capability?
- Readiness: Is the required connection, selection, or service available?
- Data: Did the source return usable evidence?
- Quality: Is the result complete, partial, inferred, or otherwise caveated?
References
