A global redirect is a redirect rule that forwards all traffic arriving at a domain to a single destination URL regardless of what path or page was requested. It is the broadest possible redirect, a catch-all that treats every URL on a domain identically and sends every visitor to the same place.

When someone visits olddomain.com, olddomain.com/about, olddomain.com/blog/any-post, or any other URL on a globally redirected domain, they all end up at the same destination. The specific path they requested is ignored. The global redirect does not attempt to match paths, preserve URL structure, or route different URLs to different destinations. Everything goes to one place.

Global redirects are the simplest and most widely used form of domain redirect. They require a single rule, minimal configuration, and zero ongoing maintenance as new URLs are added to either domain. For many redirect use cases, domain parking, brand protection domains, retired domains with no content worth mapping individually, a global redirect is not just sufficient but the ideal solution.

How a global redirect works

A global redirect is implemented as a wildcard redirect rule matching all paths on a domain, typically expressed as /*, pointing to a fixed destination URL. When any request arrives at the domain, the server matches it against the wildcard pattern, finds a match, and responds with the appropriate HTTP status code and a Location header pointing to the destination.

The destination is always the same regardless of what was requested. A request for olddomain.com/contact gets the same redirect response as a request for olddomain.com/pricing or olddomain.com/deeply/nested/page/that/barely/anyone/visits. The wildcard matches everything and the destination is fixed.

For the redirect to work correctly across all variants of the domain, the global rule needs to handle both HTTP and HTTPS, both www and non-www, and any other variants the domain is accessible under. A complete global redirect setup covers all four combinations:

• http://olddomain.com/* → destination

• https://olddomain.com/* → destination

• http://www.olddomain.com/* → destination

• https://www.olddomain.com/* → destination

Missing any variant means some traffic does not reach the destination correctly, particularly HTTPS variants, which require a valid SSL certificate on the redirected domain to function without browser security warnings.

Global redirects vs path-level redirects

The distinction between global redirects and path-level redirects is one of the most important concepts in redirect management. They serve different purposes, have different SEO implications, and are appropriate in different scenarios.

A global redirect applies a single rule to all URLs on a domain. It is simple, low-maintenance, and ideal when path-level specificity either does not matter or is not possible, such as when the old domain’s URL structure has no equivalent on the destination.

A path-level redirect defines individual rules for specific URLs or URL patterns. olddomain.com/about goes to newdomain.com/about-us. olddomain.com/blog goes to newdomain.com/articles. Each path is mapped explicitly to its correct destination. This is more complex to configure and maintain but significantly more precise, and significantly better for preserving SEO equity from backlinks to specific pages.

The practical rule is straightforward. Use a global redirect when the old domain has no meaningful path structure worth preserving, domain parking, brand protection, retired domains, simple forwarding. Use path-level redirects when the old domain had established content with backlinks to specific pages that you want to forward correctly to equivalent pages on the destination.

In many real-world scenarios both are used together. Path-level rules handle the most important URLs, high-traffic pages, pages with strong backlinks, and a global redirect acts as the fallback for everything else, ensuring no visitor lands on a 404 regardless of what URL they requested.

Global redirects and SEO

The SEO implications of a global redirect depend on the context in which it is used and how it is configured.

SEO equity transfer at the domain level: a global 301 redirect transfers domain-level authority and link juice from the redirected domain to the destination. Backlinks pointing to the root domain (olddomain.com) pass their equity to the destination. This is valuable for domain parking and rebranding scenarios where the old domain has accumulated backlinks over time.

Path-level equity is not preserved: the limitation of a global redirect for SEO is that backlinks pointing to specific pages on the old domain all forward to the same destination rather than to their equivalent pages. A backlink to olddomain.com/detailed-guide carries more SEO value when forwarded to the equivalent page on the new domain than when forwarded to the homepage. A global redirect treats every backlink the same regardless of the page it pointed to.

For domains with significant path-level backlink profiles, a global redirect alone leaves value on the table. Supplementing the global redirect with path-level rules for the most linked-to pages recovers that value without needing to map every URL individually.

Crawl budget efficiency: a global redirect on a domain with many previously indexed URLs generates crawl activity as Googlebot follows each redirect. Since all redirects resolve to the same destination, crawlers quickly recognise the pattern. A single-hop global redirect that resolves immediately to a 200 OK keeps this efficient.

Duplicate content prevention: a global redirect consolidates all traffic and authority from the old domain under the destination, preventing both domains from serving content simultaneously and avoiding the duplicate content issues that arise when two domains serve equivalent content without a redirect between them.

Common use cases for global redirects

Domain parking: the single most common global redirect use case. A parked domain that is not actively hosting content forwards all traffic to a primary domain. Whether it is a typo domain, an alternative TLD, an old brand name, or a defensive registration, a global redirect ensures any visitor who arrives, however they got there, reaches the right destination.

Brand protection domains: companies register multiple variations of their primary domain, common misspellings, hyphenated versions, alternative extensions, and globally redirect them all to the primary domain. Each requires nothing more than a single global redirect rule.

Retired domains: a domain that previously hosted a website but is no longer actively maintained. Rather than letting it expire and lose all incoming link equity, keeping it registered with a global redirect to the current primary domain preserves that value indefinitely.

Company mergers: the acquired company’s domain globally redirects to the acquiring company’s site. If the old site’s URL structure does not map cleanly to the new site, a global redirect to the homepage or a relevant landing page is a practical starting point, supplemented by path-level rules for the most important pages.

Simple domain rebranding: a business that rebrands and moves to a new domain globally redirects the old domain to the new one. If the URL structure is identical on both domains, a path-preserving wildcard redirect is better. If the structure has changed significantly, a global redirect to the new homepage is the practical baseline.

Apex to www or www to apex: redirecting one canonical form of a domain to the other is a global redirect. Every request to www.example.com goes to example.com, or vice versa, regardless of path. This is one of the most universal global redirect configurations on the web.

HTTP to HTTPS: redirecting all HTTP traffic to HTTPS is a global redirect at the protocol level. Every URL on the HTTP version of a domain globally redirects to its HTTPS equivalent. While this is typically implemented as a path-preserving wildcard rather than a fixed-destination global redirect, it is conceptually a global rule: every URL on the HTTP domain is covered by a single rule.

Global redirect as fallback

One of the most important practical applications of global redirects is as a fallback rule within a broader redirect configuration. When a domain has both specific path-level rules and a global fallback, the rules work together in a priority order:

Specific path-level rules are evaluated first. If the requested URL matches one of them, that rule fires and the visitor is sent to the mapped destination.

If no path-level rule matches, the global redirect fires as the fallback, sending the visitor to the default destination rather than returning a 404 error.

This layered approach is the most robust redirect configuration for domain migrations and large-scale redirect scenarios. The most important URLs, highest traffic, most backlinks, get their own path-level rules pointing to exact equivalent pages. Everything else is caught by the global fallback. No visitor ever lands on a dead end.

In Redirect Supply this is exactly how the free plan is designed: global redirects for all domains, with path-level rules available on paid plans for domains where more precise mapping is needed.

Global redirects and HTTPS

Handling HTTPS correctly in a global redirect setup is the most common point of failure. The requirements are the same as for any domain redirect but worth restating explicitly because the consequences of getting it wrong affect every single visitor to the domain.

The redirected domain needs a valid SSL certificate to handle HTTPS connections before the redirect response is sent. Without it, visitors typing https://olddomain.com or following an HTTPS link to the old domain receive a certificate error from their browser before the redirect can happen.

Registrar forwarding almost universally fails this requirement: it operates over HTTP only and has no SSL certificate on the forwarding domain. A global redirect implemented through a dedicated redirect management platform that provisions SSL on all connected domains handles this correctly by default, ensuring every visitor, regardless of which protocol or www variant they use to reach the old domain, is forwarded seamlessly to the destination.

Common mistakes with global redirects

Using 302 instead of 301: a global redirect using a temporary status code does not transfer SEO equity from the old domain to the destination. Always use 301 for global redirects that are intended to be permanent.

Not covering all URL variants: a global redirect that handles HTTP but not HTTPS, or www but not non-www, leaves some visitors and crawlers unable to reach the destination correctly. Cover all four variants.

Not provisioning SSL on the redirected domain: without a valid SSL certificate on the redirected domain, HTTPS visitors see a certificate error before the redirect fires. This affects every HTTPS visitor to the domain.

Sending all traffic to the homepage when path-level mapping is possible: for domains with established content and backlinks to specific pages, supplementing the global redirect with path-level rules for important pages recovers link equity that a pure global redirect leaves behind.

Letting the redirected domain expire: a global redirect only works as long as the domain is registered and pointing to the redirect infrastructure. Letting the domain expire removes the redirect entirely. Maintain registration of all globally redirected domains for as long as they have active backlinks or traffic.

Creating a redirect loop: a global redirect rule that catches its own destination URL creates an instant loop. Always verify the destination is outside the scope of the wildcard rule.