External Link Inventory — Audit Outbound Links in HTML

An external links checker lists the outbound HTTP and HTTPS destinations found in a page’s anchor elements, including destination hosts, anchor labels, rel attributes, target behavior, and repeated occurrences. Enter a permitted public URL or paste the page’s HTML, then filter external links, same-host links, or all web links. The inventory analyzes links declared in the inspected markup; it does not open every destination or declare those destinations healthy. Mailto links, JavaScript URLs, and fragment-only references are excluded from the web destination list, and an incomplete source cannot support a complete link count. Export the inventory as CSV or JSON to review outbound citations, sponsored attributes, accessibility labels, and changes between page versions.

External Links Checker At a Glance

What Counts as an External Link

For this inventory, an external link is an anchor whose resolved URL has a hostname different from the hostname of the inspected page. A link to a different path on the same host remains internal even when its query string or protocol differs. A link to a subdomain is treated as external because its hostname differs, although an organization might manage both hosts. This is a deterministic comparison, not a determination of organizational ownership or domain registration boundaries. Links that begin with a fragment, such as #pricing, do not create another web destination and are omitted. Other schemes, such as mailto and tel, are also outside the HTTP(S) link inventory. These definitions make exported counts understandable and reproducible.

Anchor Labels, Destination URLs, and Rel Values

Each result preserves the destination URL alongside readable anchor text or an available labeling attribute. Those fields should be reviewed together, because an apparently descriptive anchor might point to an unexpected destination or an anchor might contain only an unlabeled icon. The rel field is inspected for tokens such as nofollow, sponsored, and ugc without assuming their presence proves compliance with a particular advertising policy. A target value such as _blank is recorded so you can review how the link is expected to open. The inventory is not an accessibility audit or editorial endorsement, but it puts important attributes into one report that can be checked without manually opening every source-code fragment.

How Relative Links Resolve

A relative href such as ../resources/ is interpreted against the inspected document URL. A root-relative path such as /support/ resolves against the host, while a protocol-relative value beginning with two slashes inherits the document’s current scheme. The parser also considers a valid same-origin base element. Resolving references is essential before categorizing a destination as internal or external, because the raw href may contain no hostname at all. Invalid or nonweb values are counted separately rather than assigned invented destinations. If the original HTML is pasted offline, enter the appropriate original page URL; otherwise relative links could be interpreted against an unrelated host and distort the inventory.

Worked Example: Editorial Citations and Sponsored Links

Imagine a page linking to a technical standard twice, a product supplier once, and an internal contact page several times. The inventory produces an entry for each distinct combination of destination, label, rel, and target attributes, with repeated identical occurrences counted. The external-host summary highlights the standard’s domain and the supplier’s domain, while the contact page appears only when same-host or all-links mode is selected. If the supplier link contains rel="sponsored", the relevant flag is visible in the row. The checker does not infer commercial relationships from the wording of a link; it reports the markup that can be inspected and leaves the factual interpretation to the reviewer.

Distinguishing Inventory from Broken-Link Checking

A destination appearing in HTML does not mean it is reachable. Some links point to removed pages, regional redirects, authentication walls, or sites that reject automated requests. This tool inventories declared links and their attributes, but it does not issue outbound requests to every target. Running a mass destination probe would raise additional security, network, rate-limit, and permission concerns. For a page where response status matters, use an explicitly scoped HTTP status checker on selected URLs and record access failures without assuming a 403 response means the link is permanently broken. Keeping discovery separate from availability testing makes the report less misleading.

Using a Public Page or Saved HTML

The live mode sends the source URL to the existing restricted PHP inspection endpoint, which validates public destinations, DNS, redirects, robots rules, response size, and rate limits. When it retrieves an HTTP 200 HTML document, the browser extracts anchors from that response. The offline mode parses pasted HTML or a local file without making a network assertion. Choose the mode that matches your evidence. A copied template may omit links added by a CMS, while a live response may omit elements inserted later by scripts. Neither mode executes third-party widgets or clicks through navigation. A complete inventory of a dynamic application may require a separate rendered-browser crawl.

Reviewing Host Concentration and Repetitions

The destination-host table counts occurrences of the extracted link variants grouped by hostname. This makes it easier to notice when one source domain dominates citations or when a template repeatedly inserts a footer credit. A high count is not automatically a problem; repeated links can serve meaningful navigation or attribution purposes. Examine the individual destinations and their surrounding meaning before deciding to remove or change any link. Likewise, a small set of external hosts is not evidence of inadequate research. The tool should support a deliberate review of context, trust, and destination relevance rather than encouraging arbitrary numerical targets for external-link counts.

Exporting a Link Inventory Safely

CSV export includes quoted text fields and a protective prefix for values that resemble spreadsheet formulas. That is important because anchor text or URLs can contain characters which spreadsheet applications interpret as executable formulas when files are opened. The JSON export retains booleans for flags and the structured host summary, while the CSV offers tabular filtering and sorting. If you compare inventories across versions, preserve the original page URL and inspection mode in your notes. A difference in row counts may come from modified content, different rendering behavior, or an incomplete source download; it should not be attributed to an editorial change until the underlying evidence is checked.

Important Limitations of Markup Analysis

Only links present in the HTML response or supplied source can be analyzed. Navigation created by JavaScript after page load, shadow DOM components, and links inside inaccessible frames may be missing. Anchor elements without href do not count as destinations, and non-HTTP protocols are outside this report. The sample is also capped so a very large document does not consume unbounded browser memory; if the cap is reached, the report identifies the truncation. An external URL is categorized by hostname rather than by corporate ownership or the public suffix list. These constraints should accompany any conclusion about the extent of outbound linking on a site.

Turning Link Findings into Practical Corrections

Start by checking whether the anchor text describes the destination as it appears to a reader. Then review the outgoing URL for obsolete redirects, tracking parameters that were not intended for distribution, incorrect protocols, and unexpected host changes. Confirm the presence of appropriate rel attributes where your policy requires them, and inspect new-window behavior for usability. When a URL includes unwanted campaign parameters, a URL tracking parameter remover can produce a cleaner draft, but removing parameters should never be automated without confirming their legitimate role. Prioritize clear, justified corrections instead of broad changes made only to lower the number of outgoing links.

Frequently Asked Questions

Conclusion

An outbound link inventory supports careful review of destinations, labels, and declared relationships. Use the results as evidence of the inspected HTML, then verify important destinations and the editorial context before making changes.