---
title: Broken Links Across 50 Client Sites — What Should an Agency Fix First?
description: A practical broken-link workflow for agencies — prioritize revenue paths, navigation, internal links, external dependencies, false positives, and ownership.
source: https://pingvera.com/blog/broken-links-across-client-sites.html
---
# Broken Links Across 50 Client Sites: What Should an Agency Fix First?

A broken-link scan across 50 websites does not produce a to-do list. It produces a
 pile.

Some links lose leads. Some break navigation. Some point to a harmless old source in a five-year-old
 article. Some are blocked only for bots. If every 404 receives the same urgency, the agency either
 wastes the week or ignores the report entirely.

The missing step is prioritization.

## Not all broken links have equal impact

Rank a link by where it appears and what the visitor was trying to do.

### Critical

- checkout and payment;
- contact, booking, or quote buttons;
- login and account recovery;
- primary navigation;
- campaign landing pages;
- legal or compliance documents required for a transaction.

### High

- product and service pages;
- internal links from high-traffic pages;
- download links promised in lead-generation content;
- important support documentation;
- canonical migration redirects.

### Normal

- old external citations;
- low-traffic archive pages;
- optional related-reading links;
- third-party resources with a valid replacement.

The priority is business impact, not the raw count.

## Internal and external links require different responses

### Internal broken links

The agency usually controls the fix:

- correct the URL;
- restore the missing page;
- add a relevant 301 redirect;
- remove the link;
- update a template or navigation component.

An internal broken link often points to a deployment, migration, CMS, or routing problem.

### External broken links

The agency cannot restore the destination. Options are:

- replace it with an authoritative alternative;
- link to an archived copy where appropriate;
- remove the citation;
- keep the text without a link.

External sites may also block automated requests while working for browsers. Confirm before
 creating a ticket.

## The context an alert needs

"https://example.com returned 404" is incomplete.

Record:

- source page;
- anchor text;
- destination;
- internal or external;
- HTTP status and redirect chain;
- first and last detection;
- number of pages containing the link;
- whether the source is a critical page;
- confirmation result.

One broken URL repeated in a global footer should become one issue with many occurrences, not 500
 tickets.

## A practical scoring model

Use a simple impact score:

The numbers are less important than consistency. The queue should put the business-critical
 failures first.

## Scan frequency

Use different schedules:

- critical navigation and conversion links: after deployments and daily;
- core content: weekly;
- deep archives and external citations: monthly;
- full portfolio scan: before quarterly reviews or migrations.

Scanning every URL every minute is wasteful and noisy. Broken-link monitoring is a coverage
 problem, not an uptime frequency contest.

## Common false positives

- `403` or `429` responses caused by bot protection;
- temporary vendor outages;
- links requiring authentication;
- `mailto:` and `tel:` schemes treated as HTTP;
- JavaScript navigation missed by a simple crawler;
- relative URLs resolved against the wrong base;
- intentionally removed campaign pages;
- external sites blocking specific regions.

Confirm from another probe or a browser-like request before escalating.

## Turn scan output into agency work

1. Deduplicate by destination and root cause.
2. Assign business impact.
3. Group template-wide occurrences.
4. Confirm high-priority failures.
5. Create one owner per issue.
6. Fix or redirect internal links.
7. Replace or remove external links.
8. Rescan the affected pages.
9. Add the completed work to the client report.

This is where monitoring becomes visible value:

> Fixed three conversion-path links after a content migration and restored the quote flow
>  before the campaign launched.

## Free first check

For an individual site, start with the
 [Pingvera broken-link checker](https://pingvera.com/check/broken-links). For an agency
 portfolio, move from a one-time scan to scheduled monitoring with history, confirmation, ownership,
 and client reporting.

## Frequently asked questions

**Do broken links directly hurt rankings?**

The impact depends on context. Focus first on user experience, crawlability, internal
 navigation, and lost conversion paths rather than treating every 404 as an SEO
 emergency.

**Should every removed page redirect to the homepage?**

No. Redirect to a genuinely relevant replacement. If none exists, a correct 404 or 410 can be
 better than a misleading redirect.

**How should an agency report broken-link work?**

Summarize affected business paths, completed fixes, and remaining client decisions. Keep the
 full URL list in the appendix.

## Sources

- [Google: troubleshooting crawling errors and soft 404s](https://developers.google.com/search/docs/crawling-indexing/troubleshoot-crawling-errors)
- [Google: URL structure and broken relative links](https://developers.google.com/search/docs/crawling-indexing/url-structure)
- [Pingvera broken-link checker](https://pingvera.com/check/broken-links)