/ Index
Sign in
Leaderboard›media

【楽天市場】Shopping is Entertainment! ： インター…

rakuten.co.jp
Claim this domain
Overall score
44.9Poor
▲ 5.4
Rank
#442
Prev: #470 · top 68% of 652 tracked
media rank
#77 of 84
Sector average 59.8
Benchmark runs
3
1 domain on the index claimed by owners

楽天市場はインターネット通販が楽しめる総合ショッピングモール。楽天ポイントがどんどん貯まる！使える！毎日お得なクーポンも。食品から家電、ファッション、ベビー用品、コスメまで、充実の品揃え。

Markets
JP
Locales
ja
Opportunity cost · media

【楽天市場】Shopping is Entertainment! ： インター… could see ~$5,620,200 of subscription & ad revenue exposed to agent-led journeys each year

Public agent-traffic forecasts suggest a growing share, modelled here at roughly 34%, of content discovery and subscription sessions in the media sector could be initiated or completed by AI agents[1][2]. 【楽天市場】Shopping is Entertainment! ： インター… currently scores 44.9 on the Index[3], roughly 5.1 points below the media peer average, leaving a 55-point gap to the ideal agent experience (100). The illustrative figure below applies that gap to the agent-driven slice of a typical annual subscription & ad revenue baseline for this sector. It is a directional estimate, not a measured conversion rate.

Gap to leader
55.1 pts
Below media avg
5.1 pts
Modelled revenue at risk
$5,620,200

Estimate assumes a $30M combined subscription and ad-revenue baseline. Claim your domain to replace this placeholder with your reported subscription & ad revenue.

Sources
  1. [1]Gartner (2025) — Intelligent Agents in AI Really Can Work Alone. Here’s How.
  2. [2]Adobe Analytics (2025) — Generative AI traffic to U.S. retail sites (weekly trend)
  3. [3]Stunt Double (2026) — Stunt Double Index methodology & scoring rubric

Category breakdown

Brand awarenessCan agents recognise you exist?
66
▲ 0.6
DiscoveryWill they pick you?
67
▲ 27.0
Information retrievalCan they read your site?
57
▼ 3.0
Market rankingWhere do you sit in the lineup?
26
▲ 11.1
AccuracyDo they tell the truth about you?
51
▼ 34.2
Task completionCan an agent complete a task on behalf of a user?
35
▲ 15.0
Delegated accessDo you let agents in, safely?
30
▲ 30.0
Contact & communicationCan an agent reach a human?
0

By agent provider

By agent provider
Session quality, 30-day rolling, N ≥ 10 per provider
ChatGPT Agent
OpenAI
0.0

Where agents get stuck

Public summary · full session replay available to verified owners
mediumBrand awareness
No Organization JSON-LD. Agents can’t tell who owns the site at a glance.
lowBrand awareness
Fewer than two social profiles linked. Agents struggle to triangulate the brand.
mediumDiscovery
No robots.txt. Agents fall back to defaults and may miss crawl hints.
mediumDiscovery
No sitemap.xml. Agents can’t enumerate indexable pages.
mediumInformation retrieval
Homepage responded in 5560ms. Slow for agent workflows.
mediumMarket ranking
No Product/Service schema on the homepage. Agents can’t easily compare offerings.
lowMarket ranking
No review or aggregateRating schema. Agents have no signal for ranking vs peers.
mediumMarket ranking
No price visible to non-JS clients. Agents may report "pricing not disclosed".
mediumAccuracy
No freshness headers. Agents can’t tell when content was updated.
mediumTask completion
No visible primary call-to-action in the server-rendered HTML. Agents have nothing concrete to click on behalf of a user.
highTask completion
No reachable entry point for delegated tasks: nothing at `/pricing`, `/signup`, `/cart`, `/book`, or similar responds without auth.
lowTask completion
No detectable agentic-commerce rail (Stripe SPT, Shopify/UCP, PayPal ACP). Agent-initiated payment needs custom work.
mediumTask completion
No mention of delegated auth primitives (passkey, OAuth, MCP). Agents must drive a full browser session.
highDelegated access
No discoverable MCP server. ChatGPT apps and Claude connectors have no scoped way to call your product; agents must drive a browser instead.
mediumDelegated access
No OAuth/OIDC discovery metadata. Agents cannot bootstrap a scoped, revocable session; any delegation falls back to password sharing.
highDelegated access
No public API docs detected. Agents have no scoped way in; they must drive a browser.
highContact & communication
No contact page linked or reachable. Agents acting on a user’s behalf have nowhere to send a message.
mediumContact & communication
No contact email visible in server-rendered HTML. Agents can’t fall back to email.
lowContact & communication
No help, support, or FAQ hub linked. Agents can’t self-serve an answer before reaching out.