The Websites page is the top-level starting point for Siteimp. It gives you a quick view of the websites stored in your local workspace, shows whether they have been scanned yet, and gives you the shortest path into the rest of the application. In practice, this is the page you return to when you want to orient yourself, add another site, or move from one website to another. The page header and actions shown in the application match that role directly, including DB health check, Refresh, and Add website. :contentReference[oaicite:0]{index=0}

This page is intentionally light on deep analysis. Siteimp treats it as an operational map rather than an evidence-heavy dashboard. The deeper material lives inside individual website dashboards and scan results. The footer on the page says that explicitly: this page is your top-level operational map, while website dashboards and scan results hold the deeper evidence. :contentReference[oaicite:1]{index=1}

If you are brand new to Siteimp, this is also the place where the application shows its current state most plainly. If there are no websites yet, the page switches to an empty state and invites you to add your first website. If websites already exist, it switches to summary cards and a table view instead. That means the page does double duty: it is both the first-run starting point and the long-term workspace overview. :contentReference[oaicite:2]{index=2}

What this page is for

The Websites page exists to answer a few simple operational questions quickly:

  • How many websites are in this local Siteimp workspace?
  • Which websites have completed scans?
  • Which websites have not been scanned yet?
  • What is the shortest path into a specific website dashboard?

When website records are present, the page displays three summary cards: Websites, Completed scans, and Not scanned yet. These are derived from the website rows already stored locally and are meant to give you a quick workspace-level snapshot before you drill into any one site. :contentReference[oaicite:3]{index=3} :contentReference[oaicite:4]{index=4}

Below that summary, the main table lists each website with its name, start URL, last scan timing, last scan status, and discovered page count. Each row is clickable, and selecting a row takes you directly into that website’s dashboard. :contentReference[oaicite:5]{index=5}

What you can do here

Review your local website list

The main table is the core of the page. Each row shows:

  • the website name
  • the registrable domain
  • the start URL
  • the last scan date or activity
  • the last scan status
  • the discovered page count for the latest scan

This makes it easy to see, at a glance, which sites are active, which have never been scanned, and which are ready for deeper inspection. :contentReference[oaicite:6]{index=6}

Open a website dashboard

Clicking a row opens the matching website dashboard. The row is also keyboard-accessible, so you can open it with Enter or Space when the row has focus. This is useful if you prefer navigating the app without relying only on the mouse. :contentReference[oaicite:7]{index=7} :contentReference[oaicite:8]{index=8}

Add a website

The Add website action in the page header takes you to the new website form. If your workspace is empty, the page also shows an empty-state button that says Add your first website. :contentReference[oaicite:9]{index=9} :contentReference[oaicite:10]{index=10}

Refresh the list

The Refresh button reloads website records from the local database. If the page is currently loading, the button changes state so the interface reflects that work. :contentReference[oaicite:11]{index=11} :contentReference[oaicite:12]{index=12}

Check database health

The DB health check button runs a local database check and reports the outcome through the in-app feedback system. A successful result confirms that Siteimp can read the local SQLite database and includes the SQLite version in the returned message. :contentReference[oaicite:13]{index=13} :contentReference[oaicite:14]{index=14}

How to use this page

A good default workflow for this page is:

  1. Open Websites to get your workspace-level overview.
  2. Check the summary cards to see how many sites exist and whether any are still waiting for a first scan.
  3. Use the table to choose the website you want to inspect.
  4. Open that website’s dashboard to move into deeper evidence.
  5. Come back here whenever you want to switch websites or add another one.

If you are setting up Siteimp for the first time, the workflow is even simpler:

  1. Open Websites.
  2. Choose Add website.
  3. Create your first website record.
  4. Return here and use the table as your operational starting point.

Understanding the statuses

The page normalizes scan status labels so they are easier to read in the table. For example:

  • completed becomes Completed
  • running becomes Running
  • queued becomes Queued
  • failed becomes Failed
  • aborted becomes Aborted
  • no recorded status becomes No scans

This is why a website that has never been scanned appears as No scans rather than as a blank cell. :contentReference[oaicite:15]{index=15}

The last scan date also has a fallback behavior. If there is no scan timestamp yet, the page shows Never. That helps distinguish between “this website exists but has not been scanned” and “this website has scan history.” :contentReference[oaicite:16]{index=16}

Empty state

If no websites exist in the local workspace, the page does not show the summary cards or the websites table. Instead, it shows an empty state that explains there are no websites yet and invites you to add your first site. The empty-state message also notes that Siteimp will preview robots.txt and help prepare for a polite first scan. :contentReference[oaicite:17]{index=17}

That empty state is important because it signals that nothing is broken. It simply means your workspace has not been set up yet.

Database health check

What it does

The database health check confirms that Siteimp can read the local SQLite database. It is meant as a quick operational test, not a deep repair tool. When the check succeeds, the app reports that the database is healthy and includes the responding SQLite version. :contentReference[oaicite:18]{index=18}

When to use it

Use DB health check when:

  • you want reassurance that the local database is reachable
  • the Websites page feels out of date and you want to rule out a local storage issue
  • you are troubleshooting with support and want to confirm basic local health

Database health check failed

If the health check fails, Siteimp reports that it could not confirm the local database connection and asks you to review the error and try again. This does not automatically tell you the root cause, but it does confirm that the local database needs attention before the rest of the workspace can be trusted fully. :contentReference[oaicite:19]{index=19}

Refreshing the page data

The Refresh action reloads website rows from the local database. This is useful if you suspect the page is stale or if you have just completed an action elsewhere in the app and want to confirm the latest state here. When refresh is running, the page enters a loading state and the button reflects that. :contentReference[oaicite:20]{index=20} :contentReference[oaicite:21]{index=21}

Where to go next

Once you leave this page, the next most common destinations are:

  • Add website, if you are still building out your workspace
  • a website dashboard, if you want to inspect a specific site
  • deeper scan-level pages, after a website already has scan history

In other words, the Websites page is less about deep interpretation and more about clean orientation. It is the page that tells you what exists, what has happened so far, and where to go next.