How to Fix Internal Links Pointing to Redirects in WP

You ran a site audit and it came back with a long list of “internal links to redirect” warnings. Or you changed a few slugs last year, and now you notice every click on an old link flashes through a 301 before it lands. The pages still load, so nothing looks broken. It just feels sloppy, and the audit tool won’t let it go.

This is a common one. A Yoast forum thread from early 2024 is titled, simply, “Why are all the links on my website 301 redirects ?”. In that case the cause was a trailing slash mismatch, which is one of several ways this happens.
Below we cover why it’s worth fixing (and why it isn’t an emergency), where these links come from, how to find them by hand, and how to fix them without breaking anything for people arriving from outside your site.
Why internal links to redirects matter (a bit)
When a post links to /old-slug/ and WordPress redirects that to /new-slug/, the browser makes two requests instead of one. The visitor waits for an extra round trip before the real page starts loading.
For search engines, Google’s own documentation on redirects says plainly that Googlebot follows them. So a link through a 301 still gets crawled and still points at the right page. The costs are smaller and more practical:
- Wasted crawling on big sites. Every redirecting link is a URL the crawler fetches just to be told “go over there”. On a 50-page site, nobody cares. On a site with thousands of posts and lots of old links, it adds up.
- Redirect chains. Change a slug twice and you can end up with
/a/to/b/to/c/. Chains are slower and more fragile. If one redirect in the middle gets deleted, the link breaks. - You depend on the redirect forever. If someone cleans up the redirect plugin in two years, or you migrate hosts and lose server rules, every old internal link turns into a 404.
- Noisy reports. Your audits stay full of warnings, which makes the real problems harder to spot.
So: worth cleaning up, not worth panicking over. Your rankings didn’t tank because of a handful of 301s.
Where these links come from
Almost always, it’s one of these:
- A changed slug. You renamed a post’s slug and WordPress quietly redirects the old one. Links you typed into other posts still use the old address. We wrote more about this in changing a permalink without losing traffic.
- A moved page. A page got a new parent, or you restructured categories, so the full path changed.
?p=123shortlinks. Someone copied the “shortlink” or a preview URL and pasted it into a post. WordPress redirects?p=123to the pretty permalink every time.- http links on an https site. Older posts written before you moved to SSL still say
http://. Your server or a plugin redirects them tohttps://. - Trailing slash or www mismatches. Your permalinks end in a slash and the link doesn’t (or the other way round). Same for
www.versus nowww.. WordPress or the server fixes it with a redirect. - Manual redirects. You set up a redirect in a plugin to merge two posts, but the posts linking to the old one were never updated.
How to find them by hand
Search Console won’t really help with this. Its indexing report can show URLs Google found that redirect, but it doesn’t tell you which of your own posts contain the links. You need a crawler that follows your site the way a visitor would.
Option 1: Screaming Frog (free up to 500 URLs)
- Crawl your site.
- Open the Response Codes tab and pick the Redirection (3XX) filter. That’s every URL on your site that answered with a redirect.
- Click one and open the Inlinks tab at the bottom to see which pages link to it.
- For the full list, Screaming Frog has a bulk export for redirection inlinks under Bulk Export > Response Codes. The exact menu label can differ a little between versions, so look around in that menu if it’s not where you expect.
That export is your to-do list: source page, old link, where it redirects to.
Option 2: your SEO audit tool
Ahrefs, Semrush and Sitebulb all flag internal links to redirects in their site audits. They’ll give you a similar list. Whatever tool you use, what you want is three columns: the page with the link, the URL it links to, and the final URL it lands on.
Option 3: spot checks
For a small site, you can search your own posts. In the WordPress admin, search Posts for your old slug, or for http://yourdomain, or for ?p=.
How to fix them
The fix is simple in principle: change each link so it points at the final address. Doing it safely takes a little care.
Take a backup first
Every method below writes to your database. Make a full database backup before you touch anything. Seriously, every time.
For a few links: edit the posts
If your audit found ten links, just open the ten posts and update them. In the block editor, select the link, paste the new URL, save.
For many links: Better Search Replace
Better Search Replace is the usual free plugin for this. Put the old URL in “Search for”, the new one in “Replace with”, select the wp_posts table, and keep the dry run box ticked on the first pass. The dry run tells you how many changes it would make without making them. If the number looks right, untick it and run again.
A few traps people hit:
- Be specific. Search for the full old URL including the trailing slash, like
https://example.com/old-slug/. If you search for just/old-slug, you’ll also rewrite/old-slug-part-2/, which is a different post. - Page builders store links elsewhere. Elementor keeps its content as JSON in post meta, with slashes escaped, so the link looks like
https:\/\/example.com\/old-slug\/. A search onwp_postsalone won’t touch it. You’d need to includewp_postmetaand search for the escaped form too. This is the most common reason people say “I replaced it but the page still shows the old link”. - One URL at a time. If you have a hundred redirecting links, that’s a hundred search-and-replace runs. It works. It’s slow.
With WP-CLI
If you have shell access, WP-CLI does the same job faster and lets you script it:
wp search-replace 'https://example.com/old-slug/' 'https://example.com/new-slug/' wp_posts --dry-run
Check the counts it reports, then run it again without --dry-run. For the http to https case:
wp search-replace 'http://example.com' 'https://example.com' wp_posts --dry-run
Same caveats as above. Same specificity rule, same page builder blind spot unless you include the meta table.
Keep the redirect in place
This is the part people get wrong. Fixing your internal links does not mean you should delete the redirect. Other sites, old emails, bookmarks and social posts still use the old URL, and you have no way to update those. The redirect is for them. Your internal links just shouldn’t need it.
If you’re unsure which type of redirect to keep, our post on 301 vs 302 redirects in WordPress covers it.
Re-crawl to check
Run your crawler again. The Redirection (3XX) list should now only contain URLs that nothing on your site links to (or only redirects you meant to keep, like an affiliate link that goes through a tracking URL).
Doing it inside WordPress with JnK Linkweave Pro
To be clear about the free version: its link check treats a redirecting link as working, because it does work. So Free won’t list these. If you’re on Free, the manual methods above are the way to go.
You can download JnK Linkweave here.
Stopping it from coming back
A few habits help:
- Pick slugs carefully when you publish, and change them rarely. Every slug change creates a batch of these.
- When you do change a slug, fix the internal links the same day, while you remember which posts link there.
- Copy links from the live page’s address bar, not from the editor’s preview or shortlink.
- Run a crawl every few months. A small list is a five-minute job; a list that piled up for three years is an afternoon.
And if a link actually 404s rather than redirecting, that’s a different (and more urgent) problem. We cover that in finding and fixing broken links.
Frequently asked questions
Do internal links to redirects hurt my SEO?
Not much on their own. Google follows redirects, so the link still reaches the right page. The real costs are an extra request for every click, wasted crawling on large sites, and the risk that links break if the redirect is ever removed. It’s worth cleaning up, but it’s not a ranking emergency.
Should I delete the redirect after I fix my internal links?
No. Keep it. Other websites, bookmarks, emails and social posts still use the old URL, and you can’t update those. Fixing internal links just means your own pages stop relying on the redirect.
Why did search and replace not change the link on my Elementor page?
Elementor stores its content as JSON in post meta, with the slashes in URLs escaped. A search on the posts table for a normal URL won’t find it. Include the post meta table and search for the escaped form of the URL as well, after taking a backup.