Skip to content

Add redirects for 18 legacy doc paths still returning 404#694

Open
danstotts-ops wants to merge 1 commit into
mainfrom
fix/gsc-404-redirects
Open

Add redirects for 18 legacy doc paths still returning 404#694
danstotts-ops wants to merge 1 commit into
mainfrom
fix/gsc-404-redirects

Conversation

@danstotts-ops

Copy link
Copy Markdown
Contributor

What

GSC's 'Not found (404)' validation on the runpod.io domain property failed (July 3 email); a chunk of the still-404 URLs are legacy docs paths from old structures: /graphql/*, /category/*, /docs/*, and pre-restructure serverless paths. Several carry external backlinks (/graphql/manage-pods has 11 referring pages).

Change

Adds 18 entries to the redirects array in docs.json, each mapped to the closest current page. All destination paths verified to exist (as .mdx or live 200). No content changes.

After this deploys, re-request validation in GSC for the 'Not found (404)' issue.

🤖 Generated with Claude Code

18 legacy paths from old docs structures (graphql/, category/, docs/ prefixes,
pre-restructure serverless paths) still return 404 and are failing the GSC
'Not found (404)' validation on the runpod.io domain property. Several carry
external backlinks (/graphql/manage-pods has 11). Map each to its closest
current page; all destinations verified to exist.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jul 7, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
runpod-docs 🟢 Ready View Preview Jul 7, 2026, 10:01 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant