Two public profiles · no score or winner
github.com and stackoverflow.com
Measured takeaway
Botfy does not have comparable evidence for a strong policy takeaway; the available states are shown below.
Measured in Botfy's 2026-09-07 publication.At a glance
A difference appears only when both sites have comparable evidence. Unavailable or unresolved observations remain incomplete.
| Evidence | github.com | stackoverflow.com |
|---|---|---|
| robots.txt | Served and parsed | Returned HTTP 403 |
| Google crawl posture | Open | Open |
| Unnamed crawler fallback | Partly Restricted they inherit the wildcard (*) group's rules | Unavailable |
| Base /llms.txt | Published | Not probed |
Treatment by purpose
Only resolved blocked, allowed, or mixed states count as a policy agreement or difference. Unnamed agents still inherit each site's wildcard rules.
| Declared purpose | github.com | stackoverflow.com |
|---|---|---|
| Model training | Not explicitly addressed | Observation unavailable |
| AI search | Not explicitly addressed | Observation unavailable |
| Live assistant fetch | Not explicitly addressed | Observation unavailable |
| Opt-out directives | Not explicitly addressed | Observation unavailable |
| Ambiguous / undocumented | Not explicitly addressed | Observation unavailable |
Named agents
Measured differences appear first. “Not explicitly addressed” is not the same as allowed; the site's wildcard fallback governs that crawler.
| Agent | github.com | stackoverflow.com |
|---|---|---|
| gptbot OpenAI | Not explicitly addressed | Observation unavailable |
| claudebot Anthropic | Not explicitly addressed | Observation unavailable |
| oai-searchbot OpenAI | Not explicitly addressed | Observation unavailable |
| perplexitybot Perplexity | Not explicitly addressed | Observation unavailable |
| chatgpt-user OpenAI | Not explicitly addressed | Observation unavailable |
| claude-user Anthropic | Not explicitly addressed | Observation unavailable |
How each site compares with its own rank peers
The sites may belong to different rank bands. Each percentage keeps its own population and denominator; Botfy does not subtract rates from unlike cohorts.
| Trait | github.com | stackoverflow.com |
|---|---|---|
| Wildcard group | Yes 95.1% Ranks 1–1,000 · n=529 | Parsing unavailable 95.1% Ranks 1–1,000 · n=529 |
| Effectively open file | No 11.3% Ranks 1–1,000 · n=529 | Parsing unavailable 11.3% Ranks 1–1,000 · n=529 |
| Sitemap declared | No 66.0% Ranks 1–1,000 · n=529 | Parsing unavailable 66.0% Ranks 1–1,000 · n=529 |
| robots.txt served | Yes 53.3% Ranks 1–1,000 · n=1,000 | No 53.3% Ranks 1–1,000 · n=1,000 |
| robots.txt returned 404 | No 4.6% Ranks 1–1,000 · n=1,000 | No 4.6% Ranks 1–1,000 · n=1,000 |
| Over the RFC parse limit | No 0.8% Ranks 1–1,000 · n=529 | Parsing unavailable 0.8% Ranks 1–1,000 · n=529 |
| Blanket disallow | No 8.9% Ranks 1–1,000 · n=529 | Parsing unavailable 8.9% Ranks 1–1,000 · n=529 |
How this comparison is measured
Both sites use Botfy's latest published observations. A missing fetch, unresolved agent verdict, and measured absence are different states. Peer percentages use each site's exclusive Tranco rank band and print their own denominator. Populations, sources, and limits →