Fix Ahrefs internal redirect links

community-solutions/runpod-network-volume-storage-tool.mdx

@@ -7,7 +7,7 @@ icon: "floppy-disk"
 
 GitHub repository: [github.com/justinwlin/Runpod-Network-Volume-Storage-Tool](https://github.com/justinwlin/Runpod-Network-Volume-Storage-Tool)
 
-Runpod provides an [S3-compatible layer](/serverless/storage/s3-api) for network volumes, enabling object storage operations on your network storage. This community tool makes it easy to interact with that S3 layer through three interfaces: a command-line interface, a Python SDK for programmatic access, and a self-hosted REST API server for integration with other applications.
+Runpod provides an [S3-compatible layer](/storage/s3-api) for network volumes, enabling object storage operations on your network storage. This community tool makes it easy to interact with that S3 layer through three interfaces: a command-line interface, a Python SDK for programmatic access, and a self-hosted REST API server for integration with other applications.
 
 ## Requirements
 

containers.mdx

@@ -9,7 +9,7 @@ Learn how to build and deploy applications on the Runpod platform with this set
 
 </Card>
 
-<Card href="/tutorials/introduction/containers/" horizontal>
+<Card href="/tutorials/introduction/containers" horizontal>
 ## 📄️ Intro to containers
 
 Discover the world of containerization with Docker, a platform for isolated environments that package applications, frameworks, and libraries into self-contained containers for consistent and reliable deployment across diverse computing environments.

docs.json

@@ -590,7 +590,8 @@
   },
   "logo": {
     "dark": "/logo/runpod-logo-white.svg",
-    "light": "/logo/runpod-logo-black.svg"
+    "light": "/logo/runpod-logo-black.svg",
+    "href": "/overview"
   },
   "navbar": {
     "links": [

flash/apps/apps-and-environments.mdx

@@ -85,7 +85,7 @@ Environments can be in several states:
 |-------|-------------|
 | `deploying` | Deployment in progress (building artifacts, provisioning endpoints) |
 | `deployed` | Successfully deployed and running |
-| `failed` | Deployment failed (check logs in the [Runpod console](https://www.runpod.io/console/serverless)) |
+| `failed` | Deployment failed (check logs in the [Runpod console](https://console.runpod.io/serverless)) |
 | `updating` | Configuration update in progress |
 
 ## Builds and deployments

flash/apps/build-app.mdx

@@ -12,7 +12,7 @@ If you haven't already, we recommend starting with the [Quickstart](/flash/quick
 
 ## Requirements:
 
-- You've [created a Runpod account](/get-started/manage-accounts).
+- You've [created a Runpod account](/accounts-billing/manage-accounts).
 - You've [created a Runpod API key](/get-started/api-keys).
 - You've installed [Python 3.10, 3.11, 3.12, or 3.13](https://www.python.org/downloads/).
 

flash/apps/requests.mdx

@@ -247,7 +247,7 @@ output = run_request.output()  # Get result once complete
 result = endpoint.run_sync({"prompt": "Hello world"})
 ```
 
-See the [Runpod SDK documentation](/sdks/python/endpoints) for complete SDK usage.
+See the [Runpod SDK documentation](/serverless/endpoints/send-requests) for complete SDK usage.
 
 ## Next steps
 
@@ -258,7 +258,7 @@ See the [Runpod SDK documentation](/sdks/python/endpoints) for complete SDK usag
   <Card title="Configuration reference" href="/flash/configuration/parameters" icon="layer-group" horizontal>
     View all endpoint configuration parameters.
   </Card>
-  <Card title="Runpod SDK" href="/sdks/python/endpoints" icon="code" horizontal>
+  <Card title="Runpod SDK" href="/serverless/endpoints/send-requests" icon="code" horizontal>
     Use the Python SDK for programmatic access.
   </Card>
 </CardGroup>

flash/cli/login.mdx

@@ -67,7 +67,7 @@ Or add it to your project's `.env` file for local CLI use:
 RUNPOD_API_KEY=your_api_key_here
 ```
 
-Generate an API key from [Settings > API Keys](https://www.runpod.io/console/user/settings) in the Runpod console.
+Generate an API key from [Settings > API Keys](https://console.runpod.io/user/settings) in the Runpod console.
 
 ## Credential resolution priority
 

flash/configuration/parameters.mdx

@@ -39,7 +39,7 @@ This page provides a complete reference for all parameters available on the `End
 **Type**: `str`
 **Required**: Yes (unless `id=` is specified)
 
-The endpoint name visible in the [Runpod console](https://www.runpod.io/console/serverless). Use descriptive names to easily identify endpoints.
+The endpoint name visible in the [Runpod console](https://console.runpod.io/serverless). Use descriptive names to easily identify endpoints.
 
 ```python
 @Endpoint(name="ml-inference-prod", gpu=GpuGroup.ANY)

flash/custom-docker-images.mdx

@@ -264,7 +264,7 @@ await job.cancel()           # Cancel the job
 - Verify your Docker image is compatible with [Runpod Serverless](/serverless/overview).
 - Check environment variables are correct.
 - Ensure the image includes a valid handler function.
-- Check worker logs in the [Runpod console](https://www.runpod.io/console/serverless).
+- Check worker logs in the [Runpod console](https://console.runpod.io/serverless).
 
 ### Out of memory errors
 
@@ -282,7 +282,7 @@ await job.cancel()           # Cancel the job
 
 **Solutions**:
 - Add `HF_TOKEN` to `env` for Hugging Face gated models.
-- Configure Docker registry authentication in [Runpod console](https://www.runpod.io/console/user/settings) for private images.
+- Configure Docker registry authentication in [Runpod console](https://console.runpod.io/user/settings) for private images.
 
 ## Next steps
 

flash/pricing.mdx

@@ -105,7 +105,7 @@ def process(data): ...
 
 ### Monitoring costs
 
-Monitor your usage in the [Runpod console](https://www.runpod.io/console/serverless) to track:
+Monitor your usage in the [Runpod console](https://console.runpod.io/serverless) to track:
 
 - Total compute time across endpoints.
 - Worker utilization and idle time.

flash/quickstart.mdx

@@ -8,7 +8,7 @@ This quickstart gets you running GPU workloads on Runpod in minutes. You'll exec
 
 ## Requirements
 
-- [Runpod account](/get-started/manage-accounts) with a verified email address.
+- [Runpod account](/accounts-billing/manage-accounts) with a verified email address.
 - [An API key](/get-started/api-keys) with **All** access permissions to your Runpod account.
 - [Python 3.10, 3.11, 3.12, or 3.13](https://www.python.org/downloads/) installed.
 - [uv](https://docs.astral.sh/uv/) installed.
@@ -141,7 +141,7 @@ If you're having authorization issues, you can set your API key directly in your
 export RUNPOD_API_KEY="your_key"
 ```
 
-Replace `your_key` with your actual API key from the [Runpod console](https://www.runpod.io/console/user/settings).
+Replace `your_key` with your actual API key from the [Runpod console](https://console.runpod.io/user/settings).
 </Tip>
 
 ## Step 5: Update and run again
@@ -214,7 +214,7 @@ def gpu_matrix_multiply(size):
 
 The `@Endpoint` decorator configures everything in one place:
 
-- **`name`**: Identifies your endpoint in the [Runpod console](https://www.runpod.io/console/serverless).
+- **`name`**: Identifies your endpoint in the [Runpod console](https://console.runpod.io/serverless).
 - **`gpu`**: Which GPU to use (`GpuGroup.ANY` accepts any available GPU for faster provisioning).
 - **`workers`**: Maximum parallel workers (allows 3 concurrent executions).
 - **`idle_timeout`**: Seconds a worker stays active after completing a request before scaling down. Setting this to 300 (5 minutes) gives you more time to iterate on your code while the worker remains warm.
@@ -413,7 +413,7 @@ def gpu_matrix_multiply(size):
     ...
 ```
 
-You can also check [GPU availability](https://www.runpod.io/console/serverless) in the console.
+You can also check [GPU availability](https://console.runpod.io/serverless) in the console.
 
 ### Import errors
 

flash/troubleshooting.mdx

@@ -32,7 +32,7 @@ Available levels: `DEBUG`, `INFO`, `WARNING`, `ERROR`.
 
 ### Runpod console
 
-View detailed metrics and logs in the [Runpod console](https://www.runpod.io/console/serverless):
+View detailed metrics and logs in the [Runpod console](https://console.runpod.io/serverless):
 
 1. Navigate to the **Serverless** section.
 2. Click on your endpoint to view:
@@ -46,7 +46,7 @@ The console provides metrics including request rate, queue depth, latency, worke
 
 Access detailed logs for specific workers:
 
-1. Go to the [Serverless console](https://www.runpod.io/console/serverless).
+1. Go to the [Serverless console](https://console.runpod.io/serverless).
 2. Select your endpoint.
 3. Click on a worker to view its logs.
 
@@ -88,7 +88,7 @@ Get a key: https://docs.runpod.io/get-started/api-keys
 
 **Solution:**
 
-1. Generate an API key from [Settings > API Keys](https://www.runpod.io/console/user/settings) in the Runpod console. The key needs **All** access permissions.
+1. Generate an API key from [Settings > API Keys](https://console.runpod.io/user/settings) in the Runpod console. The key needs **All** access permissions.
 
 2. Authenticate using one of these methods:
 
@@ -343,7 +343,7 @@ Endpoint URL not available - endpoint may not be deployed
 
 2. **For Flash apps**: Deploy the app first with `flash deploy`, then call the endpoint.
 
-3. **Check endpoint status**: View your endpoints in the [Serverless console](https://www.runpod.io/console/serverless).
+3. **Check endpoint status**: View your endpoints in the [Serverless console](https://console.runpod.io/serverless).
 
 ### Execution timeout
 
@@ -382,7 +382,7 @@ Failed to connect to endpoint [name] ([url])
 
 1. **Check internet connection**: Verify you have network access.
 2. **Retry**: Transient network issues often resolve on retry. Flash includes automatic retry logic.
-3. **Check endpoint status**: Verify the endpoint is running in the [Serverless console](https://www.runpod.io/console/serverless).
+3. **Check endpoint status**: Verify the endpoint is running in the [Serverless console](https://console.runpod.io/serverless).
 
 ### HTTP errors from endpoint
 
@@ -395,7 +395,7 @@ HTTP error from endpoint [name]: 500 - Internal Server Error
 
 **Solutions:**
 
-1. **Check logs**: View worker logs in the [Serverless console](https://www.runpod.io/console/serverless) for detailed error messages.
+1. **Check logs**: View worker logs in the [Serverless console](https://console.runpod.io/serverless) for detailed error messages.
 
 2. **Test locally**: Use `flash dev` to test your function locally before deploying.
 
@@ -519,7 +519,7 @@ Circuit breaker is open. Retry in [N] seconds
    gpu=GpuGroup.ANY
    ```
 
-3. **Check availability**: View GPU availability in the [Serverless console](https://www.runpod.io/console/serverless).
+3. **Check availability**: View GPU availability in the [Serverless console](https://console.runpod.io/serverless).
 
 4. **Contact support**: For guaranteed capacity, contact [Runpod support](https://www.runpod.io/contact).
 

flash/windows-wsl2.mdx

@@ -10,7 +10,7 @@ Flash runs natively on macOS and Linux. On Windows, you can run Flash through Wi
 
 - Windows 10 version 2004 or later, or Windows 11.
 - Administrator access to your Windows machine.
-- [Runpod account](/get-started/manage-accounts) with a verified email address.
+- [Runpod account](/accounts-billing/manage-accounts) with a verified email address.
 - [An API key](/get-started/api-keys) with **All** access permissions.
 
 ## Step 1: Enable WSL2

get-started.mdx

@@ -341,7 +341,7 @@ runpodctl pod delete $RUNPOD_POD_ID
   <Card title="Generate API keys" href="/get-started/api-keys" icon="key" horizontal>
     Create API keys for programmatic resource management.
   </Card>
-  <Card title="Manage your account" href="/get-started/manage-accounts" icon="users" horizontal>
+  <Card title="Manage your account" href="/accounts-billing/manage-accounts" icon="users" horizontal>
     Create teams and invite collaborators.
   </Card>
   <Card title="Choose the right Pod" href="/pods/choose-a-pod" icon="server" horizontal>

get-started/connect-to-runpod.mdx

@@ -29,7 +29,7 @@ The Runpod REST API allows you to programmatically manage and control compute re
 
 Runpod provides SDKs in Python, JavaScript, Go, and GraphQL to help you integrate Runpod services into your applications.
 
-[Explore the SDKs →](/sdks/python/overview)
+[Explore the SDKs →](/serverless/sdks)
 
 ## Command-line interface (CLI)
 

hub/publishing-guide.mdx

@@ -4,7 +4,7 @@ sidebarTitle: "Hub publishing guide"
 description: "Publish your repositories to the Runpod Hub."
 ---
 
-Learn how to publish your repositories to the [Runpod Hub](https://www.runpod.io/console/hub), including how to configure your repository with the required `hub.json` and `tests.json` files.
+Learn how to publish your repositories to the [Runpod Hub](https://console.runpod.io/hub), including how to configure your repository with the required `hub.json` and `tests.json` files.
 
 After you publish your repository to the Hub, you can start [earning revenue](/hub/revenue-sharing) from your users' compute usage.
 

instant-clusters/slurm-clusters.mdx

@@ -92,4 +92,4 @@ If you encounter issues with your Slurm Cluster, try the following:
 - **Jobs stuck in pending state:** Check resource availability with `sinfo` and ensure requested resources are available. If you need more resources, you can add more nodes to your cluster.
 - **Authentication errors:** Munge is pre-configured, but if issues arise, verify the munge service is running on all nodes.
 
-For additional support, contact [Runpod support](https://contact.runpod.io/) with your cluster ID and specific error messages.
+For additional support, contact [Runpod support](https://contact.runpod.io/hc/en-us) with your cluster ID and specific error messages.

integrations/n8n-integration.mdx

@@ -28,7 +28,7 @@ In this tutorial, you'll learn how to:
 
 Before you begin, you'll need:
 
-* A [Runpod account](/get-started/manage-accounts) (with available credits).
+* A [Runpod account](/accounts-billing/manage-accounts) (with available credits).
 * A [Runpod API key](/get-started/api-keys).
 * An [n8n](https://n8n.io/) account.
 

pods/configuration/connect-to-ide.mdx

@@ -45,7 +45,7 @@ Before you can connect to a Pod, you'll need an SSH key that is paired with your
     ssh-ed25519 AAAAC4NzaC1lZDI1JTE5AAAAIGP+L8hnjIcBqUb8NRrDiC32FuJBvRA0m8jLShzgq6BQ YOUR_EMAIL@DOMAIN.COM
     ```
 
-3.  Copy and paste the output into the **SSH Public Keys** field in your [Runpod user account settings](https://www.runpod.io/console/user/settings).
+3.  Copy and paste the output into the **SSH Public Keys** field in your [Runpod user account settings](https://console.runpod.io/user/settings).
 
 <Warning>
 To enable SSH access, your public key must be present in the `~/.ssh/authorized_keys` file on your Pod. If you upload your public key to the settings page before your Pod starts, the system will automatically inject it into that file at startup.
@@ -76,7 +76,7 @@ Next, you'll configure SSH access to your Pod using the Remote-SSH extension. Th
 <Tabs>
 
   <Tab title="VSCode">
-   1. From the [Pods](https://www.runpod.io/console/pods) page, select the Pod you deployed.
+   1. From the [Pods](https://console.runpod.io/pods) page, select the Pod you deployed.
    2. Select **Connect**, then select the **SSH** tab.
    3. Copy the second command, under **SSH over exposed TCP**. It will look similar to this:
 
@@ -95,7 +95,7 @@ Next, you'll configure SSH access to your Pod using the Remote-SSH extension. Th
 
   <Tab title="Cursor">
 
-1. From the [Pods](https://www.runpod.io/console/pods) page, select the Pod you deployed.
+1. From the [Pods](https://console.runpod.io/pods) page, select the Pod you deployed.
 
 2. Select **Connect**.
 3. Under **Direct TCP Ports**, look for a line similar to:

pods/manage-pods.mdx

@@ -141,7 +141,7 @@ curl --request POST \
 
 ## Start a Pod
 
-Resume a stopped Pod. Note: You may be allocated [zero GPUs](/references/troubleshooting/zero-gpus) if capacity has changed.
+Resume a stopped Pod. Note: You may be allocated [zero GPUs](/pods/troubleshooting/zero-gpus) if capacity has changed.
 
 <Tabs>
 <Tab title="Web">
@@ -253,7 +253,7 @@ Access logs from the [Pods page](https://www.console.runpod.io/pods) by expandin
 
 | Issue | Solution |
 |-------|----------|
-| **Zero GPUs on restart** | See [Zero GPU Pods](/references/troubleshooting/zero-gpus) |
+| **Zero GPUs on restart** | See [Zero GPU Pods](/pods/troubleshooting/zero-gpus) |
 | **Pod stuck initializing** | Check logs for command errors; ensure you have an idle job (e.g., `sleep infinity`) if using SSH |
 | **Docker Compose not working** | Not supported. Use a [custom template](/pods/templates/overview) with your dependencies baked in. |
 

pods/storage/cloud-sync.mdx

@@ -52,7 +52,7 @@ Follow the steps below to sync your data with Amazon S3:
   </Step>
 
    <Step title="Sync your data with Runpod">
-    In the Runpod console, navigate to the [Pods page](https://runpod.io/console/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **AWS S3** from the available providers.
+    In the Runpod console, navigate to the [Pods page](https://console.runpod.io/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **AWS S3** from the available providers.
 
     Enter your **AWS Access Key ID** and **Secret Access Key** in the provided fields. Specify the **AWS Region** where your bucket is located and provide the complete bucket path where you want to store your data. 
 
@@ -82,7 +82,7 @@ Follow the steps below to sync your data with Google Cloud Storage:
   </Step>
 
   <Step title="Sync your data with Runpod">
-    In the Runpod console, navigate to the [Pods page](https://runpod.io/console/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **Google Cloud Storage** from the available providers.
+    In the Runpod console, navigate to the [Pods page](https://console.runpod.io/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **Google Cloud Storage** from the available providers.
 
     Paste the entire contents of your Service Account JSON key into the provided field. Specify the source/destination path within your bucket and select which folders from your Pod to transfer.
 
@@ -115,7 +115,7 @@ Follow the steps below to sync your data with Microsoft Azure Blob Storage:
   </Step>
 
   <Step title="Sync your data with Runpod">
-    In the Runpod console, navigate to the [Pods page](https://runpod.io/console/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **Azure Blob Storage** from the available providers.
+    In the Runpod console, navigate to the [Pods page](https://console.runpod.io/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **Azure Blob Storage** from the available providers.
 
     Enter your **Azure Account Name** and **Account Key** in the provided fields. Specify the source/destination path in your blob storage where you want to store your data.
 
@@ -143,7 +143,7 @@ Follow the steps below to sync your data with Backblaze B2 Cloud Storage:
   </Step>
 
   <Step title="Sync your data with Runpod">
-    In the Runpod console, navigate to the [Pods page](https://runpod.io/console/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **Backblaze B2** from the available providers.
+    In the Runpod console, navigate to the [Pods page](https://console.runpod.io/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **Backblaze B2** from the available providers.
 
     Enter your **Backblaze B2 Account ID**, **Application Key**, and **bucket path** as shown in the Backblaze interface.
 
@@ -176,7 +176,7 @@ Follow the steps below to sync your data with Dropbox:
   </Step>
 
   <Step title="Sync your data with Runpod">
-    In the Runpod console, navigate to the [Pods page](https://runpod.io/console/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **Dropbox** from the available providers.
+    In the Runpod console, navigate to the [Pods page](https://console.runpod.io/pods) and select the Pod containing your data. Click **Cloud Sync**, then select **Dropbox** from the available providers.
 
     Paste your **Dropbox Access Token** and specify the remote path where you want to store the data. Creating a dedicated folder in Dropbox beforehand helps with organization.