---
title: "Glassdoor agent readiness: the 360 check | Agent Ready Crawlers"
description: "Glassdoor on Ora's agent-readiness scan, read 2026-11-09: 21 of 100, grade F. The door, what agents can read and do, the fixes worth most."
canonical: https://agentreadycrawlers.com/blog/glassdoor-agent-readiness
site: "Agent Ready Crawlers"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Glassdoor agent readiness: the 360 check | Agent Ready Crawlers

> Glassdoor on Ora's agent-readiness scan, read 2026-11-09: 21 of 100, grade F. The door, what agents can read and do, the fixes worth most.

Source: https://agentreadycrawlers.com/blog/glassdoor-agent-readiness
Site: Agent Ready Crawlers
Last reviewed: 2026-11-09
Agent endpoints: https://agentreadycrawlers.com/llms.txt (index), https://agentreadycrawlers.com/openapi.json (API), https://agentreadycrawlers.com/mcp (MCP server), https://agentreadycrawlers.com/ask (search)
Access: https://agentreadycrawlers.com/auth.md (no key). Pricing: https://agentreadycrawlers.com/pricing.md (free).

360 check, 9 November 2026

# Glassdoor: the 360 agent-readiness check

In short

Glassdoor scores 21 of 100 on Ora's agent-readiness scan, an F, read 9 November 2026. At the door, bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. 6 of 70 applicable checks pass; the gap worth most is Developer resource discoverability, about 4.8 points by Ora's estimate. A challenge page in front of a policy that welcomes agents.

Glassdoor is the employer review site, also owned by Recruit. On 9 November 2026 its public site scored **21 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, an F, in Ora's News & Intelligence category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. The check below walks through all 132 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: Glassdoor has a public API with reachable endpoints, but lacks an OpenAPI specification.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Discovery | Can agents find and recommend it | 9 of 14 | 64% |
| Access | Can agents read it | 2 of 52 | 4% |
| Usability | Can agents use it | 7 of 58 | 12% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade F | 21 of 100 | 21% |

**

6 checks pass, 9 are partial, 55 fail and 62 do not apply to this site. Every check is defined in [Ora's catalog](https://ora.ai/api/checks?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) (read 2026-11-05); the result for each one is in the groups below, with what Ora saw where it said.

## At the door

What the site answers when a request arrives with an agent’s user agent, and what robots.txt says to the crawlers in the Index. 3 checks in this group do not apply to this site and are left out.

Agents named in Ora's results, with their Index rows: [ChatGPT-User](https://agentreadycrawlers.com/crawlers/chatgpt-user/), [OAI-SearchBot](https://agentreadycrawlers.com/crawlers/oai-searchbot/), [Claude-User](https://agentreadycrawlers.com/crawlers/claude-user/), [PerplexityBot](https://agentreadycrawlers.com/crawlers/perplexitybot/), [Perplexity-User](https://agentreadycrawlers.com/crawlers/perplexity-user/).

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection | Partial | 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A challenge is an identity check that verified crawlers pass, |
| Agent crawler reachability | Partial | 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged, |
| robots.txt AI crawler policy | Pass | 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 0 of 2 checks (2 crawlers on 1 page), not scored. |
| robots.txt agent-user policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://glassdoor.com/. Declared policy only; |
| Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them. 4 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript | Partial | 0 of 3 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Sitemap exists | Fail | 0 of 2 | No sitemap found |
| llms.txt exists | Fail | 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| 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, |
| Markdown URL fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://glassdoor.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Agent mode view | Fail | 0 of 2 | No agent mode view detected at ?mode=agent (optional) |
| JSON-LD structured data | Partial | 0 of 4 | Homepage blocked by WAF - cannot check structured data |
| Organization schema completeness | Partial | 0 of 2 | Homepage blocked by WAF - cannot check Organization schema |
| JSON-LD entity linking (sameAs) | Partial | 0 of 2 | Homepage blocked by WAF - cannot check entity linking |
| Schema type breadth | Partial | 0 of 2 | Homepage blocked by WAF - cannot check schema types |
| Metadata completeness | Partial | 0 of 2 | Homepage blocked by WAF - cannot check metadata |
| Agent instruction / when-to-use | Fail | 0 of 3 | No agent instruction file with when-to-use guidance found |

## What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, a command line.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Public API with reachable endpoints | Pass | 7 of 7 | GraphQL endpoint at https://glassdoor.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 3 | Homepage blocked by WAF - cannot check for docs links |
| Developer portal | Fail | 0 of 6 | No developer portal found |
| OpenAPI spec published | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| MCP server / manifest | Fail | 0 of 6 | No MCP server or manifest found |
| MCP well-known discovery | Fail | 0 of 2 | No MCP server URL discovered |
| A2A / agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support | Fail | 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| OAuth Protected Resource metadata (RFC 9728) | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support | Fail | 0 of 5 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found |
| NLWeb /ask endpoint | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET) |
| CLI tool available | Fail | 0 of 3 | No CLI tool found |
| Multi-language SDK packages | Fail | 0 of 3 | No SDK packages found across language ecosystems |
| Rate limit response headers | Fail | 0 of 2 | GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages |
| Idempotency-Key support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| JSON error responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 2 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability | Pass | 3 of 3 | glassdoor.com ranks #2 for "glassdoor" (searched your brand name alone: we could not read a product term from your site) |
| Wikipedia / Wikidata entity presence | Pass | 4 of 4 | Wikipedia "Glassdoor" and Wikidata Q15954148 both verified - domain confirmed on both sources |
| Developer resource discoverability | Fail | 0 of 3 | Agent searched for "glassdoor" developer resources but found nothing relevant |
| NPM/PyPI SDK package | Fail | 0 of 1 | No NPM or PyPI SDK package found |
| ChatGPT app listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Listed on skills.sh | Fail | 0 of 1 | No official skills self-published on skills.sh (38 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json (and no legacy /.well-known/ai-catalog.json) |

## The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Glassdoor, with what Ora observed. The wording of each fix is Ora's job; the links go to the check in its catalog.

Developer resource discoverability

Fail, 0 of 3, about 4.8 points to gain. Ora saw: Agent searched for "glassdoor" developer resources but found nothing relevant

MCP server / manifest

Fail, 0 of 6, about 4.6 points to gain. Ora saw: No MCP server or manifest found

OpenAPI spec published

Fail, 0 of 7, about 4.5 points to gain. Ora saw: No OpenAPI/Swagger specification found

Developer portal

Fail, 0 of 6, about 3.8 points to gain. Ora saw: No developer portal found

OAuth 2.0 support

Fail, 0 of 5, about 3.8 points to gain. Ora saw: No OAuth 2.0 or OpenID Connect support detected

## Our read

Glassdoor, Indeed's stablemate under Recruit, posts the same pattern with a friendlier policy: robots.txt allows the AI search crawlers on three of three checks, refuses both training crawlers and places no restriction on the user-triggered agents, while bot management challenged all four of Ora's test agents and kept the home page behind the wall. Behind it a GraphQL endpoint at glassdoor.com/graphql answers but requires a key for introspection, and that is the only developer surface Ora found; the site has neither a portal nor an OpenAPI specification, neither an MCP server nor a sitemap, and no llms.txt. The Discovery layer is sound at 9 of 14, with Wikipedia and Wikidata confirming the domain and glassdoor.com second for its own name. An F at 21 for the employer review site is a challenge page standing in front of a policy that says come in.

## Check your own door

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site, then compare the door with the [Block Rate Report](https://agentreadycrawlers.com/block-rates/) for sites of your rank and kind. Our [guide to testing whether agents can reach your site](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/) has the curl commands for a manual check, and the [robots.txt builder](https://agentreadycrawlers.com/robots-builder/) writes a policy file from the Index. Payments did not apply to this site; a site that sells would read that layer against the [vendors at the door](https://agentreadycrawlers.com/vendors/ranking/).

[Scan your own domain on Ora](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)

[All 360 checks](https://agentreadycrawlers.com/blog/). One company a day; corrections to [the corrections page](https://agentreadycrawlers.com/corrections/).

**

The check we recommend

[Ora](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) scans a public URL: 16 Discovery checks and 42 Access checks, read from its catalog on 2026-11-05. Its Journey sends a real agent to the site. [How to run it](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/).

**Limits.** Ora reads public URLs only, and what it records as blocked comes from its own network. It says the same scan run twice converges within a couple of points ([Ora's Deep Scan post](https://ora.ai/blog/introducing-deep-scan?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)), and the pages we read give no repeat-scan figures. Its fixing product is behind a waitlist ([Ora's home page](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)).

## Sources

-   [Ora's scan of glassdoor.com, GET /api/score (vendor)](https://ora.ai/api/score/glassdoor.com?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-09
-   [Ora's check catalog, GET /api/checks (vendor)](https://ora.ai/api/checks?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05
-   [Glassdoor home page](https://glassdoor.com/) read 2026-11-09
-   [How to test whether AI agents can reach your site (this site)](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/) read 2026-11-04
-   [Ora: Deep Scan v2 (vendor)](https://ora.ai/blog/introducing-deep-scan?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05
-   [Ora home page, waitlist (vendor)](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05

Last reviewed 2026-11-09