Walgreens: 28 of 100 on Ora's agent-readiness scan

The score

Walgreens is a pharmacy chain based in Illinois.

• 28of 100, grade D
  Ora's agent-readiness scan of walgreens.com, read 9 November 2026.
• 10Discovery, of 11
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 0Access, of 41
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 7Usability, of 42
  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: Walgreens offers discoverable public APIs and endpoints, but lacks published OpenAPI specifications for agent integration.

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.

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.

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. MCP server / manifest, worth about 6.3 points by Ora's estimate: No MCP server or manifest found.
2. OpenAPI spec published, worth about 5.7 points by Ora's estimate: No OpenAPI/Swagger specification found.
3. WebMCP support, worth about 5.3 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.

Our read

Walgreens challenges every agent at the door and keeps one endpoint behind it. Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot, 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 41; there is no sitemap and no llms.txt. The act layer is a GraphQL endpoint at walgreens.com/graphql with introspection gated behind authentication, and nothing around it that an agent could use: no developer portal, no OpenAPI specification, and neither an MCP server nor OAuth discovery, so the Usability layer reads 7 of 42. The Discovery layer is nearly full at 10 of 11, with Wikipedia and Wikidata confirmed and walgreens.com first for walgreens. A pharmacy whose customers ask assistants whether a prescription is ready has a site those assistants cannot open; an MCP server is the fix Ora values most, at 6.3 points, and the challenge is the one that comes first.

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