Checking one redirect takes ten seconds. Migrating four thousand URLs without leaking rankings is a different discipline entirely— and the tools that serve each are not the same. Here is what you need for spot checks, for bulk creation, and for a full migration, plus the chain problem every one of them has to solve.
“301 redirect” — 3,600 searches/mo (Google, US)Average monthly US search volume. Source: Google autocomplete demand via AnswerThePublic, 2026.
Job 1 — Checking a single redirect
Any online redirect checker or your browser’s Network tab will show the status code and the full hop chain. What you are looking for: a single 301 straight to the final URL. Two or more hops is a chain worth collapsing; a 302 on a permanent move is a mistake worth fixing, because the old URL stays indexed.
Job 2 — Finding the redirects you don’t know about
This is where spot checks fail. Nobody has a list of which internal links point at redirected URLs — it accumulates over years of edits. Only a crawl finds them, which is why redirect chains and links-to-redirects are standard audit findings rather than something you search for one URL at a time. The free audit reports both across 25 pages without signup.
Job 3 — Bulk creation and migrations
- Crawl the old site first and export every indexable URL — you cannot map what you have not listed.
- Map old to new in a spreadsheet. Closest equivalent, never a blanket redirect to the homepage, which reads as a soft 404.
- Import the map into a redirect manager, using regex patterns for whole folders rather than thousands of individual rows.
- Update internal links to the new URLs. The redirect is the safety net for external links; your own links should point at the destination.
- Monitor 404s for weeks afterwards — the tail you missed shows up as real traffic hitting dead ends.
Server rules versus a redirect manager
Editing .htaccessor nginx config is fastest at runtime, but it is invisible to your team, impossible on many managed hosts, and unauditable six months later. A redirect manager inside WordPress trades a few milliseconds for a list anyone can read, import, export, and search — plus the thing config files can never do: tell you which URLs are actually being hit.
The concepts behind the tooling — 301 versus 302, chains, loops, and when to use 410 instead — are in what is a 301 redirect. Start by finding out what your site currently does: run the free audit.
Frequently asked questions
- How do I check if a URL has a 301 redirect?
- For one URL, open browser developer tools on the Network tab and watch the status codes, or use any online redirect checker — both show the full hop chain. For a whole site, only a crawler answers the question that matters: which internal links point at redirected URLs, and where the chains are.
- What are the best tools for bulk 301 redirects?
- On WordPress, a redirect manager plugin with import/export and regex support handles bulk work: you map old to new in a spreadsheet, import once, and pattern rules cover whole folders. At server level, .htaccess or nginx rules are faster but harder to audit and impossible on many managed hosts.
- How do I migrate URLs without losing rankings?
- Map every old URL to its closest new equivalent before launch, 301 each one, update internal links to point at the new URLs directly rather than through the redirect, keep the old sitemap accessible briefly so crawlers rediscover the map, then monitor 404s for the tail you missed. The step people skip is the internal-link update.
- What is a redirect chain and why does it matter?
- A chain is A → B → C instead of A → C. Each extra hop adds latency for users and crawl cost for search engines, and very long chains may not be followed to the end. Chains accumulate silently across successive site changes, which is why they are a standard audit finding rather than something anyone creates deliberately.
- Do redirects hurt SEO?
- Correctly implemented 301s pass ranking signals and are the mechanism that preserves rankings through a change. What hurts is the sloppiness around them: chains, loops, redirects to irrelevant pages that get treated as soft 404s, and internal links left pointing at the old URLs.
