Target: 47 of 100 on Ora's agent-readiness scan

In short

Target scores 47 of 100 on Ora's agent-readiness scan, grade D, read on 18 November 2026. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. Every test agent gets in, and Ora found no MCP server or OpenAPI specification.

The score

Target is a general merchandise retailer based in Minneapolis.

  • 47of 100, grade D
    Ora's agent-readiness scan of target.com, read 18 November 2026, listed under E-commerce.
  • 7Discovery, of 10
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
  • 26.83Access, of 45
    Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
  • 12.83Usability, of 51
    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.

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

Ora's one-line summary: Turns agents away at the door: no MCP server, no OpenAPI spec, and no declared OAuth scopes.

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 target.com
CheckResultWhat Ora saw
Not blocked by bot detectionPass, 2 of 2Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
Agent crawler reachabilityPass, 1 of 1Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable
robots.txt AI crawler policyPass, 1 of 1AI 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 policyPass, 1 of 1No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://target.com/. Declared policy only;
Content without JavaScriptPartial, 3.33 of 5Homepage: 2774 chars with H1, but 1.9% content ratio is below the 5% target. No inner pages checked: the 5 sampled pages were skipped (forms, login pages, bot challenges, error pages).
Homepage not hidden from searchPass, 1 of 1No 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.

Reading target.com
CheckResultWhat Ora saw
llms.txt existsPass, 1 of 1Found the llms.txt at https://developer.target.com/llms.txt.
llms.txt formattingPass, 2 of 2The llms.txt is well-formatted: 64 lines with markdown links, 6,158 characters in total.
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 servingFail, 0 of 1No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly.
JSON-LD structured dataPartial, 0.5 of 2JSON-LD found (1 block(s)) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is
Organization schema completenessFail, 0 of 1No Organization type found in JSON-LD
Sitemap existsPass, 1 of 1Valid sitemap found at https://www.target.com/sitemap_keywords-index.xml.gz with multiple sitemaps entries
Metadata completenessPartial, 0.5 of 13/4 metadata signals present - missing: og:image
Page token budgetPass, 1 of 1All 6 measured pages fit an agent context budget (largest ~1K tokens)
Acting through target.com
CheckResultWhat Ora saw
MCP server / manifestFail, 0 of 10No MCP server or manifest found
MCP well-known discoveryFail, 0 of 2No MCP server URL discovered
Public API with reachable endpointsPartial, 3.43 of 8Documentation site found at https://developer.target.com but API content unclear. Best-of-protocols score: 3/7.
Public API/docs linked from homepagePass, 4 of 4Documentation site found at https://developer.target.com
OpenAPI spec publishedFail, 0 of 8No OpenAPI/Swagger specification found
Developer portalPass, 5 of 5Developer portal found at https://developer.target.com
OAuth 2.0 supportPartial, 2 of 5OAuth mentioned on homepage but no standard endpoints found
Scoped permissionsFail, 0 of 5No declared OAuth scopes, security schemes, or scoped-permission documentation found
CLI tool availableDid not apply, 0 of 3No CLI tool found
WebMCP supportPartial, 6.4 of 8Runtime-verified: 1 tool captured in a real browser session. Graded from a browser audit on 2026-11-17: 77/100 on the WebMCP rows below.
Finding Target
CheckResultWhat Ora saw
Brand name discoverabilityPartial, 1 of 3target.com ranks #9 for "Target" (searched your brand name alone: no main product term from your homepage qualified)
Developer resource discoverabilityPass, 4 of 4In a search for your API docs, your docs came up at #7 (https://plus.target.com/docs/spec/taxonomy)

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 8.7 points by Ora's estimate: No MCP server or manifest found.
  2. OpenAPI spec published, worth about 5.9 points by Ora's estimate: No OpenAPI/Swagger specification found.
  3. Brand name discoverability, worth about 4.4 points by Ora's estimate: target.com ranks #9 for "Target" (searched your brand name alone: no main product term from your homepage qualified).

Our read

Target's read turns on a store that lets every agent in and gives it little to do once inside. ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot all reached the site, robots.txt allows AI search crawlers in 3 of 3 checks, and a valid sitemap index is published. The home page shows 2,774 characters without JavaScript, thin against the markup around it, and its one JSON-LD block never says what kind of business this is. The developer site at developer.target.com publishes a 64-line llms.txt, and the site already exposes one WebMCP tool that Ora captured in a real browser session. The missing piece is the layer where agents act: Ora found neither an MCP server nor an OpenAPI specification, and OAuth is mentioned without standard endpoints. Ora also found no working way for an agent to pay, so payments were not scored. The fix worth most is an MCP server, about 8.7 points. A D at 47: the doors are open, and the checkout lanes are unstaffed.

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 target.com; a scan of a public site takes a few minutes and needs no account.

Sources

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

Last reviewed