PurrView
Start monitoring
Menu
Sign in

PurrView Link Fixing Tutorial

Guide · Updated April 14, 2026

Use this guide as your impact-first workflow for bad, unsafe, redirect, and blocked URLs in PurrView.

Start with the issues that reach the most pages, then work through the pages that matter most.

New to the dashboard? The Dashboard Guide covers layout, sections, and navigation before you start fixing.

Start with impact, not volume

Widest-impact issues first

Start in Recent runs, choose one issue type, and look for findings that touch multiple pages. That is usually a better use of time than clearing isolated one-off items first.

If Unsafe appears in the run, review it early. Those are Web Risk outcomes, so the stakes can be higher than a routine redirect cleanup task.

Then move to the important pages

Each finding card in Link Tasks shows a Found on: section with the pages where the issue appears. Click any page URL there to filter Link Tasks to that page, or use the Found on page search field to narrow the queue to a specific URL.

As items are resolved, use Mark Fixed so your working list stays accurate.

Action steps

  1. Filter Link Tasks to Bad.
  2. Review the finding card to see which pages reference the link. Click View Details to open the technical info panel for status codes and additional context.
  3. Edit the source page and update, remove, or replace the destination URL.
  4. Publish the page update.
  5. Return to PurrView and click Mark Fixed.

Repeated issue shortcut

If the same bad destination appears across several pages, check shared layout areas first: header links, footer links, sidebars, reusable blocks, and other common templates.

Trust matters here

Bad links are not only a maintenance issue. They can make a page feel stale or unsupported, especially when the link was meant to support a claim, guide a decision, or send someone to the next step.

If the destination can no longer be replaced cleanly, update the surrounding copy so the page still makes sense without it.

Action steps

  1. Filter Link Tasks to Unsafe.
  2. Click View Details to open the technical info panel. Review the threat type chips, Web Risk state, and Matched URL to understand why the destination was flagged.
  3. Remove or replace the destination URL on the source page.
  4. Publish the page update.
  5. Return to PurrView and click Mark Fixed.

When to escalate

If the flagged URL belongs to a partner, sponsor, vendor, or another business-critical destination, document what you found and share it with the person who owns that relationship before you decide on the final replacement.

Action steps

  1. Filter Link Tasks to Redirects.
  2. Click View Details to open the technical info panel and capture the final destination.
  3. Update your source page to point to the final URL.
  4. Publish and then click Mark Fixed.

When to leave it alone

Some redirects are expected. Campaign tracking links, publisher verification flows, and some trusted third-party destinations can still make sense even when they are not perfectly direct.

Prioritize redirects in navigation, footer links, and high-traffic pages first.

Common reasons

Blocked links are often private destinations, login-protected pages, or sources that do not allow the validator to confirm the URL the way a regular browser session might.

What to do

  1. Click View Details to open the technical info panel and confirm the source page.
  2. If the destination is private by design, click Ignore.
  3. If it should be public, escalate it to the team handling hosting, access, or application behavior.
  4. If you need to hand off a larger set, use Blocked CSV from Export Reports.

Common questions

Should I mark fixed before publishing changes?

Publish first, then use Mark Fixed so the dashboard matches what is actually live.

Do I need to fix every redirect?

No. Focus on the redirects that affect important pages or create unnecessary friction. Leave intentional or low-consequence redirects alone when they are still serving a clear purpose.

What if the same problem appears on multiple pages?

Treat that as a priority signal. Repeated issues are often tied to shared templates or reused content, so one fix can remove a larger amount of friction at once.

Definition of done

1. Publish

The source page update is live.

2. Mark Fixed

The queue reflects that you already handled the work.

3. Recheck

The next monitoring run confirms the issue is resolved or tells you if more work is still needed.