Redirects and moved content
This page is for website creators who move, rename or relaunch content and want old links to keep working. Broken addresses lose visitors and search ranking; Exponential handles most cases on its own.
Contents
- What happens automatically
- Redirects you set up
- Relaunching a site: a redirect plan
- Redirects in the web server
- Safe redirects inside the application
- Checklist
What happens automatically
| Event | Result |
|---|---|
| A node is renamed | a new alias is made; the old one stays and redirects to the new one |
| A node is moved | the same: the old path redirects |
| A translation is renamed | the same, per language |
| A node is removed | the address answers "not found"; nothing redirects |
So editors may rename and move freely. Removing is different: when a page goes, decide where its visitors should go instead and make an alias or a wildcard for it.
Redirects you set up
| Need | Tool |
|---|---|
| One old address to one page | the node's URL aliases tab: add the old address as an alias of the node |
| One address to a module view | Setup > URL translator: a global alias, "Alias should redirect" checked (301) |
| A group of old addresses | Setup > URL wildcards: news/* to articles/{1}, "Redirecting URL" checked |
| Many old addresses at once, after a move or relaunch | Setup > URL translator > Import: a URL map file (CSV, Excel, or the old site's Apache or nginx rules), imported as one batch that can be undone; see Migrating URLs |
| Addresses of another site | a wildcard to an https:// destination |
Wildcards are only consulted when no alias matches, in the order they were created; Try an address shows which wildcard an address matches without changing anything (URL wildcards).
Relaunching a site: a redirect plan
- Export the old site's addresses (its sitemap, or the search engine's list of indexed pages, or the server's logs).
- For each, decide the new destination: same page, a better page, or none (a "gone" page).
- Add patterns as wildcards and single pages as aliases of their node.
- Before launch, test every old address with
curl -sI <old address>and check for a301to the right place. - After launch, watch the error log and the search engines' crawl errors for misses.
| Old address | New destination | Kind |
|---|---|---|
/news/2019/* | /News/{1} | wildcard |
/about.html | node "About us" | alias on the node |
/shop/cart | shop/basket | global alias |
Redirects in the web server
Host and scheme redirects belong in the web server or Velocity, before Exponential runs: http to https, example.com
to www.example.com. See Going live: hosts, HTTPS and siteaccesses and
Velocity HTTPS certificates.
Safe redirects inside the application
Forms and buttons that send visitors "back where they came from" only follow addresses of the site itself, so an attacker cannot use them to send visitors elsewhere (Safe redirects). Use the same functions in your own code (Forms, CSRF protection and HTTP input).
Checklist
- To do: Editors know renaming and moving keep old addresses working, removing does not.
- To do: Removed pages get an alias or wildcard to a replacement.
- To do: A relaunch has a tested redirect table.
- To do: Host and HTTPS redirects are in the web server.
- To do: Redirects are 301 (permanent) unless the move is temporary.
Related pages
- Migrating URLs
- URL aliases and nice URLs
- URL wildcards and custom aliases
- Moving from an older installation
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.