Skip to main content
When a page moves or you retire a URL, add a redirect so visitors and search engines land on the new address instead of a dead page. Redirects live in the Site Builder: open More options (the sliders icon in the top bar), choose Site settings, and select the Redirects tab. You can also ask Replo in chat.

​
Add a redirect

1

Open the Redirects tab

In the Site Builder, open More options, choose Site settings, and select Redirects.
2

Add a rule

Click Add redirect. If you already have rules, the button is Add.
3

Set From and To

From is the old path on this site. It must start with /, for example /old-page. To is another path on this site (/new-page) or a full address (https://example.com/page).
4

Choose Permanent or Temporary

Permanent tells search engines to update their links. Temporary keeps the old URL indexed. Use Permanent unless you plan to put the old URL back.
5

Save, then publish

Click Done on the rule, then Save. Redirects go live the next time you publish the site.
If you leave with unsaved changes, Replo asks you to save or discard them.

​
Path patterns

An exact path matches that page only. To cover a whole section, add /:rest* so everything underneath moves too. Reuse the same name in To to keep the rest of the path: /old-blog/:rest* to /blog/:rest* sends /old-blog/post to /blog/post. Leave the capture out of To to send every match to one page. Write /old-blog/:rest*, not /old-blog/*. A bare * does not capture anything, and the form will reject it.

​
Priority

Redirects run from top to bottom. The first match wins. Drag a rule to change its priority. Put a specific exception above a catch-all. If /blogs/:rest* sits above /blogs/sale, the sale rule never runs, and the form flags it: “This redirect can’t run because /blogs/:rest* matches first.”

​
Permanent vs temporary

The form offers two types:
  • Permanent (the default). Search engines replace the old URL with the new one. Use this when the move is lasting.
  • Temporary. Search engines keep the old URL indexed. Use this for a short-term campaign or a page you will bring back.

​
Custom redirects

Some redirects cannot be edited in this form, for example a rule that depends on a cookie, a login state, or a destination computed in code. Those appear under Custom redirects as read-only. Ask Replo in chat to change one.

​
After you rename a page

Changing a page’s URL in Page settings does not create a redirect. Links to the old address stop working unless you add one here. The Page settings URL field warns you about that when you change it.

​
Query strings

A same-site destination keeps the visitor’s query string when To does not define one, so /old-page?utm_source=ad lands on /new-page?utm_source=ad. An off-site destination drops the incoming query unless you include one in To.

​
Languages

On a site with languages turned on, write From as the logical path (/old-page). That rule applies in every language, and same-site destinations pick up the visitor’s language prefix automatically. A language-prefixed source (/en-CA/old-page) matches that language only.

​
FAQ

No. Saving writes the rules to your site. They apply to visitors on the next publish.
Yes. Put a full https:// address in To.
The form blocks a source that does not start with /, a destination that is not a path or a full address, a bare * instead of /:rest*, or a rule shadowed by one above it. Fix the highlighted field, or drag the more specific rule above the catch-all.
No. Custom redirects are read-only on this tab. Ask Replo in chat to change one, rather than fighting the form.
The page moves. Old links 404 unless you add a redirect from the previous path. Page settings reminds you of this when you edit the URL.

​
Next steps

Site Builder

Open Site settings and review your pages before you publish.

Publishing

Publish so saved redirects go live.

Page and SEO settings

Change a page URL, then add a redirect from the old path.

Languages

How redirects apply across localized addresses.