---
title: "Stack Overflow agent readiness: the 360 check | Agent Ready Crawlers"
description: "Stack Overflow on Ora's agent-readiness scan, read 2026-11-09: 23 of 100, grade F. The door, what agents can read and do, the fixes worth most."
canonical: https://agentreadycrawlers.com/blog/stackoverflow-agent-readiness
site: "Agent Ready Crawlers"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Stack Overflow agent readiness: the 360 check | Agent Ready Crawlers

> Stack Overflow on Ora's agent-readiness scan, read 2026-11-09: 23 of 100, grade F. The door, what agents can read and do, the fixes worth most.

Source: https://agentreadycrawlers.com/blog/stackoverflow-agent-readiness
Site: Agent Ready Crawlers
Last reviewed: 2026-11-09
Agent endpoints: https://agentreadycrawlers.com/llms.txt (index), https://agentreadycrawlers.com/openapi.json (API), https://agentreadycrawlers.com/mcp (MCP server), https://agentreadycrawlers.com/ask (search)
Access: https://agentreadycrawlers.com/auth.md (no key). Pricing: https://agentreadycrawlers.com/pricing.md (free).

360 check, 9 November 2026

# Stack Overflow: the 360 agent-readiness check

In short

Stack Overflow scores 23 of 100 on Ora's agent-readiness scan, an F, read 9 November 2026. At the door, agents blocked: ChatGPT-User, OAI-SearchBot, PerplexityBot. 3 of 67 applicable checks pass; the gap worth most is Public API with reachable endpoints. A 418 for robots.txt, a bot wall and a licensing strategy add up to an F.

Stack Overflow is the programmers' question site, licensed to OpenAI and Google since 2024. On 9 November 2026 its public site scored **23 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, an F. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. The check below walks through all 132 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: Stack Overflow offers developer resource discoverability and SDK packages, but lacks a publicly reachable API surface.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Discovery | Can agents find and recommend it | 9 of 13 | 69% |
| Access | Can agents read it | 1 of 51 | 2% |
| Usability | Can agents use it | 7 of 45 | 16% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade F | 23 of 100 | 23% |

**

3 checks pass, 13 are partial, 51 fail and 65 do not apply to this site. Every check is defined in [Ora's catalog](https://ora.ai/api/checks?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) (read 2026-11-05); the result for each one is in the groups below, with what Ora saw where it said.

## At the door

What the site answers when a request arrives with an agent’s user agent, and what robots.txt says to the crawlers in the Index. 5 checks in this group do not apply to this site and are left out.

Agents named in Ora's results, with their Index rows: [ChatGPT-User](https://agentreadycrawlers.com/crawlers/chatgpt-user/), [OAI-SearchBot](https://agentreadycrawlers.com/crawlers/oai-searchbot/), [Claude-User](https://agentreadycrawlers.com/crawlers/claude-user/), [PerplexityBot](https://agentreadycrawlers.com/crawlers/perplexitybot/).

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection | Fail | 0 of 2 | Agents blocked: ChatGPT-User, OAI-SearchBot, PerplexityBot |
| Agent crawler reachability | Fail | 0 of 2 | No agent we tested can reach the homepage - ChatGPT-User: challenged, OAI-SearchBot: challenged, Claude-User: blocked, PerplexityBot: blocked |
| Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them. 4 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript | Partial | 0 of 3 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Sitemap exists | Fail | 0 of 2 | No sitemap found |
| llms.txt exists | Fail | 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting | Fail | 0 of 2 | No llms.txt found to evaluate quality |
| Markdown agent docs | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| Markdown URL fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://stackoverflow.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Agent mode view | Fail | 0 of 2 | No agent mode view detected at ?mode=agent (optional) |
| JSON-LD structured data | Partial | 0 of 4 | Homepage blocked by WAF - cannot check structured data |
| Organization schema completeness | Partial | 0 of 2 | Homepage blocked by WAF - cannot check Organization schema |
| JSON-LD entity linking (sameAs) | Partial | 0 of 2 | Homepage blocked by WAF - cannot check entity linking |
| Schema type breadth | Partial | 0 of 2 | Homepage blocked by WAF - cannot check schema types |
| Metadata completeness | Partial | 0 of 2 | Homepage blocked by WAF - cannot check metadata |
| Agent instruction / when-to-use | Fail | 0 of 3 | No agent instruction file with when-to-use guidance found |

## What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, a command line. 2 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Public API with reachable endpoints | Fail | 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) |
| Public API/docs linked from homepage | Partial | 0 of 3 | Homepage blocked by WAF - cannot check for docs links |
| Developer portal | Fail | 0 of 6 | No developer portal found |
| OpenAPI spec published | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| MCP server / manifest | Partial | 5 of 6 | MCP server detected at https://mcp.stackoverflow.com; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery | Partial | 1 of 2 | MCP server at https://mcp.stackoverflow.com - list its server card, hosted on your own domain, in /.well-known/ai-catalog.json so MCP clients can discover it |
| A2A / agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support | Fail | 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| OAuth Protected Resource metadata (RFC 9728) | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| NLWeb /ask endpoint | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available | Fail | 0 of 3 | No CLI tool found |
| Multi-language SDK packages | Partial | 1 of 3 | SDK package found only in npm |
| JSON error responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability | Partial | 1 of 3 | stackoverflow.com ranks #9 for "stackoverflow" (searched your brand name alone: we could not read a product term from your site) |
| Wikipedia / Wikidata entity presence | Partial | 2 of 4 | Wikidata Q549037 (Stack Overflow) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Developer resource discoverability | Pass | 3 of 3 | Can an agent find your developer resources with the searches it would really run? We search for your API docs and expect your own docs page among the results, then for your MCP server, SDK or CLI and, when you have one, expect your own page for it. Pages on other sites, including other companies with a similar name, don't count, unless your homepage or llms.txt links that site's docs, or your homepage redirects to a parent company's site and the page's address names your product. GitHub repos count only in an org your site links to. |
| Listed in MCP registries | Fail | 0 of 1 | No bi-directionally verified MCP registry entry found. To pass, either publish the server from a package whose homepage, repository or maintainer email names your domain, get a verified Smithery listing with non-zero usage, |
| NPM/PyPI SDK package | Pass | 1 of 1 | An official SDK or CLI on NPM or PyPI gives agents and the developers steering them a ready-made way in, instead of hand-rolling every API call. |
| ChatGPT app listed | Pass | 2 of 2 | Listed in the ChatGPT app directory, where hundreds of millions of users can pull your product into a conversation by name. Upside-only: the directory is curated and gated, so absence never costs points. |
| Registry branding | Fail | 0 of 2 | No registry branding (name, icon, description) found |
| Listed on skills.sh | Fail | 0 of 1 | No official skills self-published on skills.sh (100 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |

## The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Stack Overflow, with what Ora observed. The wording of each fix is Ora's job; the links go to the check in its catalog.

Public API with reachable endpoints

Fail, 0 of 7, about 6.9 points to gain. Ora saw: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)

OAuth 2.0 support

Fail, 0 of 5, about 4.9 points to gain. Ora saw: No OAuth 2.0 or OpenID Connect support detected

Scoped permissions

Fail, 0 of 5, about 4.9 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found

WebMCP support

Fail, 0 of 5, about 4.9 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found

OpenAPI spec published

Fail, 0 of 7, about 4.6 points to gain. Ora saw: No OpenAPI/Swagger specification found

## Our read

Stack Overflow licensed its corpus to OpenAI and Google in 2024 and the public site answers everyone else with a teapot: requests for robots.txt returned HTTP 418, so Ora could not read the policy, while bot detection blocked or challenged every test agent and the home page stayed behind the wall. Behind it there is an MCP server at mcp.stackoverflow.com and an npm package, which account for the 7 Usability points; the API that developers have used for years was not reachable as a public surface on this read. There is no sitemap and no llms.txt at the root. The Wikidata item is verified while no Wikipedia page is tied to the domain, and stackoverflow.com ranks ninth for its own name. An F at 23 for the programmers' question site is the sum of a 418, a bot wall and a licensing strategy.

## Check your own door

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site, then compare the door with the [Block Rate Report](https://agentreadycrawlers.com/block-rates/) for sites of your rank and kind. Our [guide to testing whether agents can reach your site](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/) has the curl commands for a manual check, and the [robots.txt builder](https://agentreadycrawlers.com/robots-builder/) writes a policy file from the Index. Payments did not apply to this site; a site that sells would read that layer against the [vendors at the door](https://agentreadycrawlers.com/vendors/ranking/).

[Scan your own domain on Ora](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)

[All 360 checks](https://agentreadycrawlers.com/blog/). One company a day; corrections to [the corrections page](https://agentreadycrawlers.com/corrections/).

**

The check we recommend

[Ora](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) scans a public URL: 16 Discovery checks and 42 Access checks, read from its catalog on 2026-11-05. Its Journey sends a real agent to the site. [How to run it](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/).

**Limits.** Ora reads public URLs only, and what it records as blocked comes from its own network. It says the same scan run twice converges within a couple of points ([Ora's Deep Scan post](https://ora.ai/blog/introducing-deep-scan?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)), and the pages we read give no repeat-scan figures. Its fixing product is behind a waitlist ([Ora's home page](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)).

## Sources

-   [Ora's scan of stackoverflow.com, GET /api/score (vendor)](https://ora.ai/api/score/stackoverflow.com?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-09
-   [Ora's check catalog, GET /api/checks (vendor)](https://ora.ai/api/checks?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05
-   [Stack Overflow home page](https://stackoverflow.com/questions) read 2026-11-09
-   [How to test whether AI agents can reach your site (this site)](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/) read 2026-11-04
-   [Ora: Deep Scan v2 (vendor)](https://ora.ai/blog/introducing-deep-scan?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05
-   [Ora home page, waitlist (vendor)](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05

Last reviewed 2026-11-09