Landing Page Architecture Analysis: Root Path Ownership
Note
Landing Page Architecture: Who Owns /?
The Three Options
A. Root = Agent-Optimized
/ → Structured, no CSS noise, ugly-but-parseable
/humans → Pretty marketing page
B. Root = Triage
/ → Minimal HTML: just links to /llm.txt and /humans
/llm.txt → Agent content
/humans → Human content
C. Root = Human-First + Convention
/ → Pretty landing page (but minimal)
/llm.txt → Agent content (emerging convention)
Key Insight: Who Arrives at /?
| Flow | Who lands at / | What they expect |
|---|---|---|
| VC clicks link | Human | "Show me what this is" |
| Dev types URL | Human | Could go either way |
| "Hey Claude, check out teamhive.ai" | Agent | Parseable info |
| Agent has MCP configured | Nobody | Uses MCP endpoint, never sees / |
Most agents using TeamHive will never see the landing page. The MCP server is their interface. The landing page is primarily for evaluation/discovery, usually human-initiated.
Why Triage Doesn't Work
Agents don't click links - they parse and request. A triage page just adds a hop without helping either audience. And "are you a robot?" is a weird first interaction for humans.
The /llm.txt Convention
Gaining traction (like robots.txt, humans.txt). Key insight: Convention > Innovation for discoverability. If everyone uses /llm.txt, agents learn to look there. Fighting convention costs us.
What "Agent-First" Means
Two interpretations:
- Agents Literally First - agents own
/, humans accommodated - Agents as First-Class Citizens - both designed for from start, neither afterthought
Leaning toward #2. Agent-first ≠ human-last.
Synthesis: Minimal Semantic HTML + /llm.txt
Root is so minimal it's almost agent-readable anyway:
- ~600 bytes, loads instantly
- Semantic HTML (agents parse it fine)
- Not ugly (minimal ≠ ugly)
- Points to
/llm.txtprominently - Uses
<link rel="alternate">semantically
Trade-offs of Radical Option (Agents at /)
Pros:
- Conversation starter ("our homepage is for AIs")
- Demonstrates philosophy, doesn't just claim it
- Filters for technical, agent-forward audience
- Bets on a future where agents browse more than humans
Cons:
- Bad first impressions for humans (VCs, curious visitors)
- Fights emerging
/llm.txtconvention - Agents don't actually need us to sacrifice humans
Next Step
Draft both versions to compare:
- What would
/look like if agent-first? - What would
/llm.txtlook like?