Start Monitoring
Menu

PurrView Dashboard Guide

Use this guide to understand what each dashboard area means and what to do after every monitoring run.

Start here if you need orientation before using the link-fixing tutorial.

Start here

Open Recent Runs to see where the work is, then move to Link Tasks and work through each finding. Connect Smart Priority to let Google data surface the most important fixes first.

Recent Runs

This is your starting point after every monitoring run. Each run card shows the target site, the date, a status label (Running, Failed, or Complete), and a label for the run schedule: Monthly scan, Weekly scan, or One-time scan.

The three most recent runs are visible by default. Use the “Show all runs” toggle to expand the full history.

Recent Runs section of the PurrView dashboard showing run cards with status labels, scan type labels, and Internal/External stat groups including Crawled, Images/Files, Bad, Unsafe, Redirects, and Blocked counts.

Internal stats

Crawled — the pages we successfully reached on your site during this run.

Images/Files — internal non-HTML resources (media, scripts, downloads) that were validated.

Bad, Unsafe, Redirects, Blocked — internal findings grouped by type.

Crawled and Images/Files are clickable on completed runs. Clicking opens the Run Links modal with a paginated list of URLs from that stat group.

External stats

Accessible — external destinations that resolved cleanly.

Images/Files — external media and file resources your site references.

Bad, Unsafe, Redirects, Blocked — external findings grouped by type.

Accessible and Images/Files are also clickable on completed runs, opening the same Run Links modal for external URLs.

Run Links modal

Clicking any of the clickable stats (Crawled, Images/Files, Accessible) opens a paginated list of URLs from that run, 50 per page. Each URL shows how many pages it was found on, a sitemap badge if the URL appears in your sitemap, and a Web Risk badge if applicable. Expand any URL to see the pages where it was found.

Queue status and Web Risk processing

Queued runs and the next scheduled date appear here when runs are waiting.

If Web Risk review is still running after the HTTP portion completes, a notice lets you know. You can start working from the queue immediately — unsafe findings will appear as they finish.

Working the queue

Once you understand the layout, here is how to work through findings efficiently.

Mark Fixed

Mark Fixed works at the page level. Each found-on row has its own Mark Fixed checkbox, so you can mark individual pages as you fix them without waiting to resolve every instance.

A card-level Mark Fixed button also appears when you are filtering by a specific page using the Found on page search. This lets you mark the fix for that page–URL pair without expanding the found-on list.

Ignore and Unignore

Use Ignore on a finding card to remove a URL from your active queue — for example, a known-private destination or an expected exception. The Ignored Links button in the panel header shows how many URLs you have chosen to skip, and opens a modal where you can review and Unignore any of them.

Note: Ignore and Unignore are not available to WordPress admin users.

Export Reports

Use the Export Reports disclosure in the panel header to download CSV files when you need to share findings outside the dashboard or assign work to a team. Four exports are available: Blocked CSV, Redirects CSV, Unsafe CSV, and Bad Links CSV. Each is disabled when there are no findings of that type.

Trend Snapshot

Trend Snapshot appears when you have narrowed the scope to a specific site and at least two runs exist for that site. It shows up to eight data points across recent runs, each displaying the date and counts for bad, unsafe, and redirect findings.

Use it to judge whether the queue is improving, holding steady, or growing.

Definition of done for a monitoring run

You have worked a run when every finding has been fixed, ignored, or reviewed and you understand why it remains. The Tasks remaining counter should reflect only items you are intentionally leaving for later. Export a report if you need a record or want to hand off remaining work.

Smart Priority (Google)

Smart Priority blends multiple signals to surface the findings that matter most. Open it from the Smart Priority (Google) button in the Link Tasks panel header.

What Smart Priority does for you

Smart Priority automatically sorts your task list so the most important fixes come first. It looks at which of your pages get the most visitors, which links appear in your sitemap, and whether any links have been flagged as unsafe. When you connect Google Search Console and Analytics, the sorting gets even more precise — pages that bring in real traffic from search get higher priority.

You do not need to understand the scoring — just work from the top of your list.

Connecting Google

To get the most out of Smart Priority:

  1. Click Connect Google (or Reconnect Google if a previous connection expired). This opens a Google OAuth popup. Note: the button is disabled unless you have a single-site scope selected.
  2. Once connected, use the Google property mapping panel to select your Search Console Property and Analytics Property from the dropdowns. Save your selections.
  3. Click Sync now to pull in the latest data from Google. This button is disabled until the connection is active.

After syncing, your Link Tasks list re-sorts based on the blended priority data, and eligible findings gain priority badges and context lines.


Priority badges on finding cards

Once Smart Priority is active, findings show badges based on their priority tier:

P1 — Sitemap: No visible badge. Affects sort order and card accent color only.

P2 — “Not Web Safe”: Shown on findings flagged by Google Web Risk. The context line reads something like “Google flagged this link as unsafe: MALWARE.”

P3 — “Search Console”: Shown on pages receiving organic clicks. The context line tells you how much search traffic the page gets.

P4 — “Analytics”: Shown on pages with recorded sessions. The context line tells you how many visitors the page gets.

Issue types

Triage tip

If the same issue appears across many pages, check shared layout areas first: navigation, footer links, reusable blocks, and other common templates. Finding cards with the “Site-wide” label are almost always template issues.

Bad

Links or resources that are not resolving correctly — HTTP errors, timeouts, and other failures. A missing page is the most common example, but the specific response varies. Open View Details to see the HTTP status code and its meaning.

Unsafe

URLs flagged by Google Web Risk for threats such as malware, social engineering, or unwanted software. Open View Details to review the threat type, Web Risk state, and matched URL before you remove or replace the destination.

Redirects

URLs that still work but take extra hops before reaching the final destination. The redirects shown here are the ones worth updating — multi-hop chains or cross-domain hops where pointing directly at the final URL will improve performance. Open View Details to see the full redirect chain.

Blocked

The destination is blocked by robots.txt, rate-limited, or otherwise inaccessible to the monitor. Confirm whether the block is expected before deciding to ignore or escalate. Open View Details to see the block reason.

View Details — Technical info

Click View Details on any finding card to open the technical info modal. The modal title reflects the issue type: “Broken link — Technical info,” “Redirect chain — Technical info,” “Unsafe link — Technical info,” or “Blocked by robots — Technical info.”

Every modal shows the type badge, priority badge (when applicable), status label (Open, Fixed, or Ignored), target URL, and a type-specific caption with guidance on what to do.

Bad — Response section

Caption: “Target returns {code}. Update or remove the link.”

Fields: HTTP status, Status meaning, Detected at.

Blocked — Robots block section

Caption: “Target is blocked by robots.txt. Replace or contact destination.”

Fields: HTTP status, Block reason, Detected at.

Unsafe — Web Risk section

Caption: “Google Web Risk flagged this URL. Remove or replace it.”

Fields: Threat type chips, Web Risk state, Matched URL, Expires at, HTTP status, Lookup error (if applicable).

Redirects — Redirect chain section

Caption: “Update the link to point directly at the final URL.”

Fields: Hop count, a visual hop timeline (ordered list showing source → intermediate hops → final destination, each with its status code), First status, Final status, Status meaning, Final URL, Detected at.

View Details modal for a broken link showing the type badge, status label, target URL, Response section with HTTP status and status meaning, and the collapsible Response headers grid.
View Details modal for a redirect chain showing the visual hop timeline from source through intermediate hops to the final destination, each with status codes.

Shared sections on every modal

All four modal types include two collapsible sections:

Response headers — a key-value grid of the HTTP response headers returned by the target.

Check history — shows First detected and Last known OK dates.

The action bar at the bottom offers an “Open target” link (hidden for unsafe findings) and a “Copy URL” button.

Ready to start fixing? The link-fixing tutorial walks through the action steps for bad links, unsafe findings, redirects, and blocked URLs.

Contact Support