diff --git a/doc/administration/geo/replication/configuration.md b/doc/administration/geo/replication/configuration.md
index 063b992d67328e6947a0ecf56e94bed762c4e0e6..a5d851878124a8192d247c207cbdfd6554a302cc 100644
--- a/doc/administration/geo/replication/configuration.md
+++ b/doc/administration/geo/replication/configuration.md
@@ -190,7 +190,7 @@ keys must be manually replicated to the **secondary** site.
    ```ruby
    ##
    ## The unique identifier for the Geo site. See
-   ## https://docs.gitlab.com/ee/user/admin_area/geo_nodes.html#common-settings
+   ## https://docs.gitlab.com/ee/administration/geo_nodes.html#common-settings
    ##
    gitlab_rails['geo_node_name'] = '<site_name_here>'
    ```
diff --git a/doc/administration/geo/replication/multiple_servers.md b/doc/administration/geo/replication/multiple_servers.md
index 4e597a2192282a6caba7a7959b742742d46301b9..29edac1be8370e6f038ade1d50d9802e70c57c96 100644
--- a/doc/administration/geo/replication/multiple_servers.md
+++ b/doc/administration/geo/replication/multiple_servers.md
@@ -67,7 +67,7 @@ The following steps enable a GitLab site to serve as the Geo **primary** site.
    ```ruby
    ##
    ## The unique identifier for the Geo site. See
-   ## https://docs.gitlab.com/ee/user/admin_area/geo_nodes.html#common-settings
+   ## https://docs.gitlab.com/ee/administration/geo_nodes.html#common-settings
    ##
    gitlab_rails['geo_node_name'] = '<site_name_here>'
 
@@ -217,7 +217,7 @@ then make the following modifications:
 
    ##
    ## The unique identifier for the Geo site. See
-   ## https://docs.gitlab.com/ee/user/admin_area/geo_nodes.html#common-settings
+   ## https://docs.gitlab.com/ee/administration/geo_nodes.html#common-settings
    ##
    gitlab_rails['geo_node_name'] = '<site_name_here>'
 
@@ -318,7 +318,7 @@ application nodes above, with some changes to run only the `sidekiq` service:
 
    ##
    ## The unique identifier for the Geo site. See
-   ## https://docs.gitlab.com/ee/user/admin_area/geo_nodes.html#common-settings
+   ## https://docs.gitlab.com/ee/administration/geo_nodes.html#common-settings
    ##
    gitlab_rails['geo_node_name'] = '<site_name_here>'
 
diff --git a/doc/administration/geo/setup/database.md b/doc/administration/geo/setup/database.md
index 1e582ee5f611c5b0fe096697c49e9a0903f66da9..be6e327732d8e523bc094cbdda6b20b8b8a08a1d 100644
--- a/doc/administration/geo/setup/database.md
+++ b/doc/administration/geo/setup/database.md
@@ -75,7 +75,7 @@ There is an [issue where support is being discussed](https://gitlab.com/gitlab-o
    ```ruby
    ##
    ## The unique identifier for the Geo site. See
-   ## https://docs.gitlab.com/ee/user/admin_area/geo_nodes.html#common-settings
+   ## https://docs.gitlab.com/ee/administration/geo_nodes.html#common-settings
    ##
    gitlab_rails['geo_node_name'] = '<site_name_here>'
    ```
diff --git a/doc/administration/geo/setup/external_database.md b/doc/administration/geo/setup/external_database.md
index 81541d1cb9c218e38093a0881e6ae71b2bae9f2f..50383546da3c3686f05f74fd9a32f68926478e7d 100644
--- a/doc/administration/geo/setup/external_database.md
+++ b/doc/administration/geo/setup/external_database.md
@@ -39,7 +39,7 @@ developed and tested. We aim to be compatible with most external
 
    ##
    ## The unique identifier for the Geo site. See
-   ## https://docs.gitlab.com/ee/user/admin_area/geo_nodes.html#common-settings
+   ## https://docs.gitlab.com/ee/administration/geo_nodes.html#common-settings
    ##
    gitlab_rails['geo_node_name'] = '<site_name_here>'
    ```
diff --git a/doc/administration/monitoring/ip_allowlist.md b/doc/administration/monitoring/ip_allowlist.md
index 89caea691bb73e1a1dbc0f58fcc163b6246c241f..364c1b27d3365140855ee05de6f41aa7766f37e8 100644
--- a/doc/administration/monitoring/ip_allowlist.md
+++ b/doc/administration/monitoring/ip_allowlist.md
@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # IP whitelist **(FREE SELF)**
 
-GitLab provides some [monitoring endpoints](../../user/admin_area/monitoring/health_check.md)
+GitLab provides some [monitoring endpoints](health_check.md)
 that provide health check information when probed.
 
 To control access to those endpoints via IP whitelisting, you can add single
diff --git a/doc/administration/reference_architectures/10k_users.md b/doc/administration/reference_architectures/10k_users.md
index fdb6302aa5be86c23271d7bd39943f3dcdd999f0..e9a77d15a6cfd98e27486d0fdcfc32ebdda3f4d1 100644
--- a/doc/administration/reference_architectures/10k_users.md
+++ b/doc/administration/reference_architectures/10k_users.md
@@ -232,7 +232,7 @@ spread connections equally in practice.
 ### Readiness checks
 
 Ensure the external load balancer only routes to working services with built
-in monitoring endpoints. The [readiness checks](../../user/admin_area/monitoring/health_check.md)
+in monitoring endpoints. The [readiness checks](../monitoring/health_check.md)
 all require [additional configuration](../monitoring/ip_allowlist.md)
 on the nodes being checked, otherwise, the external load balancer will not be able to
 connect.
diff --git a/doc/administration/reference_architectures/25k_users.md b/doc/administration/reference_architectures/25k_users.md
index 4fd32061f733c39c30877d79f6285ac3986418e4..0e608a953b83ba0b5310ebbe7b79c44005fe9678 100644
--- a/doc/administration/reference_architectures/25k_users.md
+++ b/doc/administration/reference_architectures/25k_users.md
@@ -243,7 +243,7 @@ spread connections equally in practice.
 ### Readiness checks
 
 Ensure the external load balancer only routes to working services with built
-in monitoring endpoints. The [readiness checks](../../user/admin_area/monitoring/health_check.md)
+in monitoring endpoints. The [readiness checks](../monitoring/health_check.md)
 all require [additional configuration](../monitoring/ip_allowlist.md)
 on the nodes being checked, otherwise, the external load balancer will not be able to
 connect.
diff --git a/doc/administration/reference_architectures/2k_users.md b/doc/administration/reference_architectures/2k_users.md
index fd45524c5059ccead4f7a59a47fc0331f9d8dd2b..e3e361db13319d7f0499023b9e53acce7455bb94 100644
--- a/doc/administration/reference_architectures/2k_users.md
+++ b/doc/administration/reference_architectures/2k_users.md
@@ -134,7 +134,7 @@ spread connections equally in practice.
 ### Readiness checks
 
 Ensure the external load balancer only routes to working services with built
-in monitoring endpoints. The [readiness checks](../../user/admin_area/monitoring/health_check.md)
+in monitoring endpoints. The [readiness checks](../monitoring/health_check.md)
 all require [additional configuration](../monitoring/ip_allowlist.md)
 on the nodes being checked, otherwise, the external load balancer will not be able to
 connect.
diff --git a/doc/administration/reference_architectures/3k_users.md b/doc/administration/reference_architectures/3k_users.md
index c90bea97e6238dc13a748bffd481b54b6c45c1c9..4b7563d9d8d79c5a9ae7547bf338397182a58b99 100644
--- a/doc/administration/reference_architectures/3k_users.md
+++ b/doc/administration/reference_architectures/3k_users.md
@@ -243,7 +243,7 @@ spread connections equally in practice.
 ### Readiness checks
 
 Ensure the external load balancer only routes to working services with built
-in monitoring endpoints. The [readiness checks](../../user/admin_area/monitoring/health_check.md)
+in monitoring endpoints. The [readiness checks](../monitoring/health_check.md)
 all require [additional configuration](../monitoring/ip_allowlist.md)
 on the nodes being checked, otherwise, the external load balancer will not be able to
 connect.
diff --git a/doc/administration/reference_architectures/50k_users.md b/doc/administration/reference_architectures/50k_users.md
index 1982ec64572a4e9fd5bc2c3a3b19ddc499b943a7..6dc7f7affabd1c20ea4447ab47020cb81a32795d 100644
--- a/doc/administration/reference_architectures/50k_users.md
+++ b/doc/administration/reference_architectures/50k_users.md
@@ -241,7 +241,7 @@ spread connections equally in practice.
 ### Readiness checks
 
 Ensure the external load balancer only routes to working services with built
-in monitoring endpoints. The [readiness checks](../../user/admin_area/monitoring/health_check.md)
+in monitoring endpoints. The [readiness checks](../monitoring/health_check.md)
 all require [additional configuration](../monitoring/ip_allowlist.md)
 on the nodes being checked, otherwise, the external load balancer will not be able to
 connect.
diff --git a/doc/administration/reference_architectures/5k_users.md b/doc/administration/reference_architectures/5k_users.md
index c3a19c31ca3984781e6c0f90568fbb73355209e3..754a844df3f6ffe3546efc4da0c112bdf5f754cf 100644
--- a/doc/administration/reference_architectures/5k_users.md
+++ b/doc/administration/reference_architectures/5k_users.md
@@ -240,7 +240,7 @@ spread connections equally in practice.
 ### Readiness checks
 
 Ensure the external load balancer only routes to working services with built
-in monitoring endpoints. The [readiness checks](../../user/admin_area/monitoring/health_check.md)
+in monitoring endpoints. The [readiness checks](../monitoring/health_check.md)
 all require [additional configuration](../monitoring/ip_allowlist.md)
 on the nodes being checked, otherwise, the external load balancer will not be able to
 connect.
diff --git a/doc/administration/settings/help_page.md b/doc/administration/settings/help_page.md
index febd794b04c42b06f4b9811d3e149af0eb1d4a3f..46c2c395102e296a41952bf0d3ba3b6db299be32 100644
--- a/doc/administration/settings/help_page.md
+++ b/doc/administration/settings/help_page.md
@@ -95,8 +95,8 @@ When redirecting `/help`, GitLab:
 - Appends `.html` to the URL, and removes `.md` if necessary.
 
 For example, if the URL is set to `https://docs.gitlab.com`, requests for
-`/help/user/admin_area/settings/help_page.md` redirect to:
-`https://docs.gitlab.com/${VERSION}/ee/user/admin_area/settings/help_page.html`.
+`/help/administration/settings/help_page.md` redirect to:
+`https://docs.gitlab.com/${VERSION}/ee/administration/settings/help_page.html`.
 
 <!-- ## Troubleshooting
 
diff --git a/doc/administration/settings/index.md b/doc/administration/settings/index.md
index 09c23dae2010b79b7a254264bdc1da06d7202c84..5fc0c029c306069d1570a824517efdb49d42f7ce 100644
--- a/doc/administration/settings/index.md
+++ b/doc/administration/settings/index.md
@@ -41,7 +41,7 @@ The **General** settings contain:
  restrict visibility levels. Configure import sources and Git access protocol.
 - [Account and limit](../settings/account_and_limit_settings.md) - Set projects and maximum size limits,
  session duration, user options, and check feature availability for namespace plan.
-- [Diff limits](../../user/admin_area/diff_limits.md) - Diff content limits.
+- [Diff limits](../diff_limits.md) - Diff content limits.
 - [Sign-up restrictions](../settings/sign_up_restrictions.md) - Configure the way a user creates a new account.
 - [Sign in restrictions](../settings/sign_in_restrictions.md) - Set requirements for a user to sign in.
  Enable mandatory two-factor authentication.
@@ -161,10 +161,10 @@ The **Reporting** settings contain:
 
 - Spam and Anti-bot protection:
   - Anti-spam services, such as [reCAPTCHA](../../integration/recaptcha.md),
-    [Akismet](../../integration/akismet.md), or [Spamcheck](../../user/admin_area/reporting/spamcheck.md).
-  - [IP address restrictions](../../user/admin_area/reporting/ip_addr_restrictions.md).
-- [Abuse reports](../../user/admin_area/review_abuse_reports.md) - Set notification email for abuse reports.
-- [Git abuse rate limit](../../user/admin_area/reporting/git_abuse_rate_limit.md) - Configure Git abuse rate limit settings. **(ULTIMATE SELF)**
+    [Akismet](../../integration/akismet.md), or [Spamcheck](../reporting/spamcheck.md).
+  - [IP address restrictions](../reporting/ip_addr_restrictions.md).
+- [Abuse reports](../review_abuse_reports.md) - Set notification email for abuse reports.
+- [Git abuse rate limit](../reporting/git_abuse_rate_limit.md) - Configure Git abuse rate limit settings. **(ULTIMATE SELF)**
 
 ### Repository
 
@@ -192,7 +192,7 @@ The **Repository** settings contain:
 The **Templates** settings contain:
 
 - [Templates](instance_template_repository.md#configuration) - Set instance-wide template repository.
-- [Custom project templates](../../user/admin_area/custom_project_templates.md) - Select the custom project template source group.
+- [Custom project templates](../custom_project_templates.md) - Select the custom project template source group.
 
 ## Default first day of the week
 
diff --git a/doc/administration/settings/usage_statistics.md b/doc/administration/settings/usage_statistics.md
index df9cf60f6aefdf1de965e4e1aa61a836c29e20e7..ba15ee4e33e08ede0ffe3f15da05d077779e195e 100644
--- a/doc/administration/settings/usage_statistics.md
+++ b/doc/administration/settings/usage_statistics.md
@@ -43,7 +43,7 @@ tier. Users can continue to access the features in a paid tier without sharing u
 
 ### Features available in 14.1 and later
 
-- [Email from GitLab](../../user/admin_area/email_from_gitlab.md).
+- [Email from GitLab](../email_from_gitlab.md).
 
 ### Features available in 14.4 and later