Score History & Trends

Every scan Cassian™ runs creates a permanent, numbered record of your store's health at that moment. Scan #1 is your baseline. Every scan after that tells the story of how your store is changing.

The score trend on your dashboard

The main dashboard shows a sparkline graph of your recent Cassian Score™ history. This gives you an at-a-glance view of trajectory: is your store getting healthier over time, holding steady, or gradually declining?

The sparkline shows your most recent scans. For the full history, go to the Scans page in the sidebar.

The Scans page

The Scans page lists every scan that has run on your store, in reverse chronological order. Each entry shows:

• Screenshot — A thumbnail of your store captured during the scan.
• Site and scan number — The site name with a sequential identifier (#1, #2, #3...). Numbers are assigned in the order scans start; a scan that fails still consumes its number.
• Score — The Cassian Score at the time of that scan.
• Pages — How many pages Cassian AI™ visited during that scan.
• Status — Whether the scan completed, failed, or is still running.
• Date — When the scan ran.

Viewing a specific scan

Click any scan in the list to open its full detail view. You'll see:

• Your score for that scan, with the contribution from each active layer
• Every issue found during that scan, with severity, category, and affected page
• A category switcher to filter issues by scoring layer
• The ability to dismiss individual issues directly from the scan detail view
• Scan metadata, including whether the scan ran with all AI checks or in a degraded state

This is how you compare two scans: open the detail view for each and compare the issue lists. Look at what appeared between them (new issues) and what disappeared (resolved issues).

What causes score changes between scans

Score goes down:

• New issues found on pages Cassian crawls for the first time
• Existing pages updated with content that introduces new problems (thin descriptions, broken links, etc.)
• Previously minor issues becoming more severe as they proliferate
• More pages crawled in a scan than previous scans, surfacing issues that were always there but not yet reached

Score goes up:

• Issues resolved — either by you fixing them or by underlying content changing
• Pages previously with errors updated or removed
• New pages crawled that have no issues, improving the overall picture
• Cassian occasionally refines its analysis — a check that was stricter in a previous version may produce fewer findings in a later one

Score stays flat:

• The same issues persist between scans
• New issues emerged at roughly the same rate as old ones were resolved

Understanding scan numbers

Scan numbers are assigned sequentially per site, starting at #1, in the order scans start. They are permanent — scan #12 will always be scan #12, regardless of what happens in subsequent scans. A scan that fails keeps its number, so you may see gaps in the scores between consecutive numbers. Scans cannot be deleted or renumbered.

The scan number is useful when communicating with your team: "The issue appeared in scan #7" is unambiguous.

How long is scan history retained?

Scan records are retained — your scan history stays accessible on the Scans page.

Screenshots: Scan screenshots are retained according to your plan's retention window.

Issue history: Individual issues are stored while they remain open. Once an issue is resolved (no longer found in subsequent scans), it moves to a resolved state. Resolved issues are archived after 180 days. If an issue is resolved and later recurs, it appears again as a new finding with the current date.

Dismissed issues: Issues you manually dismiss are removed from the active count and no longer appear in your lists. They are retained in the database and can be reviewed in the archived issues view.

Exporting scan data

Exports live on the scan detail page — open any scan and use the export options there:

• CSV export — Available on all plans. Includes every issue found in that scan with severity, category, and affected page URLs.
• PDF report — Available on paid plans. A formatted report with your score breakdown and findings.

For Agency plan users, scan data for all client sites can be accessed via the Agency Dashboard and exported per-site.

---

Common questions

How far back does my history go? Scan records don't expire on a schedule — your history stays on the Scans page. Resolved issues within those scans are archived after 180 days, but the scan record and score remain.

Can I see which specific issues appeared between two scans? Yes — open the detail view for each scan and compare the issue lists. Issues that appear in the later scan but not the earlier one are new; issues that disappear were resolved between the two.

Why did my score improve even though I didn't make any changes? A few explanations: a team member may have updated content on your store, Cassian AI may have refined its analysis between releases (less common), or a previously failing resource (like a product image URL) may have started resolving again. The Issues page will show whether previously flagged issues are now absent.

I ran two scans back-to-back and got slightly different scores. Why? Scans reflect the live state of your store at the moment they run. If any content, product data, or linked resources changed between the two scans — even something as minor as a product going out of stock — the results may differ slightly. This is expected behaviour.

Can I trigger a scan at any time, or do I have to wait for the schedule? On paid plans, you can trigger a manual scan from the Sites page (your site → Scan Now), limited to one per minute per site. The free Inspector plan runs scheduled scans only. Scheduled scans run automatically on top of any manual ones.

What does "degraded scan" mean in the scan detail? On rare occasions, when Cassian AI experiences issues reaching its analysis providers, a scan may complete in a degraded state. This means some AI-powered checks ran with reduced coverage — and since every layer includes AI analysis, any category can be affected, including Technical Health. Degraded categories are excluded from that scan's score rather than scored on partial data, and the scan is marked with a warning indicator. A fresh scan will run at full coverage.