Understanding Crawl Results
A comprehensive guide to interpreting crawl results, including pages, accessibility, SEO, security, and performance reports.
Understanding Crawl Results
After a crawl completes, AegisRunner provides detailed results for every page discovered, including interactive states, screenshots, accessibility audits, and AI-generated test suites.
Results Overview
The crawl results page shows:
- Pages discovered — total number of unique URLs found
- UI States — total interactive states across all pages (clicks, modals, form states)
- Duration — total crawl time
- Screenshots — one per state, viewable in the page detail
Pages & Page States
Each page can have multiple states. The initial state is the page as it loads. Additional states are discovered by interacting with the page — clicking buttons, opening modals, selecting options, filling forms.
| State Type | Example |
|---|---|
| Initial (navigate) | Page as it loads — forms, links, buttons visible |
| Update | Content changed after clicking a button or selecting an option |
| Modal | A modal or dialog opened after a click |
| Expand | An accordion, tab panel, or details element expanded |
| Form validation | Validation errors appeared after submitting an empty form |
| Navigate | A click navigated to a different page |
Page Detail View
Click any page to see:
- All states with screenshots and trigger actions
- Interactive elements — forms, buttons, links with their selectors
- Accessibility audit — WCAG violations with severity and fix recommendations
- SEO analysis — meta tags, headings, structured data
- Security headers — HSTS, CSP, X-Frame-Options
- Performance metrics — load time, resource counts
- AI-generated test suites — test cases generated for this page
Tabs
| Tab | What it shows |
|---|---|
| Pages | All discovered pages with state counts and screenshots |
| Accessibility | WCAG compliance score, violation breakdown, per-page issues |
| SEO | Meta tag coverage, heading structure, missing alt text |
| Security | Security header analysis across all pages |
| Performance | Load times, resource sizes, performance scores |
Setting a Baseline
After reviewing crawl results, you can set this crawl as your project's baseline:
- Click Set as Baseline on the crawl results page
- A regression manifest is compiled from this crawl's pages and interactions
- Future crawls can be compared against this baseline
- The Regression crawl mode becomes available for deterministic replay
Comparing with Baseline
Click Compare with Baseline on any crawl to see what changed:
- Missing pages — pages in baseline but not in this crawl (potential regressions)
- Changed pages — pages with different state counts or interactions
- New pages — pages in this crawl but not in baseline
- Unchanged pages — pages matching baseline exactly
AI Test Generation
After crawling completes, AI automatically generates test suites for each page. View them in the Test Suites section or from the page detail view. See AI Test Generation for details.
Related Documentation
- Starting a New Crawl — Crawl modes and settings
- Regression Manifests — Deterministic replay testing
- Test Baseline Review — Review AI-generated tests
- Accessibility Testing — WCAG compliance details