diff --git a/CHANGELOG.md b/CHANGELOG.md
index 61e03b69ba4..adca3aedddf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,9 @@
 
 # UNRELEASED
 
+## 👌 Improvements
+- docs: fix outdated link in documentation ([#13436](https://github.com/filecoin-project/lotus/pull/13436))
+
 # UNRELEASED v1.34.2
 
 See https://github.com/filecoin-project/lotus/blob/release/v1.34.2/CHANGELOG.md 
diff --git a/documentation/en/chain-indexer-overview-for-operators.md b/documentation/en/chain-indexer-overview-for-operators.md
index 42541da5e4c..078c266d44c 100644
--- a/documentation/en/chain-indexer-overview-for-operators.md
+++ b/documentation/en/chain-indexer-overview-for-operators.md
@@ -328,7 +328,7 @@ Note that this lack of an automated migration is primarily a concern for the rel
 
 ### `ChainValidateIndex` RPC API
 
-Please refer to the [Lotus API documentation](https://github.com/filecoin-project/lotus/blob/master/documentation/en/api-v1-unstable-methods.md) for detailed documentation of the `ChainValidateIndex` JSON RPC API.
+Please refer to the [Lotus API documentation](https://github.com/filecoin-project/lotus/blob/master/documentation/en/api-methods-v1-stable.md) for detailed documentation of the `ChainValidateIndex` JSON RPC API.
 
 The `ChainValidateIndex` JSON RPC API serves a dual purpose: it validates/diagnoses the integrity of the index at a specific epoch (i.e., it ensures consistency between indexed data and actual chain state), while also providing the option to backfill the `ChainIndexer` if it does not have data for the specified epoch.