docs: Point internal links directly at moved-page destinations - #19636
Open
coolguyzone wants to merge 1 commit into
Open
coolguyzone wants to merge 1 commit into
coolguyzone wants to merge 1 commit into
Conversation
Update internal markdown links that currently hit a 3xx redirect so they point straight to the final destination, removing a redirect hop (saves latency and preserves link equity). Destinations were resolved against production (docs.sentry.io), since redirects.js is stale in places. Covers 22 links across 19 files for high-confidence 1:1 moves, e.g.: - /product/tracing/ -> /concepts/key-terms/tracing/ - /platforms/flutter/ -> /platforms/dart/guides/flutter/ - /platforms/javascript/apis/ -> /platforms/javascript/configuration/apis/ - /product/cli/ -> /cli/ - /integrations/launchdarkly/ -> /integrations/feature-flag/launchdarkly/ Scope: markdown and <Link> links only. Platform-relative <PlatformLink> links and pages that now collapse to a generic parent (the /data-management/* cluster) are deferred to follow-ups. redirects.js is left untouched so external inbound links keep working. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
coolguyzone
requested review from
sergical and
sfanahata
and removed request for
a team
September 25, 2026 21:29
6 tasks
KyleTryon
approved these changes
Sep 25, 2026
This branch was successfully deployed
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
2 participants
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.
DESCRIBE YOUR PR
In my continued quest to get all the low-hanging fruit to help SEO and site performance, this PR removes redirect hops on internal links by pointing them directly at the intended destination. This was created programmatically with Claude, but I've made sure the links still work as intended.
<Link>links across 19 files updated to their final URLsdocs.sentry.io), because this repo'sredirects.jsis stale in several spots (somedestinationfields now 404 or redirect again)…/trace-propagation/#what-is-distributed-tracing→…/distributed-tracing/#what-is-distributed-tracing)Examples:
/product/tracing/→/concepts/key-terms/tracing//platforms/flutter/→/platforms/dart/guides/flutter//platforms/javascript/apis/→/platforms/javascript/configuration/apis//product/cli/→/cli//integrations/launchdarkly/→/integrations/feature-flag/launchdarkly/Scope / deferred: markdown +
<Link>only. Platform-relative<PlatformLink>links need per-platform handling and are a separate PR. The/data-management/*cluster now collapses to the generic/concepts/data-management/parent (specific pages gone) and needs an SME decision.redirects.jsis intentionally left untouched so external inbound links keep working.Note: the crawler's "4,601 redirecting links" counts rendered instances; the authored source links are far fewer (~100 moved-page links + ~760 trailing-slash), which these follow-ups will cover.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: