bitquery · buddies2705 · Jul 24, 2026 · Jul 24, 2026 · Jul 24, 2026 · Jul 24, 2026
diff --git a/.github/workflows/docs-build.yml b/.github/workflows/docs-build.yml
@@ -18,3 +18,5 @@ jobs:
           cache: npm
       - run: npm ci
       - run: npm run build
+      - name: Check internal links
+        run: node scripts/check-links.mjs
diff --git a/README.md b/README.md
@@ -54,4 +54,18 @@ npx docusaurus-prince-pdf -u http://localhost:3000/docs/intro
 
 ### Contributing to Docs
 
-Read contribution guidlines [here](https://docs.bitquery.io/docs/contribution-guidelines) 
+Read contribution guidlines [here](https://docs.bitquery.io/docs/contribution-guidelines)
+
+### Link checking
+
+```
+$ yarn build          # emit build/ so the checker can validate against real routes
+$ yarn check-links    # fails on broken internal links / dead URL schemes
+```
+
+`scripts/check-links.mjs` validates links against the routes Docusaurus actually emits (it reads `build/` when present), so it correctly resolves `slug:` front matter and extensionless relative links. It also runs in CI after the build.
+
+### Repo notes
+
+- `b5e8420ece5b4116b64bb3214828f286.txt` and `baidu_verify_codeva-*.html` are third-party search-engine site-verification files. Do not delete them.
+- The site is served in production by nginx (`nginx/default.conf`, `Dockerfile`), not Netlify. Redirects and 404 handling live in that nginx config.
diff --git a/blog/2023-02-21-started-doc.md b/blog/2023-02-21-started-doc.md
diff --git a/blog/2023-04-13-refactored-arguments-doc.md b/blog/2023-04-13-refactored-arguments-doc.md
diff --git a/blog/2023-05-18-added-conditional-metric-select-doc.md b/blog/2023-05-18-added-conditional-metric-select-doc.md
diff --git a/blog/2023-06-04-added-dex-trades-by-tokens-intervals-doc.md b/blog/2023-06-04-added-dex-trades-by-tokens-intervals-doc.md
diff --git a/blog/2023-06-30-added-arguments-events-array-filters.md b/blog/2023-06-30-added-arguments-events-array-filters.md
diff --git a/blog/2023-10-20-token-holders.md b/blog/2023-10-20-token-holders.md
diff --git a/blog/2024-02-05-array-intersect.md b/blog/2024-02-05-array-intersect.md
diff --git a/blog/2024-02-23-USDPrice.md b/blog/2024-02-23-USDPrice.md
diff --git a/blog/2024-05-27-solana-dex.md b/blog/2024-05-27-solana-dex.md
diff --git a/blog/authors.yml b/blog/authors.yml
diff --git a/docs/API-Blog/migrate-v1-v2.md b/docs/API-Blog/migrate-v1-v2.md
@@ -102,7 +102,7 @@ One of the major differences in v2 is how arguments and their values are handled
 
 Let's take this query in v1, where we get total number of unique currencies traded on Ethereum on a particular day. The `count` and `sum` aggregation is available in both v1 and v2.
 
-```
+```graphql
 query MyQuery {
   ethereum(network: ethereum) {
     dexTrades(date: {is: "2024-01-01"}) {
@@ -117,7 +117,7 @@ query MyQuery {
 - **Date Filtering**: Instead of a separate `date` field, v2 uses `Block.Date` for date filtering.
 - **Field Mapping**: The `buy_currency` and `sell_currency` fields in v1 are mapped to `Trade_Buy_Currency_SmartContract` and `Trade_Sell_Currency_SmartContract` respectively in v2.
 
-```
+```graphql
 query MyQuery {
   EVM(network: eth, dataset: combined) {
     DEXTrades(where: {Block: {Date: {is: "2024-01-01"}}}) {
@@ -139,7 +139,7 @@ To avoid this issue, in API v2, values are now represented as strings, allowing
 
 Let's take the below query which fetches the latest token details including USD values.
 
-```
+```graphql
 {
   ethereum(network: ethereum) {
     dexTrades(
@@ -195,7 +195,7 @@ There is no separate filter called `options`
 
 Next, we select the fields in the response
 
-```
+```graphql
 {
       Block {
         Number
@@ -254,4 +254,4 @@ To find your Bitquery API v1 key, log in to your [Bitquery account](https://acco
 
 ## V1 vs V2 : Data Points
 
-![](/img/v1v2.png)
+![Bitquery v1 to v2 API comparison](/img/v1v2.png)
diff --git a/docs/API-Blog/track-token-lock-unlock.md b/docs/API-Blog/track-token-lock-unlock.md
@@ -235,7 +235,7 @@ This subscription query tracks transactions that signal token unlocks, providing
 
 In any query if you are not sure about the event name or signature, use the `includes` filter to filter the events. In the below example, let's track latest token lock and unlock events on Optimism by using `includes: "locked"` filter for Log Signatures. You can run the query [here](https://ide.bitquery.io/Optimism-token-unlocked)
 
-```
+```graphql
 {
   EVM(dataset: archive, network: optimism) {
     Events(
-Original file line number
+Diff line change
@@ Expand Up @@
     In any query if you are not sure about the event name or signature, use the `includes` filter to filter the events. In the below example, let's track latest token lock and unlock events on Optimism by using `includes: "locked"` filter for Log Signatures. You can run the query [here](https://ide.bitquery.io/Optimism-token-unlocked)
-    ```
+    ```graphql
     {
       EVM(dataset: archive, network: optimism) {
         Events(
@@ Expand Down @@