Can an AI agent compare delivery times for nearby restaurants?
Dimension Breakdown
Six-dimension scorecard
AI Discoverability74
Answer Engine Readiness75
Agent Usability100
Trust & Verification57
Content Worthiness81
Machine Readiness40
Key Strengths
What's working
robots.txt present
GET https://www.ubereats.com/robots.txt → HTTP 200, 2289 directive lines
Primary content structure
782 chars of visible text, <h1> present, <main>=yes
Primary CTA clarity
Detected action labels: ['add your restaurant', 'sign up to deliver', 'sign up', 'your restaurant, delivered add your rest', 'deliver with uber eats sign up to delive']
Business clarity on homepage
Title (69 chars); Meta description (182 chars); Clear H1
Structured data — Homepage
1 sampled homepage — schema found: website
Key Gaps
Biggest opportunities
Structured data — Location / store pages
Sampled 1 location / store pages; expected Localbusiness OR Restaurant OR Store OR Medicalorganization OR Dentist, found: no JSON-LD.
→ Add LocalBusiness schema on each location page with `address`, `geo` (lat/long), `telephone`, `openingHoursSpecification`, and `priceRange`. Target path pattern: /location/*.
Machine-readable capability discovery
Probed 18 endpoints — none returned a valid .well-known response.
→ If you expose APIs or developer capabilities, publish /.well-known/openid-configuration, /.well-known/mcp, or /.well-known/api-catalog as appropriate.
No x402, ACP, UCP, MPP, or related commerce-protocol signals found (probed /.well-known/{acp,ucp,mpp,x402,agent-commerce}.json)
→ If you sell products or services, evaluate x402 / ACP / UCP / MPP support and publish a capability document at `/.well-known/acp.json` (or equivalent) with your protocol version + supported actions.
→ Top improvements for this scan (highest impact, already quick to ship):
• Add Localbusiness or Restaurant or Store or Medicalorganization or Dentist on /location/* (Location / store pages) — impact +10, ease 3/5.
Contact accountability signals
No /contact URL found in nav or sitemap.
→ Publish a /contact page with email, phone, and physical address (or legal entity).
Suggested Improvements
Where to focus next
Structured data — Location / store pages — Add LocalBusiness schema on each location page with `address`, `geo` (lat/long), `telephone`, `openingHoursSpecification`, and `priceRange`. Target path pattern: /location/*.
Machine-readable capability discovery — If you expose APIs or developer capabilities, publish /.well-known/openid-configuration, /.well-known/mcp, or /.well-known/api-catalog as appropriate.
Emerging commerce protocol signals (x402, ACP, UCP, MPP) — If you sell products or services, evaluate x402 / ACP / UCP / MPP support and publish a capability document at `/.well-known/acp.json` (or equivalent) with your protocol version + supported actions.
Structured data / Schema.org coverage — Top improvements for this scan (highest impact, already quick to ship):
• Add Localbusiness or Restaurant or Store or Medicalorganization or Dentist on /location/* (Location / store pages) — impact +10, ease 3/5.
Contact accountability signals — Publish a /contact page with email, phone, and physical address (or legal entity).
Get a fresh Agent Readiness audit for your own site
Run a free scan now and see how your website compares to Uber Eats and the rest of the Index.