PurrView Link Fixing Tutorial
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.
Definition of a good session
Choose one issue type, fix the highest-impact items first, then mark work done before you move on.
Quick Navigation
What PurrView checks
PurrView validates link behavior. It does not store external link HTML, and your page HTML is only handled briefly for the checks needed to produce the run.
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
Use Found on Task List to work from page-level impact, and use Found on page or Show Issues when you need to narrow the queue to a specific URL.
As items are resolved, use Mark Fixed so your working list stays accurate.
Fix a bad link
Action steps
- Filter Issue Details to Bad.
- Open Details and review Found on pages (N), the source pages, and any available link text.
- Edit the source page and update, remove, or replace the destination URL.
- Publish the page update.
- 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.
Editorial tip
If a citation URL is dead, search the publisher by headline before removing it. Many sources move without changing titles, and replacing the destination can be better than deleting the reference.
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.
Handle an unsafe finding
Action steps
- Filter Issue Details to Unsafe.
- Open Details and review Threat types, Web Risk state, Matched URL, and Found on pages (N).
- Remove or replace the destination URL on the source page.
- Publish the page update.
- 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.
Web Risk note
If the dashboard says Web Risk review is still processing for this run, keep working through the other findings and come back to Unsafe once that review finishes.
Fix a redirect
Action steps
- Filter Issue Details to Redirects.
- Open Details and capture the final destination.
- Update your source page to point to the final URL.
- 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.
Handle a blocked link
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
- Open Details and confirm the source page.
- If the destination is private by design, click Ignore.
- If it should be public, escalate it to the team handling hosting, access, or application behavior.
- If you need to hand off a larger set, use Blocked CSV from Export Reports.
Remember
Blocked does not always mean broken. Sometimes it means the destination is behaving exactly the way its owner intended.
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 run confirms the issue is resolved or tells you if more work is still needed.