Recover high-authority backlinks to removed docs paths
Current verification on 2026-07-13 found ten old docs URLs still returning 404. The highest-value links come from Runpod-controlled GitHub and package surfaces, plus Hugging Face and other developer sources.
Required redirects
| Old path |
Recommended current target |
Current result |
/serverless-ai/custom-apis |
/serverless/workers/overview |
404 |
/docs/serverless-endpoint-urls |
/serverless/endpoints/operation-reference |
404 |
/docs/pods |
/pods/overview |
404 |
/docs/template-creation |
/pods/templates/create-custom-template |
404 |
/serverless-ai/custom-apis/using-your-api |
/serverless/endpoints/send-requests |
404 |
/docs/pod-env-variables |
/pods/templates/environment-variables |
404 |
/category/workers |
/serverless/workers/overview |
404 |
/docs/automatic-stop |
/pods/manage-pods |
404 |
/faq |
Docs owner to select the current support or help destination |
404 |
/docs/faq |
Same destination as /faq |
404 |
All recommended targets above return 200 today. The FAQ target needs an owner decision because the current sitemap has no direct FAQ replacement.
Update Runpod-controlled source links
Redirects are still required after the source updates because third-party copies and older package metadata continue to point at the removed paths.
Already recovered since the June audit
/category/storage now redirects to /storage/network-volumes
/docs/create-a-network-volume now redirects to /storage/network-volumes
/serverless/endpoints/manage-endpoints now redirects to /serverless/endpoints/endpoint-configurations
/graphql/manage-pods now redirects to /sdks/graphql/manage-pods
Acceptance criteria
- Each of the ten remaining old paths returns a permanent redirect to a live 200 page.
- The two Runpod-controlled README links are updated at source.
- The PyPI and Docker Hub descriptions are refreshed from the corrected README content.
- Redirect behavior is verified with a request that follows the full chain and ends in one hop where possible.
Recover high-authority backlinks to removed docs paths
Current verification on 2026-07-13 found ten old docs URLs still returning 404. The highest-value links come from Runpod-controlled GitHub and package surfaces, plus Hugging Face and other developer sources.
Required redirects
/serverless-ai/custom-apis/serverless/workers/overview/docs/serverless-endpoint-urls/serverless/endpoints/operation-reference/docs/pods/pods/overview/docs/template-creation/pods/templates/create-custom-template/serverless-ai/custom-apis/using-your-api/serverless/endpoints/send-requests/docs/pod-env-variables/pods/templates/environment-variables/category/workers/serverless/workers/overview/docs/automatic-stop/pods/manage-pods/faq/docs/faq/faqAll recommended targets above return 200 today. The FAQ target needs an owner decision because the current sitemap has no direct FAQ replacement.
Update Runpod-controlled source links
runpod/runpod-pythonREADME still links to/serverless-ai/custom-apis: https://github.com/runpod/runpod-python/blob/08e07cb5dded275b1bab0451940433fe2a1c8244/README.mdrunpodproject inherits the same README link.runpod-workers/worker-comfyuiREADME still links to/docs/serverless-endpoint-urls: https://github.com/runpod-workers/worker-comfyui/blob/066a11c49cfe6357902d1b2d8bc8d86bc55128b0/README.mdRedirects are still required after the source updates because third-party copies and older package metadata continue to point at the removed paths.
Already recovered since the June audit
/category/storagenow redirects to/storage/network-volumes/docs/create-a-network-volumenow redirects to/storage/network-volumes/serverless/endpoints/manage-endpointsnow redirects to/serverless/endpoints/endpoint-configurations/graphql/manage-podsnow redirects to/sdks/graphql/manage-podsAcceptance criteria