The Scan results page is the main evidence hub for a single Siteimp scan. It brings together the scan’s system progress, scan-wide signals, links into deeper scan sections, and the table of pages discovered during the run.
This page can be useful while a scan is still running and after it completes. During a live scan, the system area updates as work progresses. After completion, the same page becomes the stable summary for that scan, including final counts, signals, page issues, and Lighthouse scores.
Think of this page as the scan’s table of contents and control room. It does not show every detail directly. Instead, it tells you what happened, what looks worth attention, and where to go next.
What this page is for
The Scan results page exists to answer a few practical questions:
- Is the scan still running, complete, failed, or stopped?
- How many pages, links, audits, media assets, and derived records were produced?
- Are there any scan-wide signals that need review?
- Which deeper scan sections should I inspect next?
- Which pages have page-level issues?
- Which pages have Lighthouse data?
This is the first page to review after starting a scan. It gives you the broad picture before you move into images, links, signals, or individual page details.
System
The System section shows the scan heartbeat. This is Siteimp’s progress model for the scan runtime.
When the scan is running, the circular bands can rotate or fill as work moves through different phases. The bands represent the main scan work streams, including mapping, Lighthouse audits, HTML derivation, Lighthouse derivation, and external link checks.
When the scan completes, the system section switches into a final summary. It can show final counts for work completed and timing information such as total scan time and politeness wait.
Why the scan may take time to start
The first scan for a site can take a few minutes to visibly begin. Siteimp may need to start the scan runtime, launch the browser environment, prepare workers, and wait for the first discovered pages before the page table begins to fill.
This startup delay is not ideal, and improving it is a priority. The hard part is doing that without becoming rude to websites, hiding real work behind fake progress, or creating a scan model that is faster but less trustworthy.
If the heartbeat says the system is preparing the scan, give it a little time. Once pages are discovered, the rest of the page should begin to populate.
Understanding the heartbeat
The heartbeat can show different states depending on the scan status.
Preparing
When a scan is queued or running but no pages have appeared yet, Siteimp may show that the system is preparing your scan. This usually means the runtime, browser environment, and workers are getting ready.
Running
Once discovery has started, the heartbeat shifts to live progress. Page and link counts may grow while the scan continues. Progress rows can also show audits, derivation, external checks, and media processing.
Completed
When the scan is complete, the heartbeat shows final counts. The scan is no longer changing, so the rest of the page can be treated as a stable snapshot.
Failed or stopped
If the scan failed or was stopped, partial results may still appear. Those results can still be useful, especially if pages were discovered before the stop. Review the visible signals and pages before deciding whether to rerun.
Signals
The Signals section shows scan-wide findings. A signal is about the scan or website as a whole, not just one page.
Examples include:
- broken external links
- broken internal links
- broken images
- pages found only in the sitemap
- pages found only in the crawl
- external link concentration
Signals are meant to help you notice structural patterns quickly. A signal does not always mean something is broken. Sometimes it means “this deserves a look.”
For example, a page found in sitemap only may be a page the sitemap lists but the crawler did not discover through normal internal links. A page found in crawl only may be discoverable through links but missing from the sitemap.
Signals and issues
Siteimp uses signals and issues differently.
A signal is scan-wide or website-wide. It tells you something about the scan as a whole.
An issue is page-wide. It tells you something about a specific page.
The issue pills in the pages table are page-level applications of the same evidence system. For example, the scan may have a broken image signal, while an individual page row may show an image issue pill because that page uses one or more affected images.
This distinction matters because it helps you decide where to investigate:
- Use signals when you want the broad pattern.
- Use page issue pills when you want to inspect one affected page.
Explore this scan
The Explore this scan section links to deeper scan-level pages.
Images
The Images card opens the scan images page. Use it to inspect images, metadata, and usage across the scan.
This is helpful when you want to understand which image assets were discovered, where they are used, and whether any image-related issues are present.
Links
The Links card opens the scan links page. Use it to inspect link counts and page-level structural flow across the scan.
This is helpful when you want to understand internal links, external links, broken link patterns, or how pages connect to each other.
Pages table
The Pages table lists the pages discovered in this scan. Each row represents one page record from the scan snapshot.
The table can show:
- URL
- page title
- page-level issue pills
- Lighthouse performance score
- Lighthouse accessibility score
- Lighthouse best practices score
- Lighthouse SEO score
- HTTP status or page fetch status
Rows are clickable. Opening a page row takes you into that page’s detail view, where you can inspect deeper page-level evidence.
URL display
For pages on the same site, Siteimp may shorten URLs so the table stays readable. The homepage may show as the full origin, while deeper paths may show with a shortened prefix such as ../about/.
This is only a display choice. The underlying page record still belongs to the scan snapshot.
Lighthouse scores
The table uses four Lighthouse columns:
- P for Performance
- A for Accessibility
- BP for Best Practices
- SEO for SEO
Scores may appear as numbers when Lighthouse data is available. If a score is missing, the table can show a blank or placeholder value.
These scores are useful for orientation, but they are not the whole story. Use the page detail and page metrics views when you need deeper evidence.
Page status
The status column shows the page’s HTTP or fetch status. A normal successful page commonly shows a 2xx status such as 200.
A page may show other labels if it was blocked by robots, failed during fetch, or did not produce a normal status code.
Issue pills in the pages table
Issue pills summarize page-level findings. They are intentionally compact because the table is meant to stay scannable.
A pill such as 2 images means Siteimp found image-related issues for that page. A pill such as Sitemap means that page has sitemap-related page evidence.
Clicking an issue pill opens the matching page issue detail, instead of opening the general page detail row. This lets you go directly to the evidence behind that issue.
Loading scan status
If the page says Loading scan status, Siteimp is reading the scan dashboard from the local database.
This can happen briefly when opening the page, switching scans, or refreshing after a live scan changes state.
If the message stays visible longer than expected, wait a moment and try returning to the website dashboard, then open the scan again.
Pages will appear as they are discovered
During a live scan, the pages table may be empty at first. This does not automatically mean the scan is stuck.
The scan may still be preparing the runtime, launching the browser environment, or waiting for the first pages to be discovered. Once discovery begins, pages should appear in the table and update as more evidence arrives.
How to use this page
A good review flow is:
- Start with the System section to understand whether the scan is running, complete, failed, or stopped.
- Review Signals to see scan-wide findings.
- Use Explore this scan to open images or links when those areas need deeper inspection.
- Review the Pages table for page-level issues and Lighthouse scores.
- Open individual pages or issue pills when you need page-specific evidence.
- Return to the website dashboard when you want to start another scan or compare scan history.
Where to go next
The most common next steps from this page are:
- Images, if the scan shows image issues or you want to inspect image usage
- Links, if you want to inspect link structure or broken link patterns
- Signal detail, if a scan-wide signal needs deeper review
- Page detail, if a specific page has interesting scores or issue pills
- Website dashboard, if you want to run another scan or review scan history
The Scan results page is where the evidence first comes together. The deeper pages are where you inspect the evidence one slice at a time.