Skip to content

hotfix(seo): scope ton→gram redirect to benches with gram explainer - #750

Closed
Flotapponnier wants to merge 1 commit into
mainfrom
hotfix/scope-ton-gram-redirect
Closed

hotfix(seo): scope ton→gram redirect to benches with gram explainer#750
Flotapponnier wants to merge 1 commit into
mainfrom
hotfix/scope-ton-gram-redirect

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Problem

The catch-all redirect /benchmarks/:slug/ton → /benchmarks/:slug/gram fires for every bench, including ones with no gram per_chain_explainer. Example chain on prod:

```
curl -I https://openchainbench.com/benchmarks/aggregator-head-lag/ton
→ 308 /benchmarks/aggregator-head-lag/gram
→ 404
```

Ahrefs + Google flag this redirect-to-404 chain as a soft 404 anti-pattern.

Fix

Drop the catch-all, enumerate the 3 benches that actually have a gram (formerly ton) explainer:

  • l1-finality
  • network-fees
  • wallet-labels-coverage

For all other benches, /benchmarks/<slug>/ton will return a clean 404 (no redirect chain).

Test plan

  • After deploy: curl -I /benchmarks/aggregator-head-lag/ton returns 404, not 308
  • curl -I /benchmarks/l1-finality/ton still 308 → /gram (200)
  • curl -I /benchmarks/network-fees/ton still 308 → /gram (200)
  • curl -I /benchmarks/wallet-labels-coverage/ton still 308 → /gram (200)

The catch-all /benchmarks/:slug/ton redirect fired on every bench,
including aggregator-head-lag/gas-estimation/rpc-capabilities/etc that
have no per_chain_explainer for gram. Result: 308 chain into 404, which
Ahrefs + Google flag as a soft-404 anti-pattern.
Now explicit per-bench: l1-finality, network-fees, wallet-labels-coverage.
@Flotapponnier

Copy link
Copy Markdown
CollaboratorAuthor

Superseded by #753 (bundled SEO fixes to main)

@Flotapponnier
Flotapponnier deleted the hotfix/scope-ton-gram-redirect branch July 17, 2026 14:43
Sign up for freeto 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

@Flotapponnier