Scans and pipelines

The console does not crawl your site in the browser. Pipelines — scheduled or on-demand data jobs — ingest results into your workspace. Pages query that data through the console API.

Core pipelines (onboarding)

When you submit your domain during onboarding, these pipelines start automatically:

Pipeline	Feeds
SEO crawl	SEO Report, Unified Report
Site quality	Site Quality (Playwright lab)
Content quality	Content Quality SEO + AIO
Google SERP ranks	Google SERP Ranks, rank tracking in Keyword Research

Re-run all scans on any scorecard page retriggers these four pipelines for your primary domain.

Optional pipelines

Optional scans start from their feature page:

Feature	Trigger
Backlinks	Run backlinks scan on Backlinks page
AI Citations	Run AI citations scan on AI Citations page
Keyword Research hub	Run research inside a project
Tech stack	Run tech scan on Tech stack page

Optional pipelines do not run during onboarding unless you start them later.

Competitor fan-out

When you add competitor domains to your workspace, benchmark pipelines run once per tracked domain for SERP and backlink comparisons. Your primary domain remains the workspace anchor.

Data flow

You submit domain or click Run
        ↓
Pipeline sync ingests external + crawl data
        ↓
Results stored in tenant datalake
        ↓
Console page queries latest run (Refresh data)
        ↓
Scorecard + tables render checks and rows

Keyword research adds an extra processing step after live SERP capture — clusters and vector similar keywords appear only after that step completes. See Run research.

Progress visibility

Pipeline progress streams to the console over WebSocket:

Onboarding scan page
Active scans panel in the sidebar area
Scan status banner when jobs are in flight