Ranked by what each change is worth on the composite — the gap to the next rung of the ladder times the dimension’s weight. Computed from the scores, not written by the model; the model’s sentence under each is the action.
Replace the headline with a concrete product noun that matches Sourcegraph’s codebase context offering, e.g., "Codebase Context Engine".
Add a measurable outcome tied to a product action,.
Use plain, concrete wording in the headline, avoiding abstract terms.
All three together: 56 → 67. Every dimension one rung up: 71 (grade B). Ceiling is 95.
Built only from facts already on the page — not the company’s words. Shown so the gap between what was written and what could have been written is concrete rather than a number.
Five alternative headlines in five angles, a subhead, a call-to-action line, and a line-by-line edit for each of the five dimensions — written only from facts already on sourcegraph.com, gated like a rating (anything with a struck word is dropped, not sold). Delivered on a private page in about a minute.
Five dimensions on one ladder — 5 · 20 · 35 · 50 · 65 · 80 · 95 — weighted clarity 30%, specificity 20%, jargon 20%, proof 15%, call to action 15%. For each: the rung the page matched, the words that drove it, and what would reach the next rung. Full rubric →
The headline does not name a concrete product category; it states abstract capabilities rather than a specific purchasable noun.
Code Understanding, Oversight and Evolution | Sourcegraph
Next rungReplace the headline with a concrete product noun that matches Sourcegraph’s codebase context offering, e.g., "Codebase Context Engine".
The page mentions an outcome-like benefit but contains no numeric outcome tied to a result.
Trusted by 200+ enterprise engineering teams
Next rungAdd a measurable outcome tied to a product action,.
Headline relies on abstract terms; page uses several buzzwords and tech-specific terms.
Code Understanding, Oversight and Evolution
Next rungUse plain, concrete wording in the headline, avoiding abstract terms.
Named customers/logos and a numeric stat provide verifiable proof.
Trusted by 200+ enterprise engineering teams
Next rungCite a specific customer with a metric or provide a public case study link.
There is a visible CTA to get a demo, which is a reasonable next step.
Get a demo →
Next rungMove the demo CTA near a clear, measurable product claim about codebase context benefits.
Code Understanding, Oversight and Evolution | SourcegraphMain headline lacking a concrete product noun.
Trusted by 200+ enterprise engineering teamsVisible proof of adoption with a numeric figure.
Get a demo →Primary CTA aligned with engaging users to learn more.
Code Understanding, Oversight and Evolution | Sourcegraph The context layer for your entire codebase Empower agents and developers to make faster decisions, improve AI-generated code, and execute code changes at scale. Get a demo → Now generally available Introducing Agentic Batch Changes The frontier agent for code changes at scale. Learn more → Trusted by 200+ enterprise engineering teams Reddit MathWorks Leidos Indeed Canva 1Password Dropbox HubSpot Stripe Blackstone Midjourney Mistral Guild Education The problem A tidal wave of code is coming. Code is growing faster than teams can understand or control it. Agents see only fragments of the enterprise codebase, rebuilding context for each task. As agent adoption grows, that blind spot becomes inconsistency, missed changes, and risk at scale. This is where engineering teams lose control. The solution Take back control with complete codebase context Sourcegraph indexes all of your repositories across the entire codebase, intelligently empowering agents with full context, driving improved outcomes. Execute the same task with dramatically different results. Coding Agent Agent Read models/user.go I'll add a Role field to the User struct and update the store methods. | I'll add a Role field to the User struct and update the store methods. Edit models/user.go — added Role string field Edit database/user_store.go — updated Create/Update Done! I've added: Done! I've added: Role field to the User struct Role field to the User struct
Strongest: Proof 80. Weakest: Clarity 20. The 5 passes agreed within 16 points. The band 48–64 is where a re-score of this unchanged page would most likely land: on 42 dry re-scores (12 Oct 2026) the median move was 6 points and one in four moved more than 10. A grade only changes when a new score clears the boundary by 5.
No word in the headline itself was judged empty, yet jargon-free scores 65: the scorer found generic phrasing further down the page. Headline relies on abstract terms; page uses several buzzwords and tech-specific terms.
Badges are issued to grades A and B. The share card for this page shows the headline with its jargon struck through; paste the URL anywhere that unfurls links.
Scored from the live homepage
on 2026-10-12 by gpt-5-nano,
5 independent passes, median taken.
Page snapshot 3247ca126002.
Rubric 7329c240 (current; what it says).
No person reviewed or edited this score. If the rubric and the score disagree, the rubric wins
and the page is re-scored — not hand-corrected.
Re-scored when the homepage text changes.