Skip to content

Scorecards explained

Scorecards are the primary way the console surfaces actionable findings. Every pillar page and the Unified Report organize automated checks into sections with traffic-light status.

StatusMeaning
PassCheck meets the configured threshold
WarnBorderline or advisory — worth reviewing
FailDoes not meet threshold — likely hurts visibility or quality
ErrorCheck could not run (missing data, API failure, etc.)

Hover or focus a check row to see a tooltip with the check title, description, and hints for what pass vs fail usually means.

Each scorecard belongs to a pillar — a data domain with its own pipeline and checks:

PillarConsole pages
SEO crawlSEO Report, Unified Report
Site quality labSite Quality
Content quality (SEO)Content Quality — SEO
Content quality (AIO)Content Quality — AIO
Google SERP ranksGoogle SERP Ranks
Backlink intelligenceBacklinks
Keyword researchKeyword Research (metrics, not rank tracking)
AI citationsAI Citations

The Unified Report rolls up representative checks from each pillar into one view.

Within a scorecard, checks group into sections such as Metadata, Web Vitals, Visibility, or Ingestion. Section headers include a short hint explaining what the group measures.

Scorecard pages show run history — past pipeline executions with timestamps. Select a run to view checks as they were at that point in time (where the UI supports historical runs).

Scorecards read from ingested pipeline data. Refresh data updates the view from the latest run; it does not re-run checks. To produce new check results, trigger a scan (core re-run, optional pipeline, or keyword research run).

Every check is documented in Scorecard checks — auto-generated from the same catalog that powers UI tooltips.