seo: permanent redirects for retired URLs to current equivalents#950
seo: permanent redirects for retired URLs to current equivalents#950Jordy-Baby wants to merge 2 commits into
Conversation
Adds server-side 301 from the legacy /blog/what-is-a-blockchain-indexer-for-dapp-development URL (and its .md variant) to /blog/what-is-a-blockchain-indexer, the current maintained post. The legacy source was retired in #872 and the URL has been returning 404, so this recovers accumulated equity. Lightly updates the current post's intro and one H2 to capture the dApp development and Web3 developer angles the legacy URL ranked for. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
📝 WalkthroughWalkthroughThis PR clarifies the blockchain indexer blog post introduction to emphasize the transformation of onchain data into structured databases and refocuses the "Why" section heading toward dApp developers. Additionally, permanent URL redirects are configured in Vercel to handle blog slug migrations and documentation route namespace updates for HyperSync, HyperRPC, and HyperIndex products. ChangesBlog Post Content Update
Redirect Configuration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Recovers link equity from 4xx URLs flagged by MOZ. All new entries are permanent (308) redirects in vercel.json; matches the existing pattern. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@vercel.json`:
- Around line 41-50: The PR currently claims a "301 redirect" but the
vercel.json redirect entries (the objects with "source":
"/blog/what-is-a-blockchain-indexer-for-dapp-development" /
"/blog/what-is-a-blockchain-indexer-for-dapp-development.md" and "destination":
"/blog/what-is-a-blockchain-indexer" / "/blog/what-is-a-blockchain-indexer.md"
using "permanent": true) produce HTTP 308 responses; update the PR title and
description to state "308 Permanent Redirect" to match the implementation, or if
you truly require a 301 change the implementation to use Edge Middleware/a
custom response that issues a 301 instead of relying on vercel.json's
"permanent": true.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: dd79837d-7064-41c5-9bd0-addd4964acc8
📒 Files selected for processing (2)
blog/2025-01-21-what-is-a-blockchain-indexer.mdvercel.json
Summary
vercel.jsonfor a batch of legacy paths that were returning 404, recovering link equity to the current equivalents..mdroute variants.Test plan
vercel.jsonvalid JSON;yarn buildpasses.mdvariants redirect cleanly🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
Chores