Skip to content

fix(seo): delete the retired Alchemy migration blog post - #1050

Open
Jordy-Baby wants to merge 1 commit into
mainfrom
jords/remove-retired-alchemy-blog-post
Open

fix(seo): delete the retired Alchemy migration blog post#1050
Jordy-Baby wants to merge 1 commit into
mainfrom
jords/remove-retired-alchemy-blog-post

Conversation

@Jordy-Baby

@Jordy-Baby Jordy-Baby commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

What

Deletes blog/2025-12-3-migrating-alchemy-subgraphs-to-envio.md. Nothing else.

Why

The post was retired in #1038 and vercel.json 301s /blog/migrating-alchemy-subgraphs-to-envio to /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 /explorer in 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

  • Ran a full docusaurus build with onBrokenLinks: "throw". Passed, so nothing links to the post.
  • Built sitemap goes from 206 URLs to 205. The only URL removed is the blog post. /docs/HyperIndex/migrate-from-alchemy is still listed.
  • Ran the postbuild validate-llms.js gate. Passed, 0 warnings, 83 chain redirect targets checked, 0 broken.
  • Both redirect targets confirmed live at 200, the page and its .md copy.
  • static/blog-posts-index.json regenerates from blog/ in prebuild, 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.png is now unreferenced. Left in place rather than sweeping unrelated cleanup into this PR.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Removed the guide covering migration from Alchemy Subgraphs to Envio, including its FAQs, instructions, and related links.

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>
@vercel

vercel Bot commented Aug 26, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
envio-docs Ready Ready Preview Aug 26, 2026 8:31pm

Request Review

@Jordy-Baby
Jordy-Baby requested a review from keenbeen32 August 26, 2026 20:29
@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4c9748fb-d418-483b-896f-bf12b9145079

📥 Commits

Reviewing files that changed from the base of the PR and between c1c59b5 and fdd9095.

📒 Files selected for processing (1)
  • blog/2025-12-3-migrating-alchemy-subgraphs-to-envio.md
💤 Files with no reviewable changes (1)
  • blog/2025-12-3-migrating-alchemy-subgraphs-to-envio.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The pull request deletes the blog post about migrating Alchemy subgraphs to Envio, including its metadata, migration guide, FAQs, instructions, and promotional links.

Changes

Cohort / File(s) Summary
Blog content removal
blog/2025-12-3-migrating-alchemy-subgraphs-to-envio.md
Deletes the complete migration blog post.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to fdd90

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)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: deleting the retired Alchemy migration blog post to address SEO behavior.
Docstring Coverage ✅ Passed 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…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

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 @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant