Check outbound links as a visitor, not just as strings

A document can contain a website address without giving its reader a usable link. A publishing tool might show Markdown literally, remove an anchor, or reserve its share page for signed-in users. A successful create response does not answer those questions.

For a small publishing workflow, separate three observations: the service accepted the content, the public page opens in a fresh session, and the reader can use the intended hyperlink. Keeping those observations separate makes a status report much easier to trust.

Start from the returned public address

Use the share URL returned by the service or shown in its publishing dialog. Do not construct it by swapping an editor path for a guessed public path. Some services issue separate addresses for editing and viewing; the editor address can also grant access to change or delete the document.

Keep editing credentials out of the publication ledger. The ledger needs the public address, the time of the check, the response status and the link observations. A private edit link belongs in a credential store.

Open a fresh browser context

An authenticated browser can make a private document appear publicly available. A fresh context provides a useful first check because it does not inherit the publishing account's cookies.

With Playwright installed in a Node.js project, the basic shape looks like this. This example uses a local Chrome installation in a fresh temporary profile:

import { chromium } from 'playwright';

const browser = await chromium.launch({ channel: 'chrome', headless: true });
const context = await browser.newContext();
try {
  const page = await context.newPage();
  const response = await page.goto(process.env.PUBLIC_PAGE_URL, {
    waitUntil: 'domcontentloaded'
  });
  console.log({ status: response?.status() });
  // Wait for this publisher's visible article before inspecting its links.
} finally {
  await context.close();
  await browser.close();
}

The waiting condition should refer to the article itself. A navigation header can load before the document. A fixed delay may be convenient for an initial investigation, but a visible article heading is usually a clearer completion signal for a reusable adapter.

Inspect anchors rather than searching the source text

For our team's projects, an outbound-link test might look for the official AIDropAgent website, the PawMomento storefront and the Crossborder YOUNG website. These are projects managed by our team, used here as concrete examples of intended destinations.

Parse both the expected address and the anchor's resolved href with new URL(). Compare the protocol, hostname and intended path. A substring search for a domain can also match an unrelated hostname or a URL mentioned inside somebody else's query string.

Check that the anchor belongs to the visible article. Record its rel attribute as a separate observation. A link marked nofollow remains a usable hyperlink; that observation does not establish how a search engine will treat it.

Follow platform redirects through their normal interface

Some publishers use an outbound redirect or a confirmation page. Record the link as indirect and follow the visible interface to the destination. A redirect wrapper containing the expected domain is not, by itself, proof that the visitor reaches that domain.

If a public page redirects back to a homepage, retains an access prompt or displays the addresses as plain text, keep the result unconfirmed. Investigate the existing document before creating another copy.

Keep a small evidence record

A practical record includes the publisher, public URL, check time, anonymous response status, expected destination, actual anchor destination and any redirect observation. Keep account creation and editorial review in separate fields.

That is enough to answer a useful operational question: what can a reader actually open now? It also makes failures actionable. An account problem, a public-sharing setting and an absent hyperlink each call for a different next step.

Written by AIDropAgent Team.