> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alesta.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How to interpret Alesta SEO analysis results

> Interpret Alesta PageSpeed, Core Web Vitals, SEO health, crawl, issue, ranked-keyword, and keyword-gap panels with the correct source and scope.

Alesta's SEO tab combines controlled page diagnostics, eligible real-user field evidence, on-page signals, and a bounded technical crawl. It does not represent a Google ranking score or a complete index of every site URL.

Open **Analytics > Web > SEO** to review the available panels.

## What the SEO panels show

| Panel            | What it can show                                                                             | How to interpret it                                                        |
| ---------------- | -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| PageSpeed scores | Mobile and desktop Lighthouse scores for Performance, Accessibility, Best practices, and SEO | Lab diagnostics for the tested page and run conditions                     |
| Core web vitals  | Eligible Desktop or Mobile real-visitor field values                                         | Aggregated field evidence for the displayed scope, when enough data exists |
| SEO health       | On-page metadata and content signals                                                         | A scoped diagnostic, not a ranking guarantee                               |
| Crawl summary    | Facts returned by Alesta's bounded technical crawl                                           | Evidence about the crawled sample, not proof about every URL               |
| Ranked keywords  | Keywords the domain ranks for                                                                | Conditional deeper evidence that is not part of the free baseline          |
| Keyword gap      | Terms where accepted competitors rank and the current site does not                          | Conditional evidence that depends on the confirmed competitor set          |
| Issues           | Open SEO, performance, and GEO findings                                                      | A review queue whose caveats and scope must stay attached                  |

The current free baseline can populate the core public-site panels. Ranked keywords and keyword gaps are not collected by the free flow and may be absent, locked, or otherwise conditional.

## Separate lab and field data

**PageSpeed is lab data.** It runs a page under controlled conditions and helps investigate reproducible diagnostics. Mobile and desktop runs can finish separately and should be reviewed independently.

**Core Web Vitals is field data.** It uses eligible aggregated real-user experience evidence. If the public dataset lacks enough qualifying samples for the selected device and scope, Alesta leaves the result unavailable instead of substituting PageSpeed values.

<Info>
  A working PageSpeed panel beside unavailable Core Web Vitals is a valid
  result. The two panels use different methods and availability rules.
</Info>

## Review SEO evidence step by step

1. Confirm whether the baseline is still running.
2. Compare mobile and desktop PageSpeed rows without averaging them into one score.
3. Check whether Core Web Vitals has eligible Desktop or Mobile field evidence.
4. Read SEO health and crawl summary facts with their page and crawl scope.
5. Inspect each open issue and retain its category, evidence, and caveat.
6. Use ranked-keyword or keyword-gap data only if the panel is present and readable.
7. Confirm the accepted competitor set before using a keyword gap.
8. Record how the team will verify a change after release.

## What the result does not prove

* A high diagnostic score does not guarantee rankings, traffic, or conversions.
* A low score does not identify the root cause by itself.
* No open issue means no open persisted issue in the measured scope, not a perfect website.
* A bounded crawl cannot establish the state of URLs it did not inspect.
* Missing field data does not mean there were no visitors.

If panels stay queued, fail independently, or return no evidence, follow [domain and analysis troubleshooting](/troubleshooting/domain-and-analysis) and [interpret partial and unavailable results](/guides/read-partial-and-unavailable-results).

## References

* [Web analysis overview](/workspace/web-analytics)
* [Review your first baseline](/guides/review-your-baseline)
* [Google PageSpeed Insights: field and lab data](https://developers.google.com/speed/docs/insights/v5/about)
* [Chrome UX Report documentation](https://developer.chrome.com/docs/crux)
* [Google Search Central: Core Web Vitals](https://developers.google.com/search/docs/appearance/core-web-vitals)