HrefHub
HrefHub

HrefHub

0/5 (0 ratings) — active installs Updated Nov 8, 2026

You changed a URL. Now it is wrong in forty-seven posts and you have no list of
which ones.

Broken link plugins tell you what is broken. Search-and-replace plugins swap a
string across your database and hope. Neither of them shows you what you actually
have. HrefHub is the link inventory: every link on the site, grouped by
where it points, with the number of places it appears and what happens when you
follow it.

Then it lets you change one of them everywhere, in one action.

What it does

  • Lists every link found in post content and Gutenberg blocks, grouped by destination URL
  • Shows how many places each URL appears, and which posts they are
  • Checks HTTP status and counts the redirect chain, so “three redirects” reads differently from “404”
  • Filters by status, internal or external, and post type; search by address, site name or anchor text
  • Changes a URL everywhere it appears, with a confirmation preview first
  • One-step undo of the last change
  • Bulk action: replace every redirecting URL with its final destination
  • Bulk action: remove links, reviewing every paragraph first — keep the words, drop them, or rewrite the sentence
  • CSV export of whatever you are currently looking at

The one that saves an afternoon

Sites accumulate redirects. A link you added three years ago now goes through two
or three hops before it lands. Filter to Redirects, select all, and choose
Replace redirects with their final destination. Every one of them is rewritten
to point straight at where it already ends up.

Cleaning up dead links without breaking sentences

Removing a dead link sounds simple until the link text was “click here”. Tick the
links, choose Remove links (review first), and HrefHub shows every paragraph that
uses them. For each one: keep the words, drop them, or rewrite the sentence.
Nothing changes until you choose, links like “here” and “read more” are flagged for
rewording, and the whole run can be undone.

What gets scanned

This version reads:

  • All public post types, plus reusable blocks — untick any you do not want under HrefHub Settings
  • post_content HTML anchors
  • Gutenberg block attributes — button URLs, image links, cover backgrounds and so on

This version does not read links stored by page builders (Elementor), custom
field plugins (ACF), navigation menus, widgets, theme options or FSE templates.
They are not listed and they are not changed. The admin screen states this too,
so you always know what the numbers cover.

Pages built with Elementor, Beaver Builder or Bricks are skipped as a whole. The
builder displays them from its own data, and the copy it leaves in post content
is not what visitors see, so changing links there would change nothing. The admin
screen shows how many were skipped.

Careful by default

This plugin edits your content, so it is built to be boring about it:

  • A preview before every write, showing exactly how many occurrences in how many posts
  • A snapshot of every post before it is touched, and a one-click undo
  • Post revisions are left switched on, as a second safety net
  • No link is called broken until it has failed twice — 403, 429 and 503 get a “needs review” state instead, because a bot filter is not a dead link
  • When a bot filter refuses the quick check, it is asked once more the way a browser would (a normal page request with browser headers), so fewer working links land in “needs review”
  • Removing links never changes a paragraph you did not choose: each one starts as “Leave as is”
  • Your own site’s links are resolved internally rather than fetched over HTTP, which is faster and avoids loopback stalls
  • Scanning runs in small batches, so it finishes on managed hosts that kill long requests

Privacy

HrefHub makes HTTP requests to the URLs found on your site in order to check
their status. It sends no data anywhere else, has no external API, and does not
phone home.

Each check identifies itself as HrefHub and includes your site’s address, so the
owner of a linked site can see who is checking. If a site refuses that check, it
is asked once more with ordinary browser headers. Only the address being checked
is requested; nothing about your site’s content or visitors is sent.