sourcegraph · marcleblanc2 · Sep 11, 2026 · Sep 10, 2026
diff --git a/docs/admin/pings.mdx b/docs/admin/pings.mdx
@@ -241,7 +241,7 @@ Sourcegraph telemetry pings are handled by a goroutine running on Sourcegraph's
 
 ### Misconfigured update.channel
 
-The most common scenario in which Sourcegraph stops sending pings is a change to the `update.channel` setting in an instance's [site config](https://sourcegraph.com/docs/admin/config/site-config)
+The most common scenario in which Sourcegraph stops sending pings is a change to the `update.channel` setting in an instance's [site config](/admin/config/site-config)
 
 ```
 "update.channel": "release",

diff --git a/docs/admin/repo/auth.mdx b/docs/admin/repo/auth.mdx
@@ -62,7 +62,7 @@ In Sourcegraph 5.1.0 and later, the insecure SSH rsa-sha1 signature algorithm is
 
 If you use an RSA SSH key to authenticate to your code host, you should ensure that your code host runs OpenSSL 7.2 or newer.
 
-If it is not possible to update the code host, you should generate a new ed25519 SSH key to use for authentication. This can be achieved by running `ssh-keygen -t ed25519`, and [configuring Sourcegraph](https://sourcegraph.com/docs/admin/repo/git-config) to use this new key.
+If it is not possible to update the code host, you should generate a new ed25519 SSH key to use for authentication. This can be achieved by running `ssh-keygen -t ed25519`, and [configuring Sourcegraph](/admin/repo/git-config) to use this new key.
 
 ### Error: `Host key verification failed`
 

diff --git a/docs/admin/repo/perforce.mdx b/docs/admin/repo/perforce.mdx
@@ -178,7 +178,7 @@ To ensure Sourcegraph handles host rules according to your requirements, you hav
 
 ##### Enforcing host rules
 
-If you want Sourcegraph to enforce host-specific permissions, you need to enable IP restriction enforcement in your [site configuration](https://sourcegraph.com/docs/admin/config/site-config):
+If you want Sourcegraph to enforce host-specific permissions, you need to enable IP restriction enforcement in your [site configuration](/admin/config/site-config):
 
 ```json
 {

diff --git a/docs/admin/search.mdx b/docs/admin/search.mdx
@@ -76,9 +76,9 @@ Sourcegraph indexes the code on the default branch of each repository. This spee
 
 To view which files are skipped during indexing, visit the repository settings page and click on **Indexing**.
 
-To force the indexer to include specific files (like `yarn.lock` or other large text files) that are otherwise skipped, add their file path or a glob pattern to the [search.largeFiles](https://sourcegraph.com/docs/admin/search#maximum-file-size) setting in your site configuration and reindex the repository. Note that files must still be valid UTF-8 to be indexed, even if added to `search.largeFiles`.
+To force the indexer to include specific files (like `yarn.lock` or other large text files) that are otherwise skipped, add their file path or a glob pattern to the [search.largeFiles](/admin/search#maximum-file-size) setting in your site configuration and reindex the repository. Note that files must still be valid UTF-8 to be indexed, even if added to `search.largeFiles`.
 
-For large deployments we recommend horizontally scaling indexed search. You can do this by adjusting the [number of replicas](https://sourcegraph.com/docs/admin/deploy/kubernetes/configure). Sourcegraph shards repository indexes across replicas. When the replica count changes Sourcegraph will slowly rebalance indexes to ensure availability of existing indexes.
+For large deployments we recommend horizontally scaling indexed search. You can do this by adjusting the [number of replicas](/self-hosted/deploy/kubernetes/configure). Sourcegraph shards repository indexes across replicas. When the replica count changes Sourcegraph will slowly rebalance indexes to ensure availability of existing indexes.
 
 The resource requirements for indexed search vary considerably based on the text contents of your repositories, but a good estimate is that the node should have enough memory to hold the entire text contents of the default branch of each repository.
 

diff --git a/docs/admin/telemetry/private-metadata-allowlist.mdx b/docs/admin/telemetry/private-metadata-allowlist.mdx
@@ -1,12 +1,12 @@
 # Private metadata allowlist
 
-This document lists all telemetry events that are allowed to export specific `privateMetadata` fields (from within [telemetry event parameters](https://sourcegraph.com/docs/admin/telemetry/protocol#telemetrygateway-v1-EventParameters)).
+This document lists all telemetry events that are allowed to export specific `privateMetadata` fields (from within [telemetry event parameters](/admin/telemetry/protocol#telemetrygateway-v1-EventParameters)).
 By default, `privateMetadata` is **never** exported from customers because it can contain arbitrarily-shaped data that may accidentally include sensitive or private contents.
 The specific events and properties listed below have been individually reviewed and approved for export.
 The implementation of each is monitored to ensure they contain only categorized, enumerated information.
 
 The only `metadata` we collect by default are non-sensitive numeric values.
-To learn more, refer to the [telemetry documentation](https://sourcegraph.com/docs/admin/telemetry).
+To learn more, refer to the [telemetry documentation](/admin/telemetry).
 
 | **Event feature** | **Event action** | **Allowed `privateMetadata` fields** |
 | :---------------- | :--------------- | :----------------------------------- |

diff --git a/docs/admin/telemetry/protocol.mdx b/docs/admin/telemetry/protocol.mdx
@@ -3,7 +3,7 @@
 
 This page contains the core schema for telemetry event data that gets exported from Sourcegraph.
 
-To learn more, refer to our [telemetry documentation](https://sourcegraph.com/docs/admin/telemetry).
+To learn more, refer to our [telemetry documentation](/admin/telemetry).
 
 ## Table of Contents
 

diff --git a/docs/code-navigation/private-maven-repository-configuration.mdx b/docs/code-navigation/private-maven-repository-configuration.mdx
@@ -28,7 +28,7 @@ To test and validate the Maven configuration, modify a single repository’s aut
 
 ### Set Up Executor Secrets
 
-Before triggering the indexing process, make sure the environment variables `$ARTIFACTORY_USER` and `$ARTIFACTORY_PASSWORD` are created as [Executor Secrets](https://sourcegraph.com/docs/admin/executors/executor-secrets).
+Before triggering the indexing process, make sure the environment variables `$ARTIFACTORY_USER` and `$ARTIFACTORY_PASSWORD` are created as [Executor Secrets](/admin/executors/executor-secrets).
 
 ### Trigger Indexing
 

diff --git a/docs/code-search/queries/examples.mdx b/docs/code-search/queries/examples.mdx
@@ -118,4 +118,4 @@ Regex searches are also useful when searching boundaries that are not delimited
 repo:^github\.com/sourcegraph/ \bbtn-secondary\b
 ```
 
-More examples of regex searches are available [here](https://sourcegraph.com/docs/code-search/queries#regular-expression-search)
+More examples of regex searches are available [here](/code-search/queries#regular-expression-search)
diff --git a/docs/cody/capabilities/auto-edit.mdx b/docs/cody/capabilities/auto-edit.mdx
@@ -72,7 +72,7 @@ Site admins can opt their organization out of the auto-edit feature by disabling
 
 Auto-edit is available as default for Enterprise customers with [Sourcegraph Model Provider (Cody Gateway)](/model-provider) access. To configure auto-edit:
 
--   Add `fireworks::*` as an [allowed provider](https://sourcegraph.com/docs/cody/enterprise/model-configuration#model-filters)
+-   Add `fireworks::*` as an [allowed provider](/cody/enterprise/model-configuration#model-filters)
 
 The following example demonstrates how to add Fireworks as an allowed LLM provider:
 
@@ -125,7 +125,7 @@ Site admins can opt their organization out of the auto-edit feature by disabling
 
 Auto-edit is available as default for Enterprise customers with [Sourcegraph Model Provider (Cody Gateway)](/model-provider) access. To configure auto-edit:
 
--   Add `fireworks::*` as an [allowed provider](https://sourcegraph.com/docs/cody/enterprise/model-configuration#model-filters)
+-   Add `fireworks::*` as an [allowed provider](/cody/enterprise/model-configuration#model-filters)
 
 The following example demonstrates how to add Fireworks as an allowed LLM provider:
 
@@ -177,7 +177,7 @@ You can opt out and switch back to autocomplete by deselecting it from the Cody
 
 Auto-edit is available as default for Enterprise customers with [Sourcegraph Model Provider (Cody Gateway)](/model-provider) access. To configure auto-edit:
 
--   Add `fireworks::*` as an [allowed provider](https://sourcegraph.com/docs/cody/enterprise/model-configuration#model-filters)
+-   Add `fireworks::*` as an [allowed provider](/cody/enterprise/model-configuration#model-filters)
 
 The following example demonstrates how to add Fireworks as an allowed LLM provider:
 

diff --git a/docs/cody/prompts-guide.mdx b/docs/cody/prompts-guide.mdx
@@ -104,7 +104,7 @@ You can learn more about context [here](/cody/core-concepts/context).
 
 @-mention local and current repositories are only available if you have your repository indexed. Enterprise and Enterprise Starter users can request their admins to add their local project for indexing to get access to @-mention context.
 
-Repository indexing is only available to supported [Code Hosts](https://sourcegraph.com/docs/admin/code-hosts), please reach out to your admins if you require assistance with indexing.
+Repository indexing is only available to supported [Code Hosts](/admin/code-hosts), please reach out to your admins if you require assistance with indexing.
 
 ## Selecting the right LLM
 

diff --git a/docs/cody/use-cases/vsc-tutorial.mdx b/docs/cody/use-cases/vsc-tutorial.mdx
@@ -39,7 +39,7 @@ You can also use the [Cody: Commands Menu](command:cody.menu.commands) which has
 
 **✨ Pro-tips for using Cody commands**
 
--   You can build your own [Custom Commands (Beta)](https://sourcegraph.com/docs/cody/custom-commands) with custom prompts, output into chat or perform code edits, and more.
+-   You can build your own [Custom Commands (Beta)](/cody/capabilities/prompts) with custom prompts, output into chat or perform code edits, and more.
 
 ## Edit Code
 
@@ -53,7 +53,7 @@ You can also use the default keyboard shortcut of `Opt+K`/`Alt+K`.
 
 -   You can open the 💡 menu, with an "Cody: Edit Code" option, by selecting any line of code and using the keyboard short `Command` `.` on macOS or `Ctrl` `.` on Windows & Linux.
 -   If you start an empty line and open the 💡 menu (using the keyboard short `Command` `.` on macOS or `Ctrl` `.` on Windows & Linux) you can use "Cody: Generate Code" to generate new lines of code based on instructions.
--   You define your own custom code editing commands using [Custom Commands (Beta)](https://sourcegraph.com/docs/cody/custom-commands), by setting the [`commands.<id>.mode` property](https://sourcegraph.com/docs/cody/capabilities/commands#commands-id-mode).
+-   You define your own custom code editing commands using [Custom Commands (Beta)](/cody/capabilities/prompts), by setting the [`commands.<id>.mode` property](/cody/capabilities/prompts).
 
 ## Explain Code
-Original file line number
+Diff line change
@@ Expand Up @@
     ##### Enforcing host rules
-    If you want Sourcegraph to enforce host-specific permissions, you need to enable IP restriction enforcement in your [site configuration](https://sourcegraph.com/docs/admin/config/site-config):
+    If you want Sourcegraph to enforce host-specific permissions, you need to enable IP restriction enforcement in your [site configuration](/admin/config/site-config):
     ```json
     {
@@ Expand Down @@