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 rules, crawl settings, recent scan history, monitoring pause behavior during scans, 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 robots rules, adjust crawl 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. Scan Results is 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 file tell Siteimp?
• Can Siteimp start a scan right now?
• Which crawl settings will future scans use?
• What happens to monitoring while a scan is running?
• 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.

Before Siteimp enables scan startup, the dashboard checks the current robots preview for the website start URL. If a matching robots rule blocks the scan, the button changes to explain the next action.

The button may show:

• Run scan, when no blocking robots rule is currently shown
• Checking..., while Siteimp is checking robots.txt
• Verify ownership, when a wildcard block applies and owner override is not active
• Scan blocked, when the Siteimp group blocks this URL

Scan startup is still the final gate. When a scan actually starts, Siteimp checks robots.txt again before it creates a snapshot, seeds the queue, or launches the runner.

Scan blocked by Siteimp group

If the Siteimp group disallows the current start URL, Siteimp disables the scan button and shows Scan blocked.

For example:

User-agent: Siteimp
Disallow: /

This is a hard stop. Ownership override does not bypass a Siteimp-specific block.

Remove or change the Siteimp group rule in robots.txt if you control the site and want Siteimp to scan it.

Ownership required for wildcard block

If the wildcard group disallows the current start URL and owner override is not active, Siteimp disables scan startup and shows Verify ownership.

For example:

User-agent: *
Disallow: /

This is a general robots block. Siteimp respects it by default.

If you own or control the site, verify ownership and enable owner override before scanning through the wildcard block.

Owner override active

If the wildcard group disallows the URL but verified owner override is active, Siteimp can allow the scan to continue.

Owner override applies to wildcard blocks only. It does not bypass a Siteimp group block.

Monitoring during scans

Siteimp includes lightweight website monitoring, but scans are the heavier operation. A scan can involve crawling, Lighthouse, media checks, external link checks, artifact writing, database work, and result derivation.

To keep scan results stable and avoid unnecessary background competition, Siteimp pauses scheduled monitoring while any scan is queued or running.

This means:

• scheduled monitoring checks pause when a scan starts
• monitoring remains configured and is not turned off
• monitoring resumes automatically after active scan work finishes
• existing monitoring history is preserved
• scan work gets priority while it is running

The Website dashboard shows this near the scan controls so the behavior is visible before you start a scan. When a scan starts, Siteimp may also show an InfoDock message explaining that monitoring has paused and will resume automatically after the scan finishes.

This pause applies to Siteimp’s built-in monitoring. It does not change any external monitoring service you may use outside Siteimp.

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 enable owner override for wildcard robots blocks. It does not bypass Siteimp-specific robots blocks.

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 rules

The Robots.txt rules 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
• whether a Siteimp group was found
• whether a wildcard group was found
• allow and disallow rule counts
• crawl delay
• sitemap locations
• raw robots.txt content when details are open

The preview is useful for orientation and for explaining why the scan button is enabled or disabled. Scan startup still checks robots.txt again before running.

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.

Robots.txt policy on this page

Siteimp uses a simple robots policy:

1. Siteimp checks the Siteimp group first for explicit Siteimp blocks.
2. A Siteimp-specific Disallow is always respected and cannot be bypassed.
3. If no Siteimp-specific block applies, Siteimp checks the wildcard group.
4. A wildcard Disallow is respected unless verified ownership enables owner override.
5. A Siteimp-specific Allow does not bypass a wildcard Disallow.

This policy keeps two site-owner controls separate:

• A site can block Siteimp specifically with User-agent: Siteimp.
• A site can block general automated access with User-agent: *.

If you own the site and want to scan through a wildcard block, verify ownership and enable owner override.

Reading the robots preview

Robots found

This means Siteimp found a robots.txt file and created a preview.

Open details to inspect the fetched URL, final URL, groups, 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.

No Siteimp group

This means the site did not publish a User-agent: Siteimp group.

In that case, Siteimp uses the wildcard group below when deciding whether the URL can be scanned.

Siteimp group found

This means the site published a User-agent: Siteimp group.

If the group contains a matching Disallow, Siteimp treats it as a hard stop. If the group contains an Allow, Siteimp still checks the wildcard group before scan startup.

Siteimp hard block

This means the Siteimp group contains a matching Disallow.

Siteimp will not scan while that rule is present. Ownership override does not bypass it.

No wildcard group

This means the site did not publish a User-agent: * group.

If no Siteimp group blocks the URL and no wildcard group applies, Siteimp can scan.

Wildcard group found

This means the site published a User-agent: * group.

If the wildcard group contains a matching Disallow, Siteimp respects it unless verified ownership and owner override are active.

Wildcard block

This means the wildcard group disallows the current URL.

If ownership is not verified, the dashboard shows Verify ownership instead of Run scan. After ownership is verified and owner override is active, Siteimp can scan through the wildcard block.

Robots.txt needs review

This means the file was fetched, but the parser could not interpret it 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 right now. The scan button can still rely on scan startup as the final check, but the preview may not explain the current robots state until the file can be fetched again.

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.

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, queued, or running scan by selecting the row.

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.

The Start new action follows the same robots gate as the main Run scan button. If robots rules currently block scanning, Siteimp will not start a new scan from an interrupted row.

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 checks current robots rules and 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 owner override for wildcard robots blocks.
4. Review the robots.txt rules before starting a scan.
5. Check crawl settings if this website needs special politeness behavior.
6. Note that scheduled monitoring pauses while scans are queued or running.
7. Run a new scan or open a recent completed scan from the table.
8. Use filters and sorting to review scan history.
9. 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 rules 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.

When the badge shows Scan running or Scan queued, scheduled monitoring is paused. Siteimp resumes scheduled monitoring automatically when active scan work finishes.

Ownership

Ownership verification proves that you control the website. Siteimp uses that state to decide whether owner override 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 unless current robots rules block the scan. 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 verified-owner scanning through wildcard robots blocks.

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.

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 message shown near the scan controls or near the top of the page.

Possible causes include a Siteimp group block, a wildcard block that needs owner override, a local database issue, scan setup issue, unreachable site, or scan worker problem.

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

Scan blocked by Siteimp group

This means the site’s robots.txt contains a Siteimp-specific rule that disallows the current start URL.

Siteimp will not scan while that rule is present. Ownership override does not bypass it.

Ownership required for wildcard block

This means the wildcard group disallows the current start URL and owner override is not active.

Verify ownership and enable owner override if you own or control the site and want Siteimp to scan through that wildcard block.

Robots preview unavailable

This means Siteimp could not preview robots.txt right now. You can try again later. Scan startup will also check robots.txt before it runs.

Monitoring paused during a scan

If monitoring appears paused while a scan is queued or running, this is expected.

Siteimp pauses scheduled monitoring during active scan work so the scan can use the app’s crawl, Lighthouse, media, external-link, artifact, and database resources without background monitoring checks competing with it.

Monitoring resumes automatically when active scan work finishes.

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.

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
• Monitoring, if you want to review monitoring state outside active scan work
• Ownership details, if you need owner override for wildcard robots blocks
• 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.