Is homedepot.com agent ready?
homedepot.com is not yet agent ready: it scores 23/100 (grade F) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (0), Agent Protocols (6), Content Quality (18), Structured Data (24). Fixing Public API surface would add about 20 points.
What to fix first
- Public API surfaceNo public API surface detected+20 points if fixed
- /.well-known/agent-card.jsonNo /.well-known/agent-card.json found+6 points if fixed
- Schema.org JSON-LD present1/10 pages have JSON-LD structured data+4 points if fixed
- MCP endpointNo MCP endpoint found (tried homepage links, /mcp and mcp.<domain>)+3 points if fixed
- XML sitemap existsNo valid XML sitemap found+3 points if fixed
How homedepot.com compares
Better than 6% of measured sites
Among 1223 websites measured under rubric v3.1
Changed since last check
No change in score since the previous check (2026-11-15)
Category scores
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ~No error status codes8 page(s) returned errorspartial
- ✗XML sitemap existsNo valid XML sitemap foundfail
- ✗Edge treatment of agent user-agentsBlocked at the edge (agent-blocked): ChatGPT-User got HTTP 403 on https://www.homedepot.com, where our declared crawler got HTTP 200. Not probed: Claude-User.tracked, not scoredfail
- ✗Content negotiation (Markdown)No markdown served via Accept: text/markdown or .md URLs (checked homepage)fail
Passes: Response time, AI agent access, robots.txt exists
Not measured: Declared AI usage preferences (tracked, not scored)
Structured Data
- ~OpenGraph meta tagsMissing OpenGraph tags on some pagespartial
- ~Semantic HTML elementsLimited use of semantic HTML (<article>, <section>, <nav>, <main>)partial
- ~Appropriate Schema.org type1/10 pages use recognized Schema.org typespartial
- ✗Heading hierarchy0/10 pages have proper heading hierarchyfail
- ~Schema.org JSON-LD present1/10 pages have JSON-LD structured datapartial
- ~Schema.org completenessAverage field completeness: 14%partial
Passes: JSON-LD valid
Content Quality
- ~Answer-first contentSome pages lack early substantive content or meta descriptionspartial
- ~Content length2/10 pages have 200+ wordspartial
- ~Token efficiency (HTML-to-text ratio)Average text-to-HTML ratio: 5.6%partial
- ✗Freshness signals0/10 pages have date/freshness signalsfail
- ✗Author attribution0/10 pages have author attributionfail
- ~Citation readinessCitation readiness score: 15%partial
- ~Lists and tables for structured info2/10 pages use lists or tablespartial
Passes: FAQ content
Agent Discovery
- ✗llms.txt existsNo llms.txt found — coding agents and AI tools that read llms.txt have no curated index of your docsfail
- ✗Markdown alternate linksNo markdown alternate links foundfail
- ✗/.well-known/agent-card.jsonNo /.well-known/agent-card.json foundfail
Not measured: llms.txt follows spec, MCP server card (tracked, not scored), Agent Skills index (tracked, not scored), llms.txt links resolve
Agent Protocols
- ✗Discoverable API endpointsNo discoverable API endpoints (OpenAPI, GraphQL, etc.)fail
- ✗MCP endpointNo MCP endpoint found (tried homepage links, /mcp and mcp.<domain>)fail
- ✗Structured forms0/5 forms have proper labels and namesfail
- ✗Reachable as Google-AgentHomepage returned HTTP 403 to Google-Agentfail
- ✗Reachable as ChatGPT-UserHomepage returned HTTP 403 to ChatGPT-Userfail
- ✗Reachable as Perplexity-UserHomepage returned HTTP 403 to Perplexity-Userfail
Passes: Action schemas
Not measured: /.well-known/ucp, WebMCP imperative API (tracked, not scored), WebMCP declarative API (tracked, not scored)
Agent Auth
- ✗Public API surfaceNo public API surface detectedfail
Not measured: MCP authorization (401 challenge → protected resource metadata), PKCE S256 support, Client ID Metadata Documents (bonus), OpenAPI specification, Agent/bot auth documentation, OAuth discovery chain (RFC 9728 → RFC 8414), Developer portal, Scoped API permissions, API catalog (RFC 9727), Agent operator signing directory (tracked, not scored)
Technical
- ~Canonical URLs2/10 pages have canonical URLspartial
- ~Content accessible without JSOnly 2/10 pages have substantial content without JS renderingpartial
- ~Security headers2/4 security headers presentpartial
Passes: HTTPS, UTF-8 charset, Mobile viewport
Score history
- 23/100 · rubric v3.1
- 23/100 · rubric v3.1
- 23/100 · rubric v3.1
- 25/100 · rubric v3.0
- 14/100 · rubric v3.0
- 29/100 · rubric v2.0
- 29/100 · rubric v2.0
- 29/100 · rubric v2.0
- 29/100 · rubric v2.0
- 24/100 · rubric v2.0
- 24/100 · rubric v2.0
- 24/100 · rubric v2.0
- 25/100 · rubric v2.0
- 25/100 · rubric v2.0
- 24/100 · rubric v2.0
- 18/100 · rubric v2.0
- 18/100 · rubric v2.0
- 18/100 · rubric v2.0
Related websites
Share this score
Link
https://w2agent.dev/score/homedepot.com
Markdown
[](https://w2agent.dev/score/homedepot.com)
HTML
<a href="https://w2agent.dev/score/homedepot.com"><img src="https://w2agent.dev/api/score/homedepot.com/badge.svg" alt="w2agent AI Readiness score for homedepot.com" /></a>
IMG
https://w2agent.dev/api/score/homedepot.com/badge.svg