agentspeed.

enterthetrenches.com

scanned 7/20/2026, 7:18:08 PM · fresh · rubric 2026.07.1
↻ Rescan
robots.txt present: passrobots.txt allows AI agents: passContent-Signal directives: failllms.txt present: warnSitemap present: failLink response headers: failCanonical URL: skipMCP server card: failOAuth authorization metadata: failOAuth resource metadata: failAPI 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: failReachability: passTime to first byte: passFull render time: skipPage weight: pass38/ 100 · F
Failing

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

Discoverability
30
Readability
11
Structured data
33
Actionability
33
Performance
100

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

Top fixes

failSitemap presentDiscoverability

No reachable sitemap.xml. Publish one and reference it in robots.txt.

Fix: Publish /sitemap.xml and reference it from robots.txt with a Sitemap: line.

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).

failPrimary action reachableActionability

Page text too sparse to probe; agent has nothing to read.

Fix: If agents cannot identify what you sell within 3 steps, your primary-offer page is under-structured. Add a visible headline, price (or "contact us"), and canonical CTA.

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 2.8% of HTML weight (97/3508 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%.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever enterthetrenches.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://enterthetrenches.com/llms.txt
# The Trenches — the crypto city in your browser

> An isometric crypto city MMO. Trade memecoins, wager 90-second duels, claim a house and build it into a mansion. Hold $TRENCHES (live on pump.fun) to play. Get rich or get rugged.

## Key pages
- [Home](https://enterthetrenches.com/)
- [Add your most important pages here](https://enterthetrenches.com/)

## About
Describe what enterthetrenches.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
The Trenches — the crypto city in your browser 🏛️ 0 GOLD TREASURY THE TRENCHES 🪙 0 GOLD

Show your score

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

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

Track this score

Get this report by email and a heads-up when enterthetrenches.com’s agent-readiness changes.

Full breakdown

6 pass1 warn14 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 9 known 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
fail
Sitemap present
No reachable sitemap.xml. Publish one and reference it in robots.txt.
0/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
fail
OAuth authorization metadataemerging
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
0/100
fail
OAuth resource metadataemerging
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
0/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 2.8% of HTML weight (97/3508 bytes). Low. Markup may be crowding out agent-usable text.
21/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
fail
Primary action reachable
Page text too sparse to probe; agent has nothing to read.
0/100
pass
Reachability
HTTP 200.
100/100
Performance
pass
Time to first byte
TTFB 101ms. Healthy.
100/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
—
pass
Page weight
Initial document is a lean 3 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