How site redirects work
A site redirect sends a visitor who opens an old address straight to a new one. You manage redirect rules in Site settings > Redirects on a Site app: each rule takes a source (a path, or a page from your site) and sends anyone who opens it to a destination you choose, which can be another page, an internal path, or an external address. Every redirect is a permanent move (HTTP 301).
Redirects go live as soon as you save them. You don't need to republish your site, and a redirect works even when the old path still belongs to an existing page.
What a rule looks like
Each rule pairs a source, the address a visitor opens, with a destination, the address they land on. The source can be a path on your site or a page you pick from the site. The destination can be a page from your site, an internal path, or an external address that starts with http or https.
Which rule wins when several could match
When more than one rule could match the address a visitor opens, an exact match beats a wildcard match, and among wildcard rules the longest matching prefix wins.
A rule matches either one exact path or any path that ends with a wildcard:
A rule for the exact path
/blog/summermatches only/blog/summer.A rule for
/blogfollowed by a wildcard matches/blog/summerand/blog/2024/launchalike.
If you also had a wildcard rule for /blog/news, a visitor who opened /blog/news/spring would follow that rule instead of the broader /blog rule, because /blog/news is the longer matching prefix.
Paths are matched case-sensitively, so /About and /about are different addresses. Two paths that differ only in the letter case of a percent escape, such as %2F versus %2f, still match the same rule.
Keep the moved path with :1
A destination path can contain :1, which occupies one complete path segment and copies over the segment the source's wildcard captured, so each visitor keeps the part of the address they originally asked for.
Suppose a rule matches any path under /offers and its destination is /shop/:1. A visitor who opens /offers/laptops lands on /shop/laptops: the captured segment travels with them.
What happens to the query
Query parameters a visitor includes in the old address keep travelling to the destination, unless the destination carries a query of its own.
A visitor opens
/sale?utm_source=emailand the rule's destination is/clearance: they land on/clearance?utm_source=email.The same visitor, with a destination of
/clearance?ref=poster: they land on/clearance?ref=poster, and the original query parameters are not kept.
Query and fragment text in a destination stays exactly as written; a colon inside it is treated as an ordinary character.
Destinations that follow your pages
When a rule's destination is a page, the redirect follows that page's published address. If the page is backed by content in your site's CMS, the redirect keeps following that entry's current address even after you rename it. If a target page or entry disappears, the redirect keeps sending visitors to its last known address instead of dropping the rule.
You set a page's address while you manage pages in the website builder.
Redirects and canonical URLs
A redirect moves visitors from one address to another. Canonical links move no one: they tell search engines which address to prefer when your site is reachable at more than one. See Set canonical URLs for a site.
Create and manage your rules
Open Site settings > Redirects to add, edit, filter, and delete redirect rules.
To set up many redirects at once, import them from a CSV file.