When you amend the structure of your site or remove pages that may no longer be relevant, your users may be led to a “page not found” error when they use old URLs. Redirects address this problem by directing your users to the correct page when they visit an old URL.
A redirect has two parts:
a source, the old path on your site that no longer leads anywhere, and
a destination, where you want visitors sent instead. The destination can be another page, folder, or collection on your site, or an external website starting with
https://. This also works if the destination page hasn't been published yet: the redirect simply starts working once it goes live.
Only site admins can add, edit, or delete redirects. If you're a publisher or editor, you can still view the list of redirects under Site Settings, but the options to add or delete one won't be available to you.
Add individual redirects
Go to Site Settings > Redirects and fill in the Source and Destination fields using this convention “/path” or “/folder/path”.
For redirects to other pages or resources within the site, you can either type or use the 🔗 Link to a page picker to choose the page, folder, or collection you want to redirect to.
For redirects to external websites, enter the full address in the Destination field, for example
https://www.gov.sg.
Click + Add
Add redirects in bulk
When you are launching a site or restructuring many pages at once, you can add all your redirects together from a CSV file instead of one at a time.
Download and fill in the template
Go to Site Settings > Redirects and select Bulk upload with a .csv.
Select Download redirects template (.csv). The csv template has two columns: When someone visits (the source, an old path on your site) and Redirect them to (the destination).
Add one redirect per row. As with single redirects, a destination can be another page, folder, or collection on your site, or an external website starting with
https://.
Upload and fix any errors
Upload your completed file (
.csv, up to 1 MB) and select Process redirects.
Isomer Studio checks every row against the same rules as a single redirect, and also flags any source that appears more than once in the file.
If any rows have errors, select Download the errors file. This is a copy of your csv file with an added Error column, with the failed rows listed first. Correct the flagged rows, then re-upload the file. Your valid rows are kept, so you do not need to start over.
Publish the batch
When every row is valid, Isomer Studio shows the redirects ready to publish. Expand the list to check each source and destination.
Select Publish to create the whole batch. Every row must be valid before you can publish, as there is no partial publish.
Isomer Studio creates all the redirects and republishes your site in one go. Allow it 5 to 10 minutes to take effect.
Add a Wildcard Redirect
A wildcard redirect sends a whole section of your site to a new location with a single rule, so you do not have to redirect each page one by one. You create a wildcard redirect by ending the source URL with /*.
This is useful when your page links have a new URL structure.
Example: You set the source to /old-news/* and the destination to /newsroom. A visitor who goes to /old-news/2026/budget is sent to /newsroom/2026/budget. Everything after /old-news/ is carried across to the new section, so every page beneath the old path keeps working with just this one rule.
💡 Keep your old links working even when you move content. Whenever you change a published page's URL, or move or rename a page/folder/collection, Isomer Studio will create a redirection for you by default.
View redirects
Every redirect you've added is listed under Site Settings > Redirects. Regardless of your user role, you will be able to see the full list of redirects for your site.
Delete redirects
To remove one, select the trash icon next to it. A confirmation window shows the source and destination so you can check you're removing the right one, then confirm to delete it.
Rules to know when setting up redirects
A redirect can't point back to its own source.
Isomer Studio blocks redirect loops. If
/balready redirects to/a, you can't also redirect/ato/b.Only one redirect is allowed per source. Isomer Studio blocks duplicates.