Redirect Manager
How to Redirect WordPress URLs with Query Parameters
Redirect WordPress URLs with query parameters while preserving functional values and removing only parameters you understand.
Main Menu
Redirects are how a site changes shape without losing the people and the rankings attached to its old addresses. Every URL you retire, every slug you rewrite, every move to a new domain leaves links pointing at something that no longer exists, and a redirect is what catches them.
These guides cover setting them up correctly, which mostly means choosing the right status code. A permanent move and a temporary one are different instructions to a browser and to a search engine, and using the wrong one either loses the ranking you were protecting or caches a change you meant to reverse.
Beyond single URLs: moving a whole domain, redirecting categories and tags, handling query parameters, normalising uppercase and trailing slashes, and doing it in bulk when a restructure produces hundreds at once. There is also the question of what a deleted page should return, which is not always a redirect.
The diagnostic articles deal with the ways redirects go wrong. Chains, where a URL passes through several hops before arriving and loses a little at each one. And loops, where two rules point at each other and nothing loads at all.
Both are invisible from a browser, which shows you the destination and nothing about the route. The diagnostic articles here show how to see the whole path.
Redirect WordPress URLs with query parameters while preserving functional values and removing only parameters you understand.
Choose an honest response for a deleted WordPress URL: 404 when it is unavailable, 410 when removal is deliberate, or a redirect to a genuine replacement.
Handle mixed-case WordPress URLs without corrupting filenames, encoded paths, APIs or external callbacks.
Fix conflicting trailing-slash redirects without breaking files, API routes, feeds or pagination.
Redirect an apex WordPress domain to WWW without loops, certificate failures, broken sessions or unnecessary hops.
Make both hostnames valid over DNS and TLS, configure WordPress for the apex, and redirect WWW directly to the matching HTTPS non-WWW URL.
Redirect obsolete category and tag archives only to equivalent destinations. Map terms and languages explicitly, handle pagination and feeds, and return honest absence otherwise.
After changing a WordPress slug, publish the new URL, map the exact old permalink to it, update first-party links, and verify canonical, sitemap, language, and query behavior.
Keep the old domain operational with valid TLS, map old URLs to equivalent new resources, update dependencies, monitor adoption, and retire it only when safe.
Trace every redirect hop without auto-following, identify its owner, point valid entry URLs directly to the canonical destination, and remove intermediates in order.