Loading…
Skip to main content

Reading your report

The dashboard combines overview cards, a site picker, run history, top issues, ignore rules, and CI context. This guide walks through how those pieces fit together after your first run.

On this page

Site picker and multi-site monitors

Each monitored sitemap is a site in your account. Runs for the same sitemap URL are grouped under one site key so history, trends, and baselines stay together.

  • When you monitor one sitemap, the page header shows that site's label (derived from the sitemap host) and when the last run started.
  • When you monitor two or more sitemaps, a Site dropdown appears in the header. Pick a site to filter overview cards, top issues, and run history to that monitor only.
  • The dropdown shows each site's display name and how many saved runs it has, for example example.com (12).

Manual runs, schedules, and CI triggers all append to the same site history when they use the same sitemap URL. See Baselines and diffs for how comparisons stay scoped per site.

Overview cards

After at least one run completes for the selected site, three cards summarize status at a glance.

  • Latest run — Status (complete, running, failed, or pending), start time, error/warning/info counts, and a cloud or agent badge for where the crawl ran. Use View report to open the full run below the history list.
  • Trend — A chart of errors and warnings across recent complete runs on this site. You need at least two runs before the chart appears. The latest run card may also show a one-line comparison to the previous run (for example whether errors went up or down).
  • Active — Shows progress while a crawl is running or pending for this site: pages processed, live error/warning counts, and Cancel scan if you need to stop an in-flight job.

Counts on the cards respect your ignore rules—suppressed findings are excluded from the headline numbers you see on the dashboard.

Top issues → drill into the report

Top issues lists the highest-impact finding types from the latest complete run on the selected site, ranked by severity and how many pages are affected.

  1. Click an issue row to select that run and scroll the report to the matching check group.
  2. Use View all in report to open the latest run without jumping to a specific check.

The run report below history includes the deploy diff hero (when a baseline exists), findings grouped by issue or severity, and per-page detail. Each check name links to the SEO checks reference for remediation guidance.

On wide layouts, top issues and run history appear side by side; on smaller screens, history is shown first, then issues. Very large runs may show a coverage banner when per-page detail is stored for a subset of crawled URLs—overview counts still reflect the full crawl.

Run history and deleting data

Run history lists saved runs for the selected site, newest first. Click a row to load that run's report on the same page.

  • Running or pending jobs can be cancelled from the history row menu while they are still active.
  • Delete run removes one completed or failed run permanently. You must confirm before deletion; this cannot be undone.
  • Delete site runs removes all saved runs for the currently selected site. Running jobs block site-wide delete until they finish or are cancelled.

Use Show more when you have more runs than the default page size. The list badge shows how many runs are loaded for the site.

On all plans, runs older than 30 days are removed automatically—see Troubleshooting and run history retention.

CI context bar

Runs triggered from CI (GitHub Actions or the trigger API) are labeled with a CI badge in history and in the report header. When GitHub metadata was supplied at trigger time, a CI context bar appears under the report title with:

  • Repository — owner/repo slug.
  • Commit — Short SHA linking to the commit on GitHub when the repo is known.
  • Ref — Branch or tag name (for example refs/heads/main shown in shortened form).
  • PR # — Pull request number when the run was tied to a PR, with a link to GitHub.
  • Workflow run — Link to the Actions run that started the crawl, when a workflow run ID or URL was provided.

Some CI runs also show a Code changes panel with compare stats and a link to the GitHub compare view when your pipeline sends that metadata.

Wire CI triggers using CI and GitHub Actions and Developers → API keys. CI baselines can differ slightly from manual dashboard baselines—see CI baselines.

Export (authenticated)

When you are signed in and viewing a completed run, use Download HTML report in the report header to save an offline copy of the findings. The file uses the same layout as the CLI HTML report: summary counts, optional comparison to the automatic baseline, and findings grouped by page or by check.

  • Ignore rules — Suppressed findings are omitted from the export, and headline error/warning/info counts match what you see in the dashboard report.
  • Deploy diff — The comparison block in the HTML export follows the automatic baseline (same as the deploy diff card) and does not apply ignore rules.
  • Stored pages — Very large runs may store per-page detail for a subset of URLs (default cap: 25 pages; errors kept first). The export includes the same stored pages as the on-screen report, not every crawled URL. See Troubleshooting — report page coverage.

CSV and JSON export are not available in the dashboard yet; use the API or CLI if you need machine-readable output.

Ignore rules

Use Ignore on a finding in the report to hide that check (for one URL or all pages) from dashboard counts and listings. Active rules appear under ignore rule(s) in the findings header; remove a rule there when you want the issue to surface again.

See the full Ignore rules guide for scope, the suppressed badge, undo, and how ignores affect top issues versus deploy diffs.

Advanced crawl options

The dashboard shows the sitemap URL above the overview; expand Advanced options for concurrency, timeout, execution mode, and agent pool before clicking Run scan now. The same fields are available on Schedules for recurring runs.

Field What it does
Sitemap URL Which sitemap to crawl. Changing it starts or continues history under a different site key.
Max concurrency How many pages are fetched in parallel (1–20). Higher values finish faster but put more load on your server.
Timeout (seconds) Per-page HTTP timeout (5–120 seconds). Increase for slow origins or heavy pages.
Execution target Signal Diff cloud runs the crawl on Signal Diff infrastructure (public internet targets). Customer agent routes the job to your enrolled agent for internal, staging, or VPN-only sites.
Agent pool (optional) Shown when execution target is Customer agent. Leave empty for your default pool, or set an ID (for example production) when you operate multiple pools. See Customer agent setup.

Completed runs show Execution route in the report header (cloud vs agent and pool). History rows use a small Cloud or Agent badge with the full route on hover.

Next steps