Albertsons Companies: 25 of 100 on Ora's agent-readiness scan
In short
Albertsons Companies scores 25 of 100 on Ora's agent-readiness scan, grade F, read on 19 November 2026. 9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44. Agents reach the gate, a firewall challenge hides the home page, and three agent files break.
The score
Albertsons Companies is a supermarket group based in Boise, Idaho, the parent of Safeway and Vons.
- 25of 100, grade FOra's agent-readiness scan of albertsonscompanies.com, read 19 November 2026.
- 4Discovery, of 10Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 4.67Access, of 40Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 17.83Usability, of 66Whether 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.
9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44.
Ora's one-line summary: Blocks agents at the door: a WAF challenge stops them from reaching the homepage, and no OpenAPI spec or WebMCP support exists.
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 | Pass, 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability | Pass, 1 of 1 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy | Pass, 1 of 1 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. |
| robots.txt agent-user policy | Pass, 1 of 1 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://albertsonscompanies.com/. Declared policy only; |
| Content without JavaScript | Partial, 0 of 5 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage blocked by WAF - cannot read its indexing directives |
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 | Fail, 0 of 1 | No llms.txt found at https://albertsonscompanies.com/llms.txt. Publish it at the site root, where agents that follow the llms.txt spec look for it. |
| llms.txt formatting | Fail, 0 of 2 | No llms.txt found to evaluate quality |
| 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 | Site is behind a WAF/bot wall - cannot probe bot-UA serving |
| JSON-LD structured data | Partial, 0 of 2 | Homepage blocked by WAF - cannot check structured data |
| Organization schema completeness | Partial, 0 of 1 | Homepage blocked by WAF - cannot check Organization schema |
| Sitemap exists | Fail, 0 of 1 | No sitemap found |
| Metadata completeness | Partial, 0 of 1 | Homepage blocked by WAF - cannot check metadata |
| Page token budget | Did not apply, 0 of 1 | Nothing sampled to measure |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Partial, 3.33 of 10 | /.well-known/mcp/manifest.json serves an HTML page, not an MCP endpoint |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Pass, 8 of 8 | GraphQL endpoint at https://albertsonscompanies.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 homepage | Partial, 0 of 4 | Homepage blocked by WAF - cannot check for docs links |
| OpenAPI spec published | Fail, 0 of 8 | No OpenAPI/Swagger specification found |
| Developer portal | Fail, 0 of 5 | No developer portal found |
| OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://albertsonscompanies.com |
| Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| 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 | Pass, 3 of 3 | albertsonscompanies.com ranks #2 for "albertsonscompanies" (searched your brand name alone: we could not read a product term from your site) |
| Developer resource discoverability | Fail, 0 of 4 | In a search for your API docs, none of the 10 results is your official docs |
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.
- Developer resource discoverability, worth about 8.9 points by Ora's estimate: In a search for your API docs, none of the 10 results is your official docs.
- OpenAPI spec published, worth about 6.7 points by Ora's estimate: No OpenAPI/Swagger specification found.
- WebMCP support, worth about 5.4 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.
Our read
Albertsons Companies lets AI agents through the gate, and then a security challenge stops them at the home page. All four test agents reached the site, and robots.txt lets them in, yet the home page answered with a firewall challenge, so its text, structured data and metadata are unverified rather than failed. Beyond it, an agent finds little: neither a sitemap nor an llms.txt, and the Access layer reads about 4.7 of 40. Some files meant for agents are broken rather than missing: the agent-skills index and the agent card are not valid JSON, and the MCP manifest path serves an HTML page. A GraphQL endpoint answers behind authentication, but there is no OpenAPI specification or developer portal. The brand search ran on the bare string albertsonscompanies, which describes the probe. The fix worth most is API documentation an agent can find by search, about 8.9 points. An F at 25: the welcome mat is out, and the front desk checks every visitor's papers.
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 albertsonscompanies.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 albertsonscompanies.com (ora.ai/score/albertsonscompanies.com), read 19 Nov 2026. Vendor claim.
Last reviewed