Website dashboard

The Website dashboard is the control center for one saved website in your local Siteimp workspace. It brings together the site’s identity, latest scan summary, ownership state, robots.txt preview, crawl settings, recent scan history, and recovery actions for interrupted scans.

This page is intentionally broader than a scan results page. It does not try to show every piece of crawl evidence. Instead, it helps you understand the current state of one website and decide what to do next: run a scan, verify ownership, review crawl expectations, adjust site-specific settings, open a previous scan, filter scan history, or clean up interrupted scan data.

Think of this page as the operational dashboard for a website. The scan results pages are where the deeper evidence lives.

What this page is for

The Website dashboard exists to answer a few practical questions:

• Which website am I looking at?
• What was the most recent scan result?
• Is the website ready for another scan?
• Is ownership verified?
• What does the current robots.txt preview show?
• Which crawl settings will future scans use?
• Which completed scans can I open for review?
• Which older scans used desktop or mobile Lighthouse settings?
• Are there interrupted scans that should be cleaned up or sent to support?

The page keeps those answers together so you do not have to jump straight into a scan before checking the website-level setup.

What you can do here

Review the website identity

At the top of the page, Siteimp shows the website name, start URL, registrable domain, and readiness status.

The Start URL is the address Siteimp uses as the primary entry point for the site. The Domain shows the registrable domain Siteimp associates with the website. The readiness badge gives a quick status such as Ready, Scan running, Scan queued, Needs review, or Stopped.

This top section is meant to confirm that you are working with the correct website before you run a scan or change scan behavior.

Run a scan

The Run a new scan section is the primary action area for this page. It lets you choose which Lighthouse viewport Siteimp should use before starting a scan.

You can currently choose:

• Desktop
• Mobile

For many search and accessibility review workflows, Mobile is often the better default because mobile conditions are a common way to review modern web pages. Desktop is still useful for desktop-specific performance review, large-screen layouts, and comparing mobile and desktop behavior.

After selecting a Lighthouse mode, choose Run scan to begin a fresh scan for this website. When the scan starts successfully, Siteimp opens the matching Scan Results page automatically.

By default, this page starts scans in strict mode. That means Siteimp respects robots.txt unless ownership verification and owner override are configured elsewhere in the website setup.

If Siteimp cannot start the scan, an error appears near the top of the page.

Go back to Websites

The Back button returns to the main Websites page. Use it when you want to switch websites, add another site, or return to the workspace-level overview.

Read the overview cards

The Overview section summarizes the most recent scan.

It can show:

• Latest scan, including the most recent scan status
• Pages, counted from the most recent scan
• Links, counted from the most recent scan
• Average Accessibility, based on the latest Lighthouse Accessibility score summary for all the pages that Siteimp found when it scanned your website.

If the website has not been scanned yet, these cards show that scan history is not available yet. That is normal for a newly added website.

Manage ownership

The Ownership section shows whether Siteimp has verified that you control the website.

Ownership verification can unlock advanced scanning modes for sites you own or control.

The ownership state is checked again and recorded when a scan starts. That means scan history can preserve the ownership state that applied at the time of a specific scan.

Review robots.txt preview

The Robots.txt preview section checks the website’s current robots.txt file and summarizes what Siteimp sees before scanning.

The preview can show:

• whether robots.txt is available
• the matched user agent
• crawl delay
• allow and disallow rule counts
• sitemap locations
• raw robots.txt content when details are open

This preview is helpful for orientation, but it is not the final scan decision. Siteimp checks robots.txt again right before a scan starts.

Adjust crawl settings

The Crawl settings section lets you adjust this website’s crawl behavior without changing global app defaults.

These settings may include:

• crawl delay override
• crawl jitter override
• max concurrency override, when available

The closed summary shows whether the website is using app defaults or a website-specific override. It also shows the effective delay and jitter values that will become part of the scan’s resolved policy.

Review recent scans

The Recent scans section lists recent scan snapshots for this website.

This table is the light scan history review area for the Website dashboard. It is not a full scan-by-scan comparison engine. Instead, it gives you a practical way to review scan history, find completed scans, separate mobile and desktop scans, and spot broad movement over time.

The table shows:

• Scan number
• Lighthouse mode
• scan status
• page count
• link count
• average Lighthouse scores
• creation time
• available actions

Completed scans can be opened from the table. Interrupted scans may show cleanup or support actions instead.

Recent scans table

The Recent scans table is the bridge from website-level setup into scan-level evidence.

Completed scan rows open a Scan Results dashboard for that snapshot. Interrupted scan rows may show recovery actions instead of opening as normal results, because interrupted data is not treated as a completed evidence snapshot.

Siteimp tracks each scan with precise identifiers, including snapshot and operation context, so a scan can be identified during support or debugging.

The Lighthouse columns use short labels:

• P means Performance
• A means Accessibility
• BP means Best Practices
• SEO means SEO

Scores are normalized to whole numbers. A dash means the score is not available for that scan.

Filter by status

Use the Status filter to choose which scans appear in the table.

Available status views may include:

• Completed
• All scans
• Running
• Queued
• Aborted
• Failed
• Interrupted

The default view shows completed scans. This keeps the table focused on scan results that finished cleanly and are most useful for review.

Use All scans when you want to see the full scan history, including scans that were interrupted, aborted, failed, queued, or still running.

Filter by mode

Use the Mode filter to separate Desktop and Mobile scans.

Available mode views are:

• All modes
• Desktop
• Mobile

This is useful because Lighthouse results from Desktop and Mobile scans are collected under different conditions. When you are reviewing scan history, it is usually clearer to compare Desktop scans with Desktop scans and Mobile scans with Mobile scans.

Sort scan history

Several table headings can be sorted. Sortable headings show sort icons in the column header.

You can sort by:

• Mode
• Status
• Pages
• Links
• Performance
• Accessibility
• Best Practices
• SEO
• Created

The default sort is Created, newest first.

Choose a sortable heading once to sort in one direction. Choose it again to reverse the direction.

For example:

• Sort by Created to find newest or oldest scans.
• Sort by Accessibility to find scans with the highest or lowest average accessibility score.
• Sort by Pages to see whether the number of recorded pages changed across completed scans.
• Sort by Mode to group Desktop and Mobile scans together.

Reset the table view

If you change filters or sorting, Siteimp may show a Reset view action.

Use Reset view to return the Recent scans table to the default view:

• Status: Completed
• Mode: All modes
• Sort: Created, newest first

This is useful when filters hide scans you expected to see.

Scan counts

Above the table, Siteimp may show a short count summary such as:

• how many rows are visible
• how many total scans exist
• how many scans completed
• how many scans were interrupted or incomplete

These counts help explain what the current filter is showing.

No scans match this view

If the table says No scans match this view, the website still has scan history, but your current filters are hiding all matching rows.

Try changing the status filter to All scans, changing the mode filter to All modes, or choosing Reset view.

Open a scan

Completed scans show an Open action. Choose Open to inspect the full Scan Results dashboard for that scan.

You can also open a completed scan by selecting the scan label in the first column.

Interrupted scan actions

Interrupted, failed, or aborted scans may show recovery actions instead of the normal Open action.

Available actions may include:

• Delete
• Start new
• Support

Use these actions when a scan did not finish cleanly and should not be treated as a normal completed result.

Interrupted scan data

Sometimes a scan may stop outside Siteimp’s normal control. For example, Windows may sleep, restart, update, or suspend the app while a scan is running.

When that happens, Siteimp may find partial scan data the next time the app starts. This can include queued work, cached page evidence, Lighthouse reports, and other temporary scan artifacts stored locally on your computer.

Siteimp does not automatically resume this data into a completed scan.

That is intentional. A Siteimp scan combines structural evidence with condition-sensitive measurements such as Lighthouse scores, fetch timings, and server responses. If a scan is interrupted and continued much later, the result could mix two different website conditions into one report.

For cleaner evidence, Siteimp treats interrupted scans as recovery cases.

Why interrupted scans are not resumed

A scan should represent one reasonably continuous observation window.

If a website is quiet when the scan starts but under heavy traffic later, the later pages may respond differently. Performance scores may drop, servers may return temporary errors, or pages may behave differently because conditions have changed.

Instead of blending those conditions into one scan, Siteimp gives you explicit choices:

• Delete
• Start new
• Support

This keeps completed scan results more trustworthy and makes interrupted data easier to understand.

Delete interrupted scan data

Use Delete when you do not need the interrupted scan anymore.

This removes the interrupted scan record and its temporary artifacts from your local Siteimp data. Use this when you simply want to clean up and move on.

Deleting interrupted scan data does not delete the website record. It only removes the unfinished scan data for that interrupted scan.

Start new scan

Use Start new when you want fresh results for the same website.

This does not resume the interrupted scan. It starts a clean new scan using the normal scan process. Before starting new scan work, Siteimp makes sure the old scan runtime is no longer active.

This is the best option when you want a clean result for review.

Support

Use Support if you want help understanding what happened.

Siteimp opens the support drawer with scan context attached. The support request can include details such as the website, snapshot ID, scan status, stop reason, artifact counts, and job counts.

Siteimp does not automatically attach the full cached website, Lighthouse report files, or artifact contents. The support flow is designed to send useful diagnostic context without quietly bundling large or sensitive local files.

How to use this page

A good default workflow is:

1. Confirm the website name, start URL, and domain.
2. Check the overview cards to see the latest scan state.
3. Review ownership if you need advanced scanning options.
4. Review the robots.txt preview before starting a scan.
5. Check crawl settings if this website needs special politeness behavior.
6. Run a new scan or open a recent completed scan from the table.
7. Use filters and sorting to review scan history.
8. If interrupted scan data appears, delete it, start a new scan, or send it to support.

For a newly added website, the flow is usually:

1. Confirm the website was saved correctly.
2. Verify ownership if you need owner override.
3. Review robots.txt and crawl settings.
4. Run the first scan.
5. Use Scan Results as the evidence hub.

Overview cards

Latest scan

The Latest scan card reports the status of the most recent scan. It may show statuses such as Completed, Running, Queued, Failed, or Aborted.

If there are no scans yet, the card explains that a scan is needed before the website has history.

Pages

The Pages card shows how many pages were recorded in the most recent scan. This is a scan-level count, not a promise about the total size of the website. The count depends on the crawl scope, robots.txt, scan settings, and what was reachable during that scan.

Links

The Links card shows how many links were recorded in the most recent scan. This helps you understand the size of the link evidence collected for the site.

Average Accessibility

The Average Accessibility card shows the average Lighthouse Accessibility score for the most recent scan when Lighthouse data is available.

This is a useful high-level indicator. It can help you notice whether the pages Siteimp scanned were generally easy for people and assistive technologies to navigate and understand.

Website readiness

The readiness badge near the top of the page gives a quick operational status:

• Ready means the website is available for action.
• Scan running means a scan is currently in progress.
• Scan queued means a scan is waiting to run.
• Needs review means the latest scan failed.
• Stopped means the latest scan was aborted.

Use this badge as a quick orientation signal before starting more work.

Ownership

Ownership verification proves that you control the website. Siteimp uses that state to decide whether advanced scanning options can be made available.

When ownership is not verified, the section shows Not verified and Advanced scanning unavailable. This does not prevent ordinary strict scans. It means owner override is not available yet.

When you open the ownership details, Siteimp can guide you through available verification methods such as Meta Tag and DNS TXT.

Meta Tag

Meta tag verification is usually the fastest option. Siteimp generates a meta tag that you add to your homepage HTML. After the tag is in place, choose Verify now.

The tag must be present in the server-delivered HTML. If it is added later by client-side JavaScript, Siteimp may not be able to verify it.

DNS TXT

DNS TXT verification is a strong long-term option. Siteimp generates a TXT record name and value that you add to your DNS provider. After the record is in place, choose Verify now.

DNS changes can take time to propagate. If verification does not pass right away, wait and try again.

Scan policy after verification

After ownership is verified, Siteimp can let you choose how future scans behave:

• Respect robots.txt keeps scans in strict mode.
• Use owner override allows advanced scanning for the verified website.

For most sites, strict mode is the safest default. Owner override is for sites you own or control where you intentionally want verified-owner scanning behavior.

Robots.txt preview

The robots.txt preview helps you review crawl expectations before starting a scan.

Robots.txt available

This means Siteimp found a robots.txt file and created a preview. Open the details to inspect fetched location, active rules, sitemap entries, and raw content.

No robots.txt found

This means Siteimp did not find a robots.txt file at the expected location. That does not automatically mean the site cannot be scanned. It means the site did not publish a robots file where Siteimp looked.

Robots.txt needs review

This means the file was fetched, but some rules could not be interpreted cleanly. Open the details and review the raw content before relying on the preview.

Robots preview unavailable

This means Siteimp could not preview robots.txt at that moment. The cause may be temporary network trouble, a server response problem, or an unreachable URL.

The preview is still only a guide. The scan checks robots.txt again right before it starts.

Crawl settings

Crawl settings control how politely Siteimp requests pages from this specific website.

Using app defaults

If the section says Using app defaults, this website does not have its own crawl setting override. Future scans use the app-level defaults.

Website override active

If the section says Website override active, this website has its own crawl settings. Those values apply to future scans for this website without changing other websites.

Crawl delay override

The crawl delay is the minimum wait between requests before jitter is applied. A larger delay makes scans gentler but slower.

Crawl jitter override

Jitter adds random extra delay per request. This helps avoid sending requests in an overly mechanical rhythm.

Max concurrency override

When available, max concurrency controls how many crawl requests can run at the same time. A value of 1 is the safest polite default.

Crawl settings not saved

If crawl settings are not saved, check the values and try again.

Delay and jitter must be whole numbers of 0 or higher. Concurrency, when shown, must be a whole number of 1 or higher.

Troubleshooting

Website details did not load

If the website details do not load, Siteimp cannot show the dashboard reliably. Use Back to return to Websites, then try opening the website again.

If the problem continues, contact support and include the website name or the route you were trying to open.

Scan did not start

If a scan does not start, review the error shown near the top of the page. Possible causes include a local database issue, scan setup issue, unreachable site, or scan worker problem.

Try refreshing the page, then start the scan again. If it still fails, contact support and include what happened when you selected Run scan.

Ownership not verified yet

This means Siteimp checked the ownership challenge but did not find the expected verification signal yet.

For meta tag verification, confirm the tag is present in the server-delivered homepage HTML.

For DNS TXT verification, confirm the record name and value match the generated challenge and allow time for DNS propagation.

Ownership check failed

This means Siteimp could not complete the ownership check. Review the displayed error and try again.

If it continues, contact support with the website, verification method, and what happened.

Robots preview unavailable

This means Siteimp could not preview robots.txt right now. You can still try again later. The scan will also check robots.txt before it starts.

Recent scans did not load

If recent scans do not load, use Refresh. If the error continues, the local scan history for this website may need review.

No scans match this view

If no rows match the current Recent scans view, your filters are hiding the available scan history.

Try All scans, All modes, or Reset view.

Interrupted scan data found

If Siteimp reports interrupted scan data, it found a scan that did not finish cleanly.

This can happen if the app was closed unexpectedly, Windows restarted, the computer went to sleep, or the scan runtime stopped before Siteimp could finish normal cleanup.

You can choose:

• Delete, if you want to remove the unfinished scan data.
• Start new, if you want a clean scan for the same website.
• Support, if you want help reviewing what happened.

Interrupted scan data is stored locally until you choose what to do with it.

Could not delete interrupted scan data

If Siteimp cannot delete interrupted scan data, the local data may still be locked or the scan runtime may still be shutting down.

Try refreshing the Website dashboard and choosing Delete again.

If the problem continues, use Support and include the scan context. This helps support identify the affected snapshot and recovery state.

Could not open scan support context

If Siteimp cannot open scan support context, the support drawer may still open, but some scan-specific details may be missing.

You can still contact support from the Help Drawer. Include the website name, what you were trying to do, and that the scan appeared interrupted.

If possible, also include the scan number shown in Recent scans.

Where to go next

From the Website dashboard, the next most common destinations are:

• Websites, if you want to switch sites or return to the workspace overview
• Scan Results, if you want to inspect the evidence from a completed scan
• Ownership details, if you need advanced scanning options
• Crawl settings, if this site needs different politeness behavior

The Website dashboard is the setup and history hub for one site. Scan Results is where the evidence becomes detailed, inspectable, and ready for decisions.