Lowe's: 42 of 100 on Ora's agent-readiness scan
In short
Lowe's scores 42 of 100 on Ora's agent-readiness scan, grade D, read on 17 November 2026. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. Bot detection admits Claude-User only, and the home page shows 207 characters without JavaScript.
The score
Lowe's is a home improvement retailer based in Mooresville, North Carolina.
- 42of 100, grade DOra's agent-readiness scan of lowes.com, read 17 November 2026, listed under E-commerce.
- 6Discovery, of 10Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 13.67Access, of 25Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 9Usability, of 39Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
- 0Payments, of 0No check in this layer applied to the site.
43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44.
Ora's one-line summary: Bot detection turns agents away at the door, and the homepage shows only 207 characters of text without JavaScript.
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.
| Check | Result | What Ora saw |
|---|---|---|
| Not blocked by bot detection | Partial, 1 of 2 | Some agents blocked: ChatGPT-User, OAI-SearchBot, PerplexityBot. A normal browser visit from us got in. |
| Agent crawler reachability | Partial, 0 of 1 | Some agents are blocked - ChatGPT-User: blocked, OAI-SearchBot: blocked, Claude-User: reachable, PerplexityBot: blocked. A normal browser visit from us got in. |
| robots.txt AI crawler policy | Did not apply, 0 of 1 | Cannot verify robots.txt permission for search crawlers: WAF/bot challenge (HTTP 403) |
| robots.txt agent-user policy | Did not apply, 0 of 1 | Cannot verify robots.txt permission for user-triggered agents: WAF/bot challenge (HTTP 403) |
| Content without JavaScript | Partial, 1.67 of 5 | Homepage: Only 207 chars of text content - agents see limited content. No inner pages checked: the scan found none to sample. |
| Homepage not hidden from search | Pass, 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
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.
| Check | Result | What Ora saw |
|---|---|---|
| llms.txt exists | Did not apply, 0 of 1 | Can't verify: a bot shield answered our request to lowes.com/llms.txt (HTTP 403); lowes.com/.well-known/llms.txt (HTTP 403) instead of the site. That is not counted against the site. |
| llms.txt formatting | Did not apply, 0 of 2 | Can't verify: a bot shield answered our request to lowes.com/llms.txt (HTTP 403) instead of the site. That is not counted against the site. |
| Markdown agent docs | Fail, 0 of 1 | Missing 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 serving | Did not apply, 0 of 1 | Can't verify: a bot shield answered our request to lowes.com/ (HTTP 403) instead of the site. That is not counted against the site. |
| JSON-LD structured data | Fail, 0 of 2 | No JSON-LD structured data found on homepage |
| Organization schema completeness | Fail, 0 of 1 | No JSON-LD found - Organization schema missing |
| Sitemap exists | Fail, 0 of 1 | No sitemap found |
| Metadata completeness | Fail, 0 of 1 | No metadata signals found - missing: canonical URL, HTML lang attribute, og:image, og:type |
| Page token budget | Pass, 1 of 1 | All 1 measured page fit an agent context budget (largest ~1K tokens) |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Did not apply, 0 of 10 | Can't verify: a bot shield answered our request to lowes.com/.well-known/mcp/manifest.json (HTTP 403); lowes.com/.well-known/mcp.json (HTTP 403); lowes.com/mcp.json (HTTP 403), and 2 more instead of the site. |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Pass, 8 of 8 | API described in documentation at https://developer.lowes.com but no machine-verifiable API surface confirmed. GraphQL endpoint at https://api.lowes.com/graphql is reachable; |
| Public API/docs linked from homepage | Pass, 4 of 4 | Documentation site found at https://developer.lowes.com |
| OpenAPI spec published | Did not apply, 0 of 8 | Can't verify: a bot shield answered our request to lowes.com/api-docs (HTTP 403); lowes.com/openapi.json (HTTP 403); lowes.com/v3/api-docs (HTTP 403), and 4 more instead of the site. That is not counted against the site. |
| Developer portal | Pass, 5 of 5 | Developer documentation portal found at https://developer.lowes.com |
| OAuth 2.0 support | Did not apply, 0 of 5 | Can't verify: a bot shield answered our request to lowes.com/.well-known/openid-configuration (HTTP 403); lowes.com/.well-known/oauth-authorization-server (HTTP 403); |
| Scoped permissions | Did not apply, 0 of 5 | Can't verify: a bot shield answered our request to lowes.com/.well-known/oauth-protected-resource (HTTP 403) instead of the site. That is not counted against the site. |
| CLI tool available | Fail, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 8 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Brand name discoverability | Fail, 0 of 3 | lowes.com was not in the top 10 for "Access Denied" (searched your brand name alone: no main product term from your homepage qualified) |
| Developer resource discoverability | Pass, 4 of 4 | In a search for your API docs, your docs came up at #9 (https://developer.lowes.com/portal) |
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.
- WebMCP support, worth about 9.1 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.
- Brand name discoverability, worth about 6.7 points by Ora's estimate: lowes.com was not in the top 10 for "Access Denied" (searched your brand name alone: no main product term from your homepage qualified).
- MCP Apps support, worth about 4.6 points by Ora's estimate: No MCP Apps support detected - this product has an in-agent UI surface but exposes no ui:// resources or tool UI metadata for agents to render.
Our read
Lowe's read turns on a shield that sorts agents by name. Bot detection blocked ChatGPT-User, OAI-SearchBot and PerplexityBot while letting Claude-User and a normal browser in, and robots.txt answered with a 403 challenge, so its policy is unverified rather than failed. Behind the door there is little to read: the home page gives 207 characters of text without JavaScript, with no JSON-LD and none of the four metadata signals Ora looks for. The same shield answered the requests for llms.txt, an MCP manifest, an OpenAPI file and OAuth discovery, so those rows are unverified too. What Ora could confirm is a developer portal at developer.lowes.com, which ranked ninth in a search for the API docs. The brand search ran on the page title Access Denied, which describes the probe more than the retailer. The fix worth most is WebMCP, about 9.1 points. A D at 42: the store opens for one assistant in four, and the shelves are bare when it gets there.
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 lowes.com; a scan of a public site takes a few minutes and needs no account.
- Scan your domain on OraThe same checks, the same scoring, on your own site.
- The self-check, 18 questionsWhat to ask for, in business terms, before the scan.
- All the 360 checksThe other companies in this series, newest first.
Sources
- Ora report for lowes.com (ora.ai/score/lowes.com), read 17 Nov 2026. Vendor claim.
Last reviewed