Nike Scored 51 out of 100 on AI Agent Readiness. The World's Biggest Sportswear Brand Has a Blind Spot.

Nike spends billions on marketing. But when an AI agent tries to recommend running shoes, Nike is barely visible.

Nike is the most recognized sportswear brand on the planet. $51 billion in annual revenue. The swoosh is on every continent. But when we ran nike.com through the Pacestack AI Agent Readiness Scanner, Nike scored a 51 out of 100. Grade C.

That puts Nike 4th out of 25 fashion and apparel brands we scanned, behind Everlane (56), Fashion Nova (56), and Tory Burch (52). The industry average is 33.2. Nike is above average, but for a company of its size and technical resources, a C is a missed opportunity.

Here is exactly what we found, broken down by the three dimensions AI agents evaluate.

Structured Data: 15 out of 30

Nike has some of the basics right. The homepage includes JSON-LD structured data with Organization and WebSite schemas. That means AI agents can identify Nike as a brand and understand the site structure. OpenGraph tags are present (og:description, og:image, og:title, og:type, og:url), and the meta description is solid at 92 characters.

But here is where it breaks down:

• No Product Schema. Nike sells thousands of products, but none of the structured data tells AI agents what those products are, what they cost, or whether they are in stock. When someone asks Claude "what are the best running shoes under $150?" the agent has no structured Nike product data to work with.
• No BreadcrumbList. AI agents cannot navigate the site hierarchy. Is this the men's section? Running? Basketball? The breadcrumb trail that helps humans navigate is invisible to agents.
• No FAQ Schema. Nike has a Help section, but the questions and answers are not marked up in a way agents can parse and cite.

The gap here is stark. Nike has brand identity in its structured data (Organization schema), but zero product intelligence. An AI agent knows Nike exists. It does not know what Nike sells at what price.

AI Accessibility: 22 out of 25

This is Nike's strongest dimension. The site is technically well-built for agent access:

• robots.txt is open. No AI crawlers are blocked. GPTBot, ClaudeBot, PerplexityBot can all access the site.
• Content works without JavaScript. 7,104 characters of text are accessible without JS rendering. Not exceptional, but enough for agents to understand the page.
• Fast response time. 0.38s time-to-first-byte. Agents get content quickly.
• HTTPS, semantic HTML, viewport meta tag all pass.

The one failure: no sitemap.xml. Nike.com does not have a discoverable sitemap, which means AI agents and search crawlers have to find pages by following links rather than having a complete map of the site. For a site with thousands of product pages, that is a significant discovery gap.

MCP and Agent Readiness: 1 out of 20

This is the dimension where Nike scores almost nothing, and it matters the most for the future of AI commerce.

• No MCP server. No .well-known/mcp.json or AI plugin manifest. AI agents cannot interact with Nike's product catalog programmatically.
• No public API documentation. No OpenAPI spec, no Swagger docs. Agents have no way to query Nike's inventory.
• No product feeds. No RSS, Atom, or XML product feeds for agents to index.
• No Google UCP profile. When Google's AI Mode launches agent-assisted checkout, brands with UCP profiles will be first in line. Nike does not have one.
• No Agent Card or llms.txt. No agent discovery files at all.

The only point Nike earned was for platform detection (Magento). The platform supports agent integrations, but Nike has not enabled any of them.

What This Means for Nike

Nike's marketing engine is built for human attention: TV ads, athlete endorsements, social campaigns, immersive website experiences. That playbook has generated $51 billion in revenue. But AI shopping agents do not watch TV. They do not see swoosh logos. They read structured data, query APIs, and parse product feeds.

Right now, when someone asks an AI agent to recommend running shoes, the agent has to work from its training data and whatever it can scrape from nike.com. It knows Nike exists (Organization schema). It has no idea what the current Air Zoom Pegasus costs, whether it is in stock in size 10, or how it compares to the Brooks Ghost on price and cushioning. That data is not structured for agent consumption.

Meanwhile, Everlane (score: 56) and Fashion Nova (56) are doing a better job of agent-readable product data. Those are not bigger brands than Nike. They are just better at talking to machines.

The Competitive Picture

Here is how Nike compares to the 25 fashion and apparel brands we scanned:

• Industry leader: Everlane and Fashion Nova (tied at 56)
• Nike's rank: #4 of 25
• Industry average: 33.2
• Scoring zero: H&M, ASOS, Uniqlo, Lululemon, Revolve

Nike is in the top tier relative to fashion, but the entire industry is underperforming. No fashion brand in our scan has a Product Schema. None have MCP servers. None have product feeds. The bar is on the floor, and the first brand to clear it will have a structural advantage when AI agents control a significant portion of product discovery.

Three Fixes That Would Move Nike to a B

1. Add Product Schema to product pages (impact: +10 points). Each product page should include JSON-LD with name, description, price, priceCurrency, availability, image, brand, SKU, and aggregateRating. This is the single highest-leverage fix.
2. Add a sitemap.xml (impact: +3 points). A sitemap lets agents discover all product pages without crawling the entire site. For a catalog Nike's size, this is critical.
3. Add FAQ Schema to the Help section (impact: +3 points). Nike already has FAQ content. Marking it up as FAQPage schema makes it citable by agents.

Those three changes would move Nike from 51 to roughly 67, a solid B. Adding a MCP server and UCP profile on top of that could push Nike above 80.