Start here

Saved views

A saved view is a named snapshot of the results table configuration. It captures which columns are visible, how the table is sorted, which filters are active, and the density mode, so you can switch between different ways of looking at the same crawl without rebuilding the layout each time.

What a view stores

Each saved view records the full set of table settings that were active at the moment it was created:

Setting What is captured
Visible columns The ordered list of columns shown in the table. Hidden columns are excluded.
Sort The active sort column and direction (ascending or descending).
Density mode One of compact, default, or roomy.
Search query The current text in the search field, if any.
Status code filter The selected status code ranges (2xx, 3xx, 4xx, 5xx).
Content type filter The selected content types (HTML, CSS, JavaScript, images, etc.).
Issue toggles Which issue categories are toggled on for filtering.

Applying a view restores all of these settings at once. Anything not listed above — scroll position, selected rows, expanded detail panels — is not part of the view and remains unchanged.

Creating views

Configure the results table the way you want it — choose your columns, set the sort order, adjust density, and apply any filters. Then open the views menu in the toolbar and select Save current view. Give the view a name and confirm.

The new view appears in the views menu alongside any others you have saved. Select a view from the list to apply it, restoring its column set, sort order, density, and filters to the results table.

To update an existing view with your current settings, open the views menu, select the view, and choose Overwrite. To remove a view, select it and choose Delete.

Persistence

Saved views are stored in localStorage. They persist across sessions and crawls but do not sync between machines or browsers.

Views degrade gracefully across app versions. If a column referenced by a saved view no longer exists in the current version, that column is dropped silently when the view is applied. If none of the saved columns survive, the table falls back to its default column set. The view itself is not deleted — it will work again if the columns return in a future update.