Scans & results

Scans run the checks for the configured URLs. Results show findings per URL, status, filters, exports and comparison views - including key metrics and bulk actions for team workflows.

Note: in addition to the spell check described here, there is a second scan type: the content assessment, which detects test content, placeholders and unreachable URLs.

Start a scan

• When a scan starts, tokens are reserved up front matching the planned scope.
• Without sufficient balance the start can be blocked or limited depending on the rules.

Progress during the run

• A progress bar shows the current state (e.g. processed URLs vs. total).
• Runtime and token consumption are shown so you can follow the run.

Results per URL

• Every URL has a result list with individual findings and context (text passage, suggestion, rule).
• Confidence score - a metric for how certain the system is about a finding (interpretation depends on rule and model).

Findings diff

• The findings diff view visualises changes between states:
  • Red - removed or marked as legacy content to be corrected.
  • Green - corrected or marked as the new, preferred state.

Categories and filters

• Typical categories include spelling, grammar, typos and punctuation (exact set depends on the product).
• Filters narrow the list down to relevant types, severities or statuses so you can work more efficiently.

The filter summary next to the filter button shows "{filtered count} of {total count}" so you always know how many findings exist overall and how many the current filter shows.

Finding statuses

• Open - still to process or check.
• Done - processed or accepted as completed.
• Ignored - deliberately not pursued (e.g. intentional spelling).

KPI cards in the scan detail

The four KPI cards at the top give you an immediate overview of the scan status:

• URL progress - shows the state as "{processed} / {planned}" with a percentage. A green bar shows checked URLs, an optional blue portion marks skipped URLs (unchanged according to the sitemap since the last scan).
• Findings - total number of findings broken down: open (amber), done (green), ignored (grey). With zero findings "Error-free" appears in green.
• Reserved - tokens reserved up front as a buffer before the scan starts. Any unused surplus is refunded after completion.
• Consumed - tokens actually consumed, with ratio relative to the reserved tokens.

Ignoring findings and the ignore list

When you ignore a finding a dialog opens with multiple options:

• Ignore only this finding - marks just the selected finding as ignored.
• Ignore all identical findings - if several findings share the same pattern, you can ignore them all at once. The count is shown in the dialog.
• Add permanently to the ignore list - this option (only for Owners and Admins) adds the pattern to the project-wide ignore list. On future scans this pattern is automatically treated as ignored.
• Reason - you can optionally state why the finding is ignored (max. 140 characters).

See Ignore list for more about the ignore list.

Export and bulk actions

• CSV - tabular export for Excel, data pipelines or ticketing systems.
• PDF - readable report for sign-off or documentation.
• Bulk actions - set or edit several findings at once (depending on role).

Cancel a scan and refunds

• Runs can be cancelled if you notice an error or need to reduce load.
• For unused or refundable portions a token refund can be issued (see the current product rules).

Auto top-up when starting a scan

If your token balance isn't sufficient for a scan and you have automatic top-up configured, a confirmation dialog appears:

• Package and cost - shows the configured auto top-up package with token amount and price.
• Confirm - "Top up & start scan" automatically buys the package and starts the scan.
• Cancel - the scan is not started, no costs are incurred.

The invoice is sent automatically by email. See Billing & Tokens for more on the configuration.

Tips

• Combine filters and status so backlogs don't grow uncontrollably.
• For striking confidence values, check the source in the finding before changing content in bulk.