diff --git a/content/rancher/v2.x/en/faq/cleaning-cluster-nodes/_index.md b/content/rancher/v2.x/en/faq/cleaning-cluster-nodes/_index.md
index a582dfe6a2e..4d9c627eedd 100644
--- a/content/rancher/v2.x/en/faq/cleaning-cluster-nodes/_index.md
+++ b/content/rancher/v2.x/en/faq/cleaning-cluster-nodes/_index.md
@@ -1,6 +1,9 @@
 ---
 title: Cleaning cluster nodes
 weight: 375
+aliases:
+  - /rancher/v2.x/en/installation/removing-rancher/cleaning-cluster-nodes/
+  - /rancher/v2.x/en/installation/removing-rancher/
 ---
 When adding a node to a cluster, resources (containers/(virtual) network interfaces) and configuration items (certificates/configuration files) are created. When removing a node from a cluster (if it is in `Active` state), those resources will be automatically cleaned and the only action needed is to restart the node. When a node has become unreachable and the automatic cleanup process cannot be used, we describe the steps that need to be executed before the node can be added to a cluster again.
 
diff --git a/content/rancher/v2.x/en/installation/single-node/_index.md b/content/rancher/v2.x/en/installation/single-node/_index.md
index e4e920cea7f..dbad2d3808e 100644
--- a/content/rancher/v2.x/en/installation/single-node/_index.md
+++ b/content/rancher/v2.x/en/installation/single-node/_index.md
@@ -2,6 +2,7 @@
 title: Single Node Install
 weight: 250
 aliases:
+  - /rancher/v2.x/en/installation/single-node-install/
   - /rancher/v2.x/en/installation/custom-ca-root-certificate/
 ---
 For development environments, we recommend installing Rancher by running a single Docker container. In this installation scenario, you'll install Docker on a single Linux host, and then install Rancher on your host using a single Docker container.