Fix the Pages That Matter First: A 30-Minute Weekly Link Routine

Most advice says to start with your top pages. That is good advice, but it is only half the system.

The better question is not only which pages matter most. It is also which issues reach the most pages.

PurrView is not just for finding broken links. It helps you see which issues spread across multiple pages so you can spend your limited time on fixes that actually move the site forward.

Start with the URLs people actually use to complete something important: landing pages, service pages, campaign pages, donation paths, signup flows, and the places where trust or conversion can break fast.

In Found on Task List, you can see which pages carry the most work. In Issue Details, issue rows show how many pages a problem touches. When the same destination appears across multiple pages, one fix can remove a much larger share of friction.

1. Open the latest run and pick the biggest bucket

Start in Recent runs. Look at the counts for Bad, Unsafe, Redirects, and Blocked. Choose one issue type for the session so the work stays bounded.

If Unsafe is present, do not bury it under routine cleanup. Those are Web Risk outcomes, and they deserve early review because the destination may create a trust or safety problem for visitors.

2. Find issues affecting multiple pages

Move to Issue Details and scan for repeated problems. Issue rows show how many pages are involved, so you can spot the problems with the widest footprint before you start working page by page.

One broken footer link can matter more than five random broken links buried in old posts.

3. Fix the top pages those issues touch

Use Found on page to narrow the list, or use Show Issues from the relevant page in Found on Task List. That switches you from issue-first triage to page-first work without losing context.

4. Spend the rest of the session on the next highest-impact pages

After the repeated issues are handled, work down Found on Task List. Focus first on the pages with clear business value. As you finish items, use Mark Fixed so the list reflects what has actually been resolved.

This routine works because it is small enough to repeat. You are not trying to empty the queue. You are trying to reduce the biggest source of friction before the next week gets busy again.

A shorter routine also leaves room for judgment. If a blocked URL is private by design or a redirect is intentional, ignore the true exception, mark what is done, and leave the rest for the next pass.

If the dashboard says Web Risk review is still processing for this run, keep working through the HTTP findings already in front of you and circle back to Unsafe outcomes when that review finishes.

• 5 minutes: review the latest run and choose one issue type
• 10 minutes: fix repeated problems affecting multiple pages
• 10 minutes: work through 1 to 3 top pages with the highest value
• 5 minutes: mark resolved items, ignore true exceptions, and leave the rest for next week

A spreadsheet can make every broken URL look equally important. They are not. The order of operations matters because it keeps you from spending the whole session on tidy but low-consequence work.

1. Issues affecting multiple pages
2. Unsafe outcomes and issues on top landing pages or conversion pages
3. Broken internal paths
4. Bad outbound references
5. Redirect cleanup and lower-priority edge cases

This order gives you the widest reach first, then the highest-value pages, then the cleanup work.

Exports still have a place. They help when you need to hand work to another team, archive a run, or review patterns offline.

But exports are a bad starting point. Giant CSVs flatten priority. The dashboard keeps the work attached to the issue type, the number of pages affected, the source pages, and the current status. That makes it easier to decide what to do next without turning routine upkeep into a sorting exercise.

PurrView already gives you export options for Blocked CSV, Redirects CSV, Unsafe CSV, and Bad Links CSV. Use them later if you need them. For weekly cleanup, start in the working UI instead.

Google’s guide to using Search Console is useful for monitoring how your site appears in Google Search and for catching issues Google surfaces. Google’s crawling troubleshooting documentation is also useful when you need to understand what Googlebot is or is not crawling.

That is still a different job from weekly link maintenance. Search Console reflects Google’s search and crawling view. It is not a page-by-page working list of every bad link, unsafe outcome, redirect, or blocked URL your team should fix next. Use it as supporting context, not as the main cleanup workflow.

This routine fits teams that need steady upkeep more than heroic cleanup days.

Small businesses: When time is tight, a short weekly pass is more realistic than a quarterly cleanup marathon.

Nonprofits: Older resource pages, archived campaigns, and long content libraries make repeated issue triage especially useful.

Marketing teams: Routine upkeep is easier when the work starts with the pages and issues most likely to affect live campaigns.

Agencies: This is a practical rhythm for post-launch QA, maintenance work, and client reporting without turning every run into a spreadsheet exercise.

You do not need a quarterly cleanup marathon. Give broken links 30 focused minutes a week. Start with the issues that affect the most pages, then work through the pages that matter most. That is how link maintenance stays manageable.