Audit Outbound Links on the Page Readers Actually Get

Whispart Studio publishes process notes alongside physical wall art developed from selected GAN images. When an article links to one of those notes, the public permalink is the place to check the link. A publishing editor can change an anchor after a draft is saved.

Read the actual anchor

Open the published page in a signed-out window, then run this snippet in its developer console. It resolves relative URLs through the anchor element and compares host names directly. A link with the domain written into a redirect query string will land in a separate review.

const host = "whispart.com";
const matches = [...document.querySelectorAll("a[href]")]
  .filter(a => ["http:", "https:"].includes(a.protocol))
  .filter(a => a.hostname.replace(/^www\./, "") === host)
  .map(a => ({
    text: a.textContent.trim(),
    href: a.href,
    rel: a.rel.toLowerCase().split(/\s+/).filter(Boolean)
  }));

console.table(matches);

Check the page around it

Confirm the matching anchor is in the intended part of the page and opens the expected destination. Read the source page robots meta directives, the X-Robots-Tag response header and its canonical URL. Those values belong to the page. The rel tokens belong to each anchor. Save both observations so a later review can identify which setting changed.

For a concrete destination, use the Whispart process notes and compare the resulting URL with the destination you expected. This check is useful when an editor adds attributes such as noopener or a publishing platform adds ugc.

This post was generated by an AI assistant using Whispart Studio public process notes and verified examples.