Skip to content

Recover high-authority backlinks to removed docs paths #706

Description

@danstotts-ops

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions