A path-level redirect is a redirect rule that targets a specific URL path or URL pattern and forwards it to a defined destination. Unlike a global redirect that sends all traffic from a domain to a single destination regardless of what was requested, a path-level redirect is precise: it matches a particular path and sends it somewhere specific while leaving all other paths unaffected.

A path is the part of a URL that comes after the domain name. In example.com/about, the path is /about. In example.com/blog/post-title, the path is /blog/post-title. A path-level redirect rule targets one or more of these paths and defines exactly where traffic matching that path should go.

Path-level redirects are the building blocks of precise redirect management. They are what separates a sophisticated redirect strategy, one that preserves SEO equity from individual pages, routes visitors to correct equivalent content, and handles complex URL restructuring, from a blunt global redirect that treats all URLs identically.

How a path-level redirect works

When a request arrives at a server, the server checks the requested URL against its configured redirect rules. For path-level rules, the server compares the path of the requested URL, everything after the domain name, against the source pattern defined in each rule.

If the path matches a rule, the server responds with the configured HTTP status code and a Location header pointing to the destination defined for that rule. If the path does not match any rule, the server either returns the page content normally or falls back to a global redirect or 404 error depending on the configuration.

A path-level redirect rule has three core components. The source path: the URL pattern the rule matches against, such as /about or /blog/*. The destination: the URL the matched request is sent to, such as https://newdomain.com/about-us. And the redirect type: the HTTP status code the server returns, most commonly 301 for permanent moves or 302 for temporary ones.

Exact path redirects vs pattern-based path redirects

Path-level redirects come in two broad forms depending on how precisely they match incoming URLs.

Exact path redirects match a single specific URL path and no other. A rule defined for /old-page matches only requests for example.com/old-page and nothing else. example.com/old-page-2 and example.com/old-page/subpage are not matched. Exact path redirects are the most precise form of redirect rule and are used when a specific URL needs to be forwarded to a specific destination.

Pattern-based path redirects use wildcards or regular expressions to match multiple URLs sharing a common pattern. A rule for /old-section/* matches every URL under the /old-section/ path. A rule for /products/*/reviews matches any URL with a product identifier between /products/ and /reviews. Pattern-based rules handle entire sections of a site with a single rule rather than defining individual redirects for every URL.

In practice, a complete redirect configuration for a site or domain typically combines both: exact rules for specific high-value pages that need precise destination mapping, and pattern-based rules for sections or categories where all URLs follow the same routing logic.

Path-level redirects and SEO

Path-level redirects are significantly more valuable for SEO than global redirects in any scenario where individual pages have accumulated backlinks, rankings, or traffic.

Preserving path-level link juice: backlinks pointing to a specific page carry SEO equity for that specific URL. A 301 redirect from that URL to its equivalent on the new domain transfers that equity directly to the correct destination page. A global redirect that sends the same backlink to the homepage dilutes that equity by pointing it at a page that may be entirely unrelated to the original content.

Preserving rankings: pages that rank for specific keywords do so because of the content, backlinks, and signals associated with that specific URL. Path-level redirects tell search engines exactly which page on the new domain inherits the ranking signals from each page on the old domain. Without path-level mapping, those signals are consolidated at the homepage rather than distributed to the most relevant new pages.

Canonical URL precision: path-level 301 redirects send a precise signal to search engines about which URL on the new domain is the canonical version of each piece of content. This is far more useful for index consolidation than a global redirect that maps all old content to a single new URL.

Crawl budget efficiency: when Googlebot follows path-level redirects and finds relevant content at each destination, it is getting value from those crawl requests. When it follows a global redirect from a specific page URL to an unrelated homepage, it is getting less signal about the relationship between old and new content.

Path-level redirects in domain migrations

Domain migrations are the highest-stakes redirect scenario and the context where path-level redirects matter most. Moving an entire site from one domain to another while preserving as much SEO value as possible requires mapping every significant URL on the old domain to its equivalent on the new one.

The standard approach for a domain migration redirect strategy is a tiered one based on URL importance.

Tier 1: high-value pages, the pages with the most traffic, the strongest backlink profiles, and the highest rankings. These get individual exact path redirect rules pointing to their precise equivalents on the new domain. This is the highest-priority work in any migration and the most impactful for SEO preservation.

Tier 2: section-level patterns, sections of the site where URLs follow a consistent structure and the new domain has equivalent sections. A single pattern-based path redirect — /old-section/* to /new-section/* — handles all URLs in the section with one rule.

Tier 3: global fallback, a global redirect or fallback redirect that catches any URL not covered by the higher-tier rules. This ensures no visitor lands on a 404 regardless of which old URL they requested, while higher-tier rules ensure the most important URLs are handled with precision.

This tiered approach balances the practicality of not mapping every URL individually with the SEO imperative of preserving path-level equity for the pages that matter most.

Path-level redirects and query strings

URL parameters and query strings, the ?key=value portion of a URL, add complexity to path-level redirect matching. A request for example.com/page?ref=newsletter has the same path as example.com/page but a different full URL.

Different redirect management tools handle query strings differently. Some path-level rules match only the path and ignore query strings: example.com/page and example.com/page?ref=newsletter are both matched by a rule for /page. Others require explicit query string handling and treat URLs with different query strings as different paths.

The standard approach for most redirect scenarios is to match on the path only and strip or ignore query strings through the redirect: the destination URL typically does not need to receive the query string from the old URL. For specific cases where query string parameters need to be preserved or mapped to new parameter structures, more granular rule configuration is needed.

Path-level redirects vs canonical tags

Both path-level redirects and canonical tags address the problem of multiple URLs serving equivalent content, but they solve it differently and are appropriate in different situations.

A canonical tag is an HTML element in the page head that tells search engines which URL is the preferred version of the content. It is a hint: search engines generally respect it but are not required to. It works without changing the URL that visitors see and without requiring the non-canonical URL to be taken offline.

A path-level 301 redirect is a definitive instruction: it actively sends both visitors and search engines to the canonical URL. It is stronger and more reliable than a canonical tag as a consolidation signal. But it takes the original URL offline: anyone requesting it is sent elsewhere rather than seeing the content at that address.

Use a path-level redirect when a URL is being permanently retired and all traffic should go to the new address. Use a canonical tag when the same content is accessible at multiple URLs for technical reasons but you want to remain accessible at all of them while signalling the preferred version to search engines.

Managing path-level redirects at scale

Individual path-level redirects are straightforward to configure one at a time. The challenge comes at scale: large sites with thousands of pages, complex URL structures, or frequent content changes can accumulate hundreds or thousands of redirect rules that need to be managed efficiently.

Bulk import: defining large numbers of path-level redirect rules through spreadsheet or CSV import rather than one at a time. This is essential for domain migrations where hundreds or thousands of URL mappings need to be deployed simultaneously.

Rule organisation: grouping redirect rules by section, migration batch, or purpose makes large rule sets easier to manage, audit, and update over time.

Regular audits: redirect rules accumulate over time. Rules added for specific migrations or campaigns can become outdated as the destination URLs they point to change or are retired. Regular audits identify stale rules pointing to 404s or redirect chains that need updating.

Testing before deployment: path-level redirect rules should be tested against a representative sample of URLs they are expected to match before going live. A rule that seems correct in isolation can behave unexpectedly with certain URL patterns, query strings, or in combination with other rules.

Path-level redirects and the free vs paid distinction

In redirect management tools, path-level redirects are typically a paid feature while global redirects are available on free plans. This distinction reflects the relative complexity and value of the two redirect types.

A global redirect requires a single rule per domain and handles all traffic with that rule. It is simple to provision and maintain and covers the most basic redirect use cases.

Path-level redirects require individual rules for each URL or pattern, need to be configured precisely, and require ongoing management as the sites on both ends of the redirect evolve. They deliver significantly more SEO value and are the feature that separates a redirect management tool from simple domain forwarding.

This is exactly the distinction Redirect Supply is built around: global redirects on the free plan for domain parking and simple forwarding, path-level redirects on paid plans for the precision redirect management that serious SEO work requires.