Web Plura

Free public URL tool

Redirect Checker

Trace the public redirect path for a URL and review final status without using a full browser run.

Website speed testTroubleshooting guide

Problem, cause, fix, verify

Problem

Redirect issues can hide behind cache, migration, HTTPS, www/non-www, language, and plugin rules unless the observed public chain is captured for the exact URL.

Audience

WordPress owners, SEO teams, developers, and agencies checking protocol, hostname, and path redirects.

First check

Enter a public URL to inspect the redirect path observed by WPlura's bounded HTTP-lite request.

Verify

Map the redirect owner before changing rules: hosting, CDN, WordPress settings, SEO plugins, multilingual plugins, custom code, or imported database values.

Editorial trust

Published
Updated
Content type
Tools
Review editorial policy

On this page

Decision Support

Redirect issues can hide behind cache, migration, HTTPS, www/non-www, language, and plugin rules unless the observed public chain is captured for the exact URL.

For: WordPress owners, SEO teams, developers, and agencies checking protocol, hostname, and path redirects.

Use The Tool

What this tool helps you check

Inputs

Enter a public URL to inspect the redirect path observed by WPlura's bounded HTTP-lite request.

Output

Review redirect hop count, hop status, final URL, final HTTP status, and timing for each observed hop.

How To Read It

One expected HTTP-to-HTTPS or canonical hostname redirect is usually normal. Long chains, loops, mixed final hosts, or unexpected destinations deserve review before SEO, cache, or migration work continues.

WordPress Fix Path

Map the redirect owner before changing rules: hosting, CDN, WordPress settings, SEO plugins, multilingual plugins, custom code, or imported database values.

This follows the same bounded public URL redirect chain as the HTTP-lite speed test and reports only observed public hops.

Limitations

Use the result as planning guidance

  • Uses bounded HTTP-lite redirect handling.
  • Does not run JavaScript or inspect browser-only navigation.
  • Private, localhost, internal, credentialed, and unsupported targets are blocked.