agentspeed.

sourcegraph.com

scanned 7/25/2026, 11:41:17 PM · cached · refresh in 23h · rubric 2026.07.4
robots.txt present: passrobots.txt allows AI agents: passContent-Signal directives: failllms.txt present: warnSitemap present: passLink response headers: failCanonical URL: skipMCP server card: failOAuth authorization metadata: passOAuth resource metadata: passAPI catalog / OpenAPI: failWeb Bot Auth: failMarkdown negotiation: failText-to-markup ratio: failContent without JavaScript: skipHeading hierarchy: skipCookie wall blocks content: skipPage title: skipMeta description: skipJSON-LD present: failStructured data validates: skipSchema type coverage: passPaywall / login wall: skipAgent Skills manifest: failWebMCP actions: failPrimary action reachable: passReachability: passTime to first byte: passFull render time: skipPage weight: pass52/ 100 · F
At risk

This is how AI agents (not browsers) experience sourcegraph.com. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.

✉ Email me this report + alert me when it changes ↓

Top fixes

Checks tagged “emerging” are 2026 agent-protocol standards most of the web hasn’t adopted yet — adopting early is an edge, not a defect.

failJSON-LD presentStructured data

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

Fix: Add a <script type="application/ld+json"> describing the page (Organization, Article, Product, FAQPage).

warnllms.txt presentDiscoverability

Found /llms.txt but missing H1 header and markdown links.

Fix: Publish /llms.txt at your domain root. Build a spec-compliant one at /tools/llms-txt-generator.

failLink response headersDiscoverability

No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.

Fix: Emit `Link:` headers for canonical, alternate-language, and describedby relations. Agents that fetch HEAD-only or stream-render rely on these.

failText-to-markup ratioReadability

Visible text is 1.2% of HTML weight (7374/595846 bytes). Low. Markup may be crowding out agent-usable text.

Fix: Heavy ad or navigation markup crowds out agent-usable text. Aim for a text-to-DOM ratio above 15%.

failContent-Signal directivesemergingDiscoverability

No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.

Fix: Add `Content-Signal:` directives to your robots.txt. This is the emerging standard (Cloudflare-driven) for declaring fine-grained AI usage policy beyond a binary allow/disallow.

failMCP server cardemergingDiscoverability

No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.

Fix: Publish an MCP Server Card describing the tools your site exposes. Agents discover capabilities via `/.well-known/mcp/server-card.json`. See modelcontextprotocol.io for the schema.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever sourcegraph.com’s agent-readiness score changes. Free, unsubscribe anytime.

Fix it

Generated, ready-to-ship files for the gaps above — copy them or download and drop them into your repo.

Add an llms.txt
Publish this at https://sourcegraph.com/llms.txt
# Code Understanding, Oversight and Evolution | Sourcegraph

> Give humans and agents complete context to understand, oversee, and evolve the world

## Key pages
- [Home](https://sourcegraph.com/)
- [Take control of your codebase](https://sourcegraph.com/)
- [A tidal wave of code is coming. Code is growing faster than teams can understand or control it.](https://sourcegraph.com/)
- [Take back control with complete codebase context](https://sourcegraph.com/)
- [Stripe makes their fleet of internal AI agents more effective with the Sourcegraph MCP server](https://sourcegraph.com/)
- [Understand. Oversee. Evolve.](https://sourcegraph.com/)
- [Built for Big Code](https://sourcegraph.com/)

## About
Describe what sourcegraph.com does, who it's for, and the primary action you want an
agent to be able to complete. Keep it factual and current.

What the agent receives

The agent’s-eye view
Code Understanding, Oversight and Evolution | Sourcegraph Modern appsec at codebase scale on Aug 6 | Register now Platform Solutions Resources Pricing Schedule a demo Deep Search Agentic, natural language AI search Code Search Powerful search for complex codebases Agentic Batch Changes New AI agent for large scale code changes Insights High-level code metrics and analytics MCP Code graph knowledge for agents APIs Integrate with Sourcegraph CLI Sourcegraph in your terminal Code Migrations and Modernization Modernize and migrate codebases at scale Code security Security visibility and remediation at scale Code understanding Give every engineer complete codebase context Agent effectiveness Give AI coding agents the context to succeed Resources hub Guides, reports, and more Case studies Real-world results from our customers Events Conferences, webinars, and meetups Partners Cloud, technology, and channel partners Blog Product + engineering updates Changelog What's changed in Sourcegraph Documentation Get help using Sourcegraph Security Explore our security and compliance portal Public Code Search Search across 1M+ public repositories Take control of your codebase Give humans and agents complete context to understand, oversee, and evolve the world's largest, most complex codebases. Get a demo → Trusted by 200+ enterprise engineering teams 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 Updated Create and Update to persist the role Updated Create and Update to persist the role Added a GetByRole query method Added a GetByRole query method You'll want to add a migration for the new column and update your auth checks. What the agent missed Auth middleware — no role check, any user can access admin routes API response DTO — role never returned to clients Audit logging — role changes not tracked, no compliance trail /admin frontend routes — no guard, UI still accessible to all Invite flow — new users created without a default role 4 integration tests — assert on user shape, will break Coding Agent Agent + Sourcegraph MCP sg mcp sg_keyword_search "User struct" across 2,847 repositories Found 31 files referencing User across 7 layers models/user.go middleware/auth.go api/dto/user_response.go routes/admin/guard.ts +27 more files This is a cross-cutting change. Here's my plan: | This is a cross-cutting change. Here's my plan: Plan 8 steps 1. DB migration 2. Model 3. Auth middleware 4. API DTO 5. Audit logging 6. Invite flow 7. Frontend 8. Tests Edit 12 files across 7 layers Complete. All layers updated, tests passing. Full diff ready for review. | Complete. All layers updated, tests passing. Full diff ready for review. Nothing missed Auth middleware API response DTO Audit logging Frontend routes Invite flow Integration tests Stripe makes their fleet of internal AI agents more effective with the Sourcegraph MCP server Read more ↗ "Minions are connected to MCP… this is how they gather context: internal docs, ticket details, build statuses, and code intelligence via Sourcegraph search." — Alistair Gray, Stripe Sourcegraph Understand. Oversee. Evolve. The platform that gives you control of your codebase. Code understanding. Understand your codebase, completely. Agents are only as good as the context they receive. Sourcegraph gives them full codebase intelligence. Deep Search. Ask complex questions in natural language. Get grounded answers with citations. Used by engineering, support, and go-to market teams. How are versioned docs deployed to sourcegraph.com? Will Dollman, Security Engineer How do we handle database migrations and schema changes across services? Erik Seliger, Software Engineer What design tokens and color variables are used across our UI components? Taiyab Raja, Product Designer Is there a way to limit or allocate searches on an individual or team level for Deep Search? Ashley Singh, Account Executive MCP Server. Make every token count. Give agents complete, SCIP-powered context to produce reliable results with fewer retries and lower inference spend. Code Search. Search your entire codebase with exact, deterministic, and exhaustive results. Trusted by enterprise teams for over a decade. Code oversight. Keep up with what's changing. Understand system-wide impact before changes ship. Track patterns, monitor risk, and stay ahead of issues as code evolves. Code Insights. Track migrations, adoption, and risk across your codebase over time. Code Monitoring. Alert agents and teams when code changes. Living Documentation. A continuously updated knowledge base of your codebase. Codebase evolution. Execute changes safely and at scale. Making one change is easy. Making it everywhere, correctly, is not. New batch change › Onboarding Modernization Code health Security Run Agentic Batch Changes. AI agent for large-scale code changes. Migrate, modernize, and remediate across every repository with full control. Understanding Oversight Evolution Built for Big Code Trusted. Scalable. Enterprise-ready. SOC2 Type II + ISO27001 Compliance. Your code and data stay secure. Zero data retention. Your LLM inference is never stored beyond what's required and never shared with third parties. Built to scale. Handles the world's largest monorepos and multi-repo architectures. Enterprise authentication. SSO (SAML, OpenID Connect, OAuth), SCIM provisioning and lifecycle management, and RBAC for secure, centralized authentication. Dedicated support. Account Managers + Support Engineers provide dedicated help. Guide The Sourcegraph guide to surviving Big Code Discover 100 ways to understand, oversee, and evolve large codebases. This guide explores practical ways for navigating Big Code and keeping your team and agents in control. Download guide Take control of your codebase Understand it. Oversee it. Evolve it with confidence at Big Code scale. Get a demo → ✕ CodeScaleBench Report Learn how Sourcegraph makes agents faster, cheaper, and more accurate. Download → Code understanding for humans and agents Platform Deep Search Code Search MCP server Agentic Batch Changes Search public code Pricing Solutions Code Migrations and Modernization Code security Code understanding Agent effectiveness Resources Documentation Resource library Blog Changelog Case studies Partners Community Security portal Company About Careers Contact Handbook Brand Guide System status Terms of service Privacy policy Cookie preferences Do not sell

Show your score

Embed this badge on your site. It links back to this live scan and updates on every rescan.

AgentSpeed score for sourcegraph.com
<a href="https://agentspeed.com/scan/sourcegraph.com"><img src="https://agentspeed.com/badge/sourcegraph.com" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email, then a heads-up when sourcegraph.com’s agent-readiness actually changes — a check regressing, or the composite dropping.

Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.

Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.

Full breakdown

10 pass1 warn10 fail9 skip
Discoverability
pass
robots.txt present
A robots.txt is reachable at the site root.
100/100
pass
robots.txt allows AI agents
All 8 answer-time access agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
warn
llms.txt present
Found /llms.txt but missing H1 header and markdown links.
60/100
pass
Sitemap present
sitemap.xml reachable and referenced from robots.txt.
100/100
fail
Link response headers
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
0/100
skip
Canonical URL
Check could not run.
fail
MCP server cardemerging
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
0/100
pass
OAuth authorization metadataemerging
OAuth authorization-server metadata (RFC 8414) is published, so agents can discover authorization endpoints without out-of-band setup.
100/100
pass
OAuth resource metadataemerging
OAuth protected-resource metadata (RFC 9728) is published, so agents can discover required scopes and authorization servers programmatically.
100/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
Readability
fail
Markdown negotiationemerging
Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.
0/100
fail
Text-to-markup ratio
Visible text is 1.2% of HTML weight (7374/595846 bytes). Low. Markup may be crowding out agent-usable text.
9/100
skip
Content without JavaScript
Browser pass unavailable; cannot measure JS dependency.
skip
Heading hierarchy
Check could not run.
skip
Cookie wall blocks content
Check could not run.
skip
Page title
Check could not run.
skip
Meta description
Check could not run.
Structured data
fail
JSON-LD present
No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
0/100
skip
Structured data validates
No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).
pass
Schema type coverage
Page intent unclear; no specific schema.org type expected.
100/100
Actionability
skip
Paywall / login wall
Check could not run.
fail
Agent Skills manifestemerging
No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.
0/100
fail
WebMCP actionsemerging
No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.
0/100
pass
Primary action reachable
Primary offering identified ("AI-powered code understanding and codebase management platfo") with price/CTA ("Get a demo").
100/100
pass
Reachability
HTTP 200.
100/100
Performance
pass
Time to first byte
TTFB 133ms. Healthy.
100/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
pass
Page weight
Initial document is a lean 582 KB.
100/100
Beyond the scan

Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.

Start watching free →See plans