chore: Add redirects for top docs 404s#3391
Draft
manovotny wants to merge 1 commit into
Draft
Conversation
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
SarahSoutoul
approved these changes
May 28, 2026
Contributor
SarahSoutoul
left a comment
There was a problem hiding this comment.
Not sure if this was ready for review as it's still in draft, but LGTM!
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.
🔎 Previews:
These urls/paths should redirect now:
What does this solve? What changed?
Investigated the top 5 docs 404s from the last 7 days and added redirects for the 2 that warranted action. The other 3 were AI/truncation noise with no canonical destination.
Investigation methodology
gh search codefor each URL to check for real referencesredirects/static/docs.jsondocs/guides/configure/auth-strategies/social-connections/) to confirm what provider docs existlint:check-duplicate-redirectsandlint:check-redirects— all checks passAnalysis of all 5 URLs
/docs/authentication/social-connections/enstallclerk_go:pkg/oauth/provider/enstall.go,clerk/dashboardprovider meta,clerk/javascriptruntime). The JS SDK ships this exact URL as thedocsUrlfor the provider inpackages/shared/src/oauth.tsandruntime-values.ts, so the 404 traffic is real users following the SDK's pointer. No docs page exists./docs/qui/docs/; almost certainly a truncated display of/docs/quickstart//docs/quickstarts/*. Both/docs/quickstartsand/docs/quickstartalready redirect to the right places. The bare truncated path is not a real URL./docs/authentication/social-connection-with-instagramsocial-connection-with-*URL pattern, but Instagram never had a docs page at that path (zero references in clerk org for this exact URL). Likely a model extrapolating from sibling providers (-with-facebook,-with-github, etc). The new-format URL (#5) is the one the SDK actually emits./docs/authentication/configuration/si/docs/authentication/configuration/sign-up-sign-in-options(often with a#social-connections-o-authfragment, as referenced fromclerk/clerk-androidand several blog posts). The full URL already resolves; the bare/siprefix is not a real URL./docs/authentication/social-connections/instagramclerk_go,clerk/javascript,clerk/dashboard,clerk-ios, andclerk-android. The JS SDK ships this exact URL as thedocsUrlinpackages/shared/src/oauth.tsandruntime-values.ts. No docs page exists.Changes
Static redirects (
redirects/static/docs.json):/docs/authentication/social-connections/enstall→/docs/guides/configure/auth-strategies/social-connections/overview/docs/authentication/social-connections/instagram→/docs/guides/configure/auth-strategies/social-connections/overviewDeadline
Other resources
clerk/javascript): TheenstallandinstagramdocsUrlentries inpackages/shared/src/oauth.tsandpackages/shared/src/types/runtime-values.tspoint to docs pages that don't exist. The fallback redirects in this PR send users to the social-connections overview, but the real fix is either (a) write per-provider docs for Instagram and Enstall underdocs/guides/configure/auth-strategies/social-connections/, or (b) drop/repoint thedocsUrlfield for these providers.