How to find which pages link to a broken URL on your website

Why a broken URL alone is not enough to fix the problem#

A failed destination tells you that a request did not reach the expected content. It does not tell you which article, menu or product page needs editing. Without source context, an editor may spend more time searching the site than making the repair.

Collect the relationship between source page, anchor text and destination. The anchor text explains the promise made to the visitor. The source page identifies the editing location. Together, they help you choose a replacement that fits the surrounding content rather than merely pointing to an address that loads.

Use a whole-site report to locate referring pages#

In Linky, a whole-site scan records source pages and link text for the destinations discovered during the crawl. Start from a connected page, choose a suitable page cap and review the destination you need to repair. Open the reported source to verify the visible reference.

The report only describes the pages and links discovered in that scan. If you know that an unscanned section also uses the destination, audit that section separately or compare the findings with a CMS search. Do not assume that absence from the crawl proves a reference no longer exists.

1. Find the destination that needs attention in a whole-site report.
2. Collect its discovered source URLs and anchor text.
3. Open representative source pages and locate the reference.
4. Identify the page or template responsible for the link.
5. Update the correct source and rescan the affected section.

Separate content references from shared-template links#

A link in one article can often be repaired in that article. A link appearing in a header, footer or reusable callout may be managed elsewhere. If the same destination and wording recur across many pages, inspect the shared component before creating dozens of separate editing tasks.

Also check whether a page contains the destination more than once. A navigation link and a body reference can have different meanings even when their URLs match. Confirm both placements so that fixing one does not leave another misleading link on the same page.

Choose replacement links that match the source context#

Read the surrounding sentence before replacing a reference. A link labeled “API authentication guide” needs material about authentication, not simply the nearest available documentation page. If no suitable replacement exists, revise the sentence so it no longer makes a promise the site cannot fulfill.

Use descriptive anchor text for useful internal links. Avoid changing every link to a vague label just to simplify the report. Readers should understand the destination before clicking. Where a linked document changed its topic or audience, update both the URL and the wording.

Handle URL variations carefully#

A destination can appear with tracking parameters, a fragment, a different host or an older protocol. Decide which variations represent the same useful resource and which carry meaningful behavior. Keep the original observed address in the repair record so the problem can be reproduced.

A fragment may identify a specific section, and a query parameter may select a document version or application state. Removing these components without checking can turn a precise reference into a generic landing page. Conversely, a stale campaign parameter may be unnecessary. Evaluate the role of each component rather than applying one blanket normalization rule.

Create a repair handover editors can use#

A useful handover includes the source URL, visible link text, old destination, proposed destination and reason for the change. Add an owner and a verification step. This lets someone make the edit without guessing the original finding or the intended reader experience.

Group repeated template findings while preserving examples that verify the pattern. Mark uncertain responses as requiring investigation. A clear report should distinguish a confirmed stale URL from a temporary access error and say whether the listed source pages represent full or partial coverage.

• Source page and link placement
• Visible anchor text and surrounding context
• Exact old destination and observed response
• Proposed repair with a relevant destination
• Owner, publication status and verification result

Frequently asked questions#

Put this workflow into practice

Read the related Linky documentation for the product controls and limits used in this article. Contact support if a result requires further investigation.