Home >BlogWordPress Redirect Plugin Plus Host Redirects: How to See the Whole Chain and Spot Extra HopsPublished 2026/11/01Updated 2026/11/01Your WordPress site has a redirect plugin set up, the old URL is supposed to land on the new one, and yet something is off: an extra hop appears in every audit, a 301 turns into a chain of three redirects, or a redirect loop makes a page unreachable. The usual mistake is looking at only one layer. WordPress plugins, .htaccess, Nginx, the hosting panel, and the CDN can all add redirects, and the chain you see in the browser is the sum of every layer. Work it top to bottom: map the whole chain, find the layer that adds the hop, then fix that layer.Symptoms: what "extra hops" actually look likeYou usually notice a chain problem in one of these forms: the browser shows a URL that takes two or three redirects before the final page; SEO tools or Search Console report a redirect chain or a redirect that is not direct; a page bounces between two URLs forever (redirect loop); or you set a rule in the plugin and it works in some places but not others. All of these are the same disease: more than one layer is rewriting the URL, and the layers disagree about the final destination.Why extra hops happen: the common causesWordPress redirect plugins (Redirection, Rank Math, Yoast) add their own rules on top of each other..htaccess or Nginx rewrite rules create another redirect after WordPress has already redirected.The hosting panel (cPanel, Plesk, custom panels) has its own redirect setting that runs before WordPress loads.A CDN like Cloudflare adds edge rules, bulk redirects, or HTTPS/SSL redirects in front of your origin.Scheme normalization (HTTP to HTTPS), host normalization (www to non-www or vice versa), and trailing-slash normalization each produce one redirect.WordPress's canonical redirect (redirect_canonical) silently appends an extra hop when the requested URL differs from the canonical one.How to see the whole chain and isolate the extra hopWork through these checks in order. Each one removes a suspect layer instead of guessing at the combination.1. Disable the redirect plugins temporarilyTurn off Redirection, Rank Math redirects, and Yoast redirects one by one (or all at once), clear any cache, and test the URL again. If the chain shortens, one of the plugin rules is the culprit or the plugins are redirecting on top of each other. Keep the plugins disabled only during testing.2. Inspect .htaccess and Nginx rewrite rulesOpen .htaccess at the site root and look for RedirectMatch and RewriteRule lines; in Nginx, check the server block for return and rewrite directives. A redirect added at this layer runs before WordPress and produces a separate hop. Comment out a single rule at a time and re-test, so you can name the exact rule that adds the hop.3. Check the hosting panel redirectsMany panels have a Redirects section that writes its own rules. It often runs before both WordPress and .htaccess. Look for old redirects left over from an earlier migration, for example one that points the old domain to an intermediate URL instead of the final one.4. Check CDN edge rulesIf you use Cloudflare or another CDN, open the redirect rules, bulk redirects, and the SSL/TLS settings. HTTPS redirection at the edge plus a separate redirect at the origin means the browser follows two redirects for a single page. Test with a curl request to your origin directly to separate the layers.5. Compare the origin response with the public responseRequest the URL against the origin IP (or via the hosting panel's direct URL) and compare it with the public URL. If the origin answers with one redirect but the public URL shows two, the extra hop lives at the CDN or the edge. This single comparison usually pinpoints the layer in minutes.6. Normalize scheme, host, and trailing slashPick one canonical form: https://www.example.com/path (or without www), with or without a trailing slash. Make HTTP redirect to HTTPS once, make the www form redirect once, and let WordPress handle the trailing slash consistently. Each pair that disagrees adds one more hop, and inconsistent canonical settings are the most common source of "one extra hop" complaints.7. Trace the full chain with a redirect chain checkerUse Redirect Chain Checker to see every hop with its status code, response time, redirect loop detection, and final destination. Paste the URL, and the tool lists the chain in order, which lets you see exactly where the extra hop sits instead of reading three browser address bars by hand. For many URLs at once, its bulk check mode and API cover the whole site.Frequently asked questionsQ: How many hops are too many?One redirect (301 from old to new) is normal and expected after a migration. Two or more hops for a single page waste link equity and slow the page; chains of four or more are a clear signal to clean up.Q: Can a plugin and .htaccess conflict?Yes. WordPress plugins write their redirects into the database and run during WordPress processing, while .htaccess runs earlier at the server level. If both redirect the same URL to different targets, you get two hops or a loop.Q: Why does my redirect work on desktop but not on HTTPS-only visitors?The extra HTTPS redirect at the CDN or server runs before your plugin rule. Test the chain with the full https:// URL and compare it with the http:// chain.Q: Does a redirect loop damage the site?It makes the URL unusable for visitors and search engines until fixed, and in rare cases the server returns a 508 or stops responding for that URL. Fix the loop before submitting anything to Search Console.Q: Should I delete old plugin rules after moving hosts?Yes. After a migration, audit every rule: remove rules pointing to dead intermediate URLs and consolidate multiple redirects to the final URL. Fewer rules means fewer places for extra hops to appear.FAQHow many hops are too many?One redirect (301 from old to new) is normal and expected after a migration. Two or more hops for a single page waste link equity and slow the page; chains of four or more are a clear signal to clean up.Can a plugin and .htaccess conflict?Yes. WordPress plugins write their redirects into the database and run during WordPress processing, while .htaccess runs earlier at the server level. If both redirect the same URL to different targets, you get two hops or a loop.Why does my redirect work on desktop but not on HTTPS-only visitors?The extra HTTPS redirect at the CDN or server runs before your plugin rule. Test the chain with the full https:// URL and compare it with the http:// chain.Does a redirect loop damage the site?It makes the URL unusable for visitors and search engines until fixed, and in rare cases the server returns a 508 or stops responding for that URL. Fix the loop before submitting anything to Search Console.Should I delete old plugin rules after moving hosts?Yes. After a migration, audit every rule: remove rules pointing to dead intermediate URLs and consolidate multiple redirects to the final URL. Fewer rules means fewer places for extra hops to appear.