fix(seo): delete the retired Alchemy migration blog post - #1050
fix(seo): delete the retired Alchemy migration blog post#1050Jordy-Baby wants to merge 1 commit into
Conversation
The post was retired in #1038 and /blog/migrating-alchemy-subgraphs-to-envio now 301s to /docs/HyperIndex/migrate-from-alchemy via vercel.json. The markdown file was left in place, so Docusaurus kept emitting a sitemap entry for a URL that redirects. Google reads the sitemap as a list of canonical pages, crawls the blog URL, gets a 301 and files it under "Page with redirect". Same defect as /explorer in enviodev/ui#1212. The redirect stays. Only the source file goes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request deletes the blog post about migrating Alchemy subgraphs to Envio, including its metadata, migration guide, FAQs, instructions, and promotional links. Changes
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized change removes a retired blog post while preserving its redirect and related documentation entries; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. Comment |
What
Deletes
blog/2025-12-3-migrating-alchemy-subgraphs-to-envio.md. Nothing else.Why
The post was retired in #1038 and
vercel.json301s/blog/migrating-alchemy-subgraphs-to-envioto/docs/HyperIndex/migrate-from-alchemy. That redirect is correct and stays.The markdown file was never removed, so Docusaurus kept generating a sitemap entry for it. The sitemap is what we hand Google as our list of canonical pages, so Google crawls the blog URL because we asked it to, gets a 301, and files it under "Page with redirect".
Same defect as
/explorerin enviodev/ui#1212, which is what triggered the Search Console sitemap alert on 22 Aug. This one is queued to trigger the next one.Verification
docusaurus buildwithonBrokenLinks: "throw". Passed, so nothing links to the post./docs/HyperIndex/migrate-from-alchemyis still listed.validate-llms.jsgate. Passed, 0 warnings, 83 chain redirect targets checked, 0 broken..mdcopy.static/blog-posts-index.jsonregenerates fromblog/inprebuild, so it drops the entry automatically. Confirmed by running the generator, 80 posts to 79, 0 alchemy entries.Not included
static/blog-assets/migrating-alchemy-subgraphs.pngis now unreferenced. Left in place rather than sweeping unrelated cleanup into this PR.🤖 Generated with Claude Code
Summary by CodeRabbit