Redirect 30 URLs from the pre-2024 docs platform - #98
Merged
Conversation
The Search Console not-found report lists them, still crawled between 2026-03 and 2026-08. None ever existed as a file in this repo on any branch: main starts at 59d0b0f (2024-01-22), whose only page folders are kernel, kerneljs, meta-infra and recovery-flow. The old content is gone, so each target is the nearest current page by subject, not a verified 1:1 move. Reasons are recorded inline where the choice is not obvious. Leaves the 8 section roots and Cloudflare's /cdn-cgi endpoint 404.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two Search Console exports were checked against the redirect table: the "page with redirect" report (55 URLs) and the "not found" report (47 URLs).
The redirect report needed nothing
The not-found report had 39 uncovered URLs
8 of the 47 were already fixed. Every crawl date in the file is 2026-08-28 or earlier, and #95 deployed on 2026-09-01, so the report predates the fix.
30 come from the docs platform that predates this repo. This PR redirects them.
8 are section roots and stay 404 for now, deliberately (below).
1 is
/cdn-cgi/l/email-protection, Cloudflare's email-obfuscation endpoint. Never a page of ours.Where the 30 came from
/create-wallets/*(12),/use-wallets/*(10),/extend-wallets/*(2), plus/security,/production,/common-issues,/getting-started,/session-keysand/introduction/why-account-abstraction.None ever existed as a file in this repository, on any branch.
mainbegins at59d0b0f"Move docs over to this repo" (2024-01-22), a 59-file commit whose only page folders arekernel,kerneljs,meta-infraandrecovery-flow. Google has been retrying these since before the migration, with crawls as recent as 2026-08-26.The old content is not recoverable, so these targets are the nearest current page by subject, not verified 1:1 moves. That is a weaker basis than the rules in #95, where each target was checked against the deleted page's own content. Most are unambiguous from the URL alone:
/create-wallets/wallets-as-a-service/privy/onboarding/privy/create-wallets/custodial-wallet-apis/turnkey/onboarding/turnkey/use-wallets/batch-transactions/smart-accounts/batch-transactions/use-wallets/pay-gas-in-erc20/smart-accounts/pay-gas-with-erc20s/session-keys/smart-accounts/permissions/session-keysSix needed a judgement call, and each carries its reason inline:
/create-wallets/web2-auth/auth0goes to/onboarding/auth-providers. Auth0 has no page of its own, and that page is the hub for a service with no native integration; it points on to the EOA and custom-signer guides.web3modal,rainbowkit,custom-connect-wallet) all go to/onboarding/eoa. They are ways to connect an external EOA, which is exactly what that guide covers, and no page covers any of the three individually. This is the grouping exception in the map's standing rules, so the reason is recorded./use-wallets/transfer-all-assetsgoes to/smart-accounts/batch-transactions. Sweeping every asset out of an account is a batch of transfers./use-wallets/advanced/update-wallet-ownergoes to/advanced/account-recovery/sdk-recovery. Changing the owner is what the recovery flow does./productiongoes to/get-started/sdks/setup-project. Weakest of the set: an old "Production" page most likely covered project and key setup, but nothing survives to confirm it./introduction/why-account-abstractiongoes to/. The home page is the introduction, so this is the nearest equivalent rather than a fallback to the root./kernel/introalready resolves the same way.Verification
Against a local
npm run buildandnpm start, every URL in both reports:npm run check:redirects:383 redirects ok, 246 routes. That covers a dead target, a chain, a duplicate source, a rule shadowing a live page, and a target no sidebar links to.The 8 section roots are not in this PR
Those folders have no
index.mdx. Held back pending a decision on whether they should be redirects or real landing pages, since the two answers lead to different work.Our own navigation is not affected: the pillar bar links to specific pages, and
/walletsis the only pillar pointing at a section root, which returns 200 because it has an index page.