Serve current coding-agent leaders in crawlable homepage HTML - #25
Merged
Conversation
Put the checked Artificial Analysis configurations in server-rendered HTML on the homepage, loading fallback, and /data so Googlebot can read model names, harnesses, scores, and cost without the chart. Add a snapshot-derived analysis page for AA Index versus cost, linked from home, /data, and the sitemap. Co-authored-by: ben <0thernet@users.noreply.github.com>
The root loading state is chart-only again so /data and blog HTML do not repeat the homepage configuration table. Co-authored-by: ben <0thernet@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
0thernet
marked this pull request as ready for review
August 22, 2026 16:02
Serve the product H1, a retrievedAt-dated leaders heading, a short snapshot answer, and the shared leaders table before the chart so no-JS crawlers do not see Loading chart as the first body. Co-authored-by: ben <0thernet@users.noreply.github.com>
cursor
Bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The homepage now answers the current coding-agent snapshot in the initial HTML. A no-JS Googlebot fetch sees the product H1, a retrievedAt-dated leaders heading, a short answer, and the shared leaders table before the chart.
Loading chart…is no longer the first meaningful body.What changed
/server-rendersHomeLeadersfirst: H1 “AI model and agent comparison charts”, H2Current leaders as of <retrievedAt>, two to four sentences from the checked snapshot, and an HTML table ofcurrentCodingAgentBenchmarkLeaders.CodingAgentExplorermounts after that block. The rootloading.tsxfallback was removed so the route does not replace the page with “Loading chart…”./datareuses the sameCodingAgentLeadersTableas the homepage. The full 59-row configuration table stays on/data.data/coding-agents.json. No benchmark numbers are authored by hand.Googlebot evidence
Local production server after
bun run check(175 tests and the production build). Fetched with:curl -sS -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" \ http://127.0.0.1:3000/HTTP 200. The first meaningful body is:
Then this HTML
<table>ofcurrentCodingAgentBenchmarkLeaders:Loading chart…still appears later as the explorerSuspensefallback. It is after the H1, answer, and table, not the first body content.