How I Troubleshoot a Broken Hyperlink (After 21 Years in IT)

April 01, 2026

After 20+ years in IT, I can tell you this—broken hyperlinks are like flat tires. They never happen at a good time, and they’re almost always something simple… once you find it.

I’ve dealt with broken links everywhere—email systems, SharePoint, VPN portals, internal dashboards—you name it. Over time, I’ve developed a no-nonsense way to track them down without wasting half a day chasing ghosts.

Here’s exactly how I approach it.

Step 1: Don’t Assume—Prove It’s Broken

First thing I do? Click the link myself.

Sounds obvious, but you’d be surprised how often the issue is:

User error
Cached sessions
Or “it didn’t work once, so now it’s broken forever.”

I’ll test it:

In another browser
In private/incognito mode
Sometimes on another machine

If it works for me but not them, I already know I’m dealing with permissions or environment—not the link itself.

Step 2: Look for the “Dumb Stuff” First

After all these years, I’ve learned this the hard way—it’s usually something small and dumb.

I scan the URL for:

Typos
Missing https://
Extra characters
Wrong file names

I can’t tell you how many times I’ve fixed an issue by correcting something like:

report_final_v2_NEW(1).pdf

versus what it should have been.

Step 3: Paste the Link Directly Into the Browser

This is one of my go-to moves.

If it fails → the destination is the problem
If it works → the hyperlink itself is the problem

That one step cuts the troubleshooting path in half immediately.

Step 4: Check Permissions (This Gets People Every Time)

If the link points to:

SharePoint
File shares
Internal apps

I immediately think permissions.

Classic scenario:

“It works for me but not for anyone else.”

That’s not a broken link—that’s access control doing its job.

I check:

Group membership
File/library permissions
Whether the link was copied from a private session

Step 5: Ask One Question: “Did Something Move?”

In IT, things don’t usually break on their own—somebody changed something.

I look for:

Renamed files
Moved folders
Website restructuring
Server migrations

A lot of broken links come from content being relocated without updating references.

Step 6: Check Redirects (Especially for Web Stuff)

If this is a website or external link, I’ll pop open dev tools and check the network tab.

I’m looking for:

301/302 redirects
Redirect loops
Old URLs pointing nowhere

Bad redirects can make a perfectly good link look broken.

Step 7: Look at the Source (When Needed)

If it’s in HTML, an app, or something like Power Apps or SharePoint:

I check:

The actual hyperlink field
Hardcoded URLs
Broken formulas or bindings

Sometimes the link isn’t wrong—the data feeding it is.

Step 8: Consider the Environment

This is where experience really matters.

I start asking:

Is the user on VPN?
Is this internal-only content?
Is Outlook rewriting the link?
Does it work on mobile?

I’ve seen links work perfectly on-network and fail completely off-network.

Step 9: Clear Cache Before You Go Crazy

Before I go too deep, I’ll clear:

Browser cache
DNS cache (ipconfig /flushdns)

Caching has wasted more IT hours than I care to admit.

Step 10: Fix It—and Fix It Properly

Once I find the issue, I don’t just patch it—I fix it so it doesn’t come back.

That usually means:

Updating the correct source (not just one instance)
Fixing permissions properly
Adding redirects if something has moved
Cleaning up messy file naming

Step 11: Prevent the Next One

If you’ve been in IT long enough, you stop thinking about just fixing problems—you think about not seeing them again.

A few habits that help:

Don’t hardcode URLs when you can avoid it
Keep file structures clean
Use consistent naming
Periodically audit links (especially in SharePoint environments)

Final Thoughts

Here’s the truth: broken hyperlinks aren’t complicated—they’re just annoying.

Nine times out of ten, it comes down to:

A typo
A permission issue
Or something that got moved by someone without telling anyone else

The trick isn’t knowing some advanced tool—it’s having a process and sticking to it.

After 21 years in IT, I still follow the same basic steps. They work, they’re reliable, and they save time.

And in this field, saving time is everything.

Virtology