The Home Depot: 24 of 100 on Ora's agent-readiness scan

In short

The Home Depot scores 24 of 100 on Ora's agent-readiness scan, grade F, read on 9 November 2026. 9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44. Six agents challenged, with sign-in and an API endpoint waiting behind the wall.

The score

The Home Depot is a home improvement retailer based in Atlanta.

  • 24of 100, grade F
    Ora's agent-readiness scan of homedepot.com, read 9 November 2026, listed under E-commerce.
  • 5Discovery, of 8
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
  • 0Access, of 50
    Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
  • 13Usability, of 58
    Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
  • 0Payments, of 0
    No check in this layer applied to the site.

9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44.

Ora's one-line summary: Home Depot offers OAuth 2.0 support, but lacks an OpenAPI specification.

What an assistant meets at the door

Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.

The door at homedepot.com
CheckResultWhat Ora saw
Not blocked by bot detectionPartial, 0 of 2Bot management challenged GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended. A challenge is an identity check that verified crawlers pass.
Agent crawler reachabilityPartial, 0 of 2Bot management challenged ChatGPT-User, ClaudeBot, Google-Extended, ora-agent, DeepSeekBot - a challenge is an identity check verified crawlers pass.
robots.txt AI crawler policyDid not apply, 0 of 2Cannot verify robots.txt permission for training and search crawlers: WAF/bot challenge (HTTP 403)
robots.txt agent-user policyDid not apply, 0 of 2Cannot verify robots.txt permission for user-triggered agents: WAF/bot challenge (HTTP 403)
Content without JavaScriptPartial, 0 of 3Homepage blocked by WAF/security challenge - content not accessible to agents

What it can read, and what it can do

The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.

Reading homedepot.com
CheckResultWhat Ora saw
llms.txt existsFail, 0 of 1No llms.txt found at /llms.txt or /.well-known/llms.txt.
llms.txt formattingFail, 0 of 2No llms.txt found to evaluate quality
Markdown agent docsFail, 0 of 1Missing 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).
Bot-UA markdown servingDid not apply, 0 of 1Site is behind a WAF/bot wall - cannot probe bot-UA serving
JSON-LD structured dataPartial, 0 of 4Homepage blocked by WAF - cannot check structured data
Organization schema completenessPartial, 0 of 2Homepage blocked by WAF - cannot check Organization schema
Sitemap existsFail, 0 of 2No sitemap found
Metadata completenessPartial, 0 of 2Homepage blocked by WAF - cannot check metadata
Page token budgetDid not apply, 0 of 1Nothing sampled to measure
Acting through homedepot.com
CheckResultWhat Ora saw
MCP server / manifestFail, 0 of 6No MCP server or manifest found
MCP well-known discoveryFail, 0 of 2No MCP server URL discovered
Public API with reachable endpointsPass, 7 of 7GraphQL endpoint at https://api.homedepot.com/graphql is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7.
Public API/docs linked from homepagePartial, 0 of 3Homepage blocked by WAF - cannot check for docs links
OpenAPI spec publishedFail, 0 of 7No OpenAPI/Swagger specification found
Developer portalFail, 0 of 6No developer portal found
OAuth 2.0 supportPass, 5 of 5OpenID Connect discovery endpoint found at https://identity.homedepot.com
Scoped permissionsFail, 0 of 5No declared OAuth scopes, security schemes, or scoped-permission documentation found
Multi-language SDK packagesPartial, 1 of 3SDK package found only in npm
CLI tool availableFail, 0 of 3No CLI tool found
WebMCP supportFail, 0 of 5No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found
Finding The Home Depot
CheckResultWhat Ora saw
Wikipedia / Wikidata entity presenceFail, 0 of 4No Wikipedia article or Wikidata entity found for "homedepot" - creating a Wikipedia page and a Wikidata item with P856 = homedepot.com is the highest-impact step for AI search citation coverage
Brand name discoverabilityPass, 3 of 3homedepot.com ranks #1 for "homedepot" (searched your brand name alone: we could not read a product term from your site)
Category share of voiceDid not apply, 0 of 6Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name).
Developer resource discoverabilityPartial, 1 of 3Agent found 2 pages by name but no recognizable developer-resource type. Not found in this search sample: API docs, OpenAPI spec, developer portal, auth docs, MCP server, SDK documentation

The six payment checks did not apply on this read: Ora did not read the site as a shop.

Three fixes to hand to the web team

Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.

  1. Developer resource discoverability, worth about 5.6 points by Ora's estimate: Agent found 2 pages by name but no recognizable developer-resource type. Not found in this search sample: API docs, OpenAPI spec, developer portal, auth docs, MCP server, SDK documentation.
  2. OpenAPI spec published, worth about 4.7 points by Ora's estimate: No OpenAPI/Swagger specification found.
  3. MCP server / manifest, worth about 4.6 points by Ora's estimate: No MCP server or manifest found.

Our read

The Home Depot challenges six agents and leaves sign-in and an endpoint standing behind them. Bot management challenged GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended and Applebot-Extended, robots.txt answered with a 403 challenge and the home page came back as a security page, so the door, content, policy, structured-data and metadata rows are unverified rather than failed, and the Access layer reads 0 of 50; there is no sitemap and no llms.txt. The act layer has two real surfaces: a GraphQL endpoint at api.homedepot.com with introspection gated, and OpenID Connect discovery at identity.homedepot.com, with an SDK on npm beside them; there is no developer portal, no OpenAPI specification and no MCP server, so the Usability layer reads 13 of 58. The Discovery layer is 5 of 8: homedepot.com ranks first for homedepot, a search run on the bare name, and no Wikipedia article or Wikidata item points at the domain. A retailer whose customers ask assistants which drill to buy has a store they cannot open; the challenge decides the grade.

Test your own site

Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for homedepot.com; a scan of a public site takes a few minutes and needs no account.

Sources

  1. Ora report for homedepot.com (ora.ai/score/homedepot.com), read 9 Nov 2026. Vendor claim.

Last reviewed