Amazon.co.jp operates as a dominant e-commerce and digital services platform in Japan, offering a vast ecosystem encompassing retail, cloud computing (AWS), and digital content. Despite its global scale, the domain currently holds a Global SEODiff Score of 18, placing it significantly below benchmark performance, with an ACRI Grade of F and an ACRI Score of 11, indicating severe deficiencies in search visibility and technical SEO maturity. The site’s AI Readiness GEO Score of 15 reflects limited alignment with emerging AI-powered search expectations, while its extractability score of 29 suggests substantial challenges in content comprehension by search engines.
The site demonstrates notable technical performance in terms of payload size—2 KB of HTML and a TTFB of 1,368 ms—yet suffers from critical structural and content issues. The word count of just 26 and useful text bytes of only 182 reveal extreme content dilution, compounded by a ghost ratio of 75%, indicating that 75% of the site’s pages likely serve no meaningful purpose. The token bloat ratio of 11.0x further underscores excessive, non-semantic code, severely hampering crawl efficiency and content extraction. While the site uses a proprietary framework, it lacks essential SEO infrastructure: no structured data blocks, no declared sitemap, zero internal or external links, and no security headers (HSTS, CSP), all of which undermine trust and discoverability.
From an architectural standpoint, the site exhibits a Gini coefficient of 0—indicating total lack of link equity distribution—suggesting a fragmented, siloed structure with no semantic or navigational coherence. The absence of organization, product, article, FAQ, or breadcrumb schema eliminates rich result opportunities. With no AI bot access allowed and no AI-friendly meta tags, the site is effectively excluded from AI-powered search indexing. To improve, Amazon.co.jp must prioritize content integrity, eliminate ghost pages, implement structured data, rebuild internal linking, and ensure AI accessibility—transforming its architecture from a black box into a transparent, crawlable, and AI-ready platform.
🧮 Score Transparency — How is this calculated?
📊 ACRI Sub-Scores (AI Readiness Detail)
amazon.co.jp punches above its weight in AI — AI visibility exceeds Google ranking. This is a competitive moat worth protecting. ACRI measures technical crawler readiness. Read the methodology →
Why amazon.co.jp ranks here
Fastest improvements
- Allow GPTBot in robots.txt so AI crawlers can access your pages (see Crawl Access).
- Allow ClaudeBot (many assistants rely on it) — blocking it often correlates with “AI invisibility.”
- Add basic Organization and WebSite JSON-LD to fix “0 schema blocks” (see Schema Coverage).
- Reduce token bloat (navigation/footer/code) so agents reach your main content faster (see Token Bloat).
- Create an
llms.txtfile so AI crawlers can discover your content structure without heavy crawling. Generate llms.txt → - Run a full entropy audit to find which DOM regions waste the most tokens. Run Entropy Audit →
Traditional SEO
14/100 25 % of Global Score 🔴 Low Confidence📝 Title Tag
Optimal range: 30–60 characters for SERP display.
📋 Meta Description
Optimal range: 120–160 characters for snippet control.
🔤 Heading Hierarchy
- ✗ Exactly 1 <h1> tag — found 0
- ✗ Has <h2> headings — found 0
- ✓ <h2> not before <h1>
🔍 Indexability
- ✗ Canonical tag present
- ✓ No noindex directive
- ✓ Meta viewport set
- ✓ HTML lang attribute →
en - ➖ Hreflang tags — N/A (single language site)
- ✓ Googlebot allowed by robots.txt
🌐 Social / OpenGraph
- ✗ og:title
- ✗ og:description
- ✗ og:image
- ✗ twitter:card
📐 How the SEO Pillar score is calculated
SEO Pillar = Title (20 pts) + Meta Desc (20 pts) + Heading Hierarchy (20 pts) + Indexability (20 pts) + Social/OG (20 pts)
Each sub-score is derived from the checks above. Canonical tag, lang attribute, og:image, and a single H1 are the highest-impact items.
AI Readiness / GEO
15/100 40 % of Global Score 🟡 Medium ConfidenceThis pillar aggregates citation share, hallucination risk, bot access, schema health, and content extractability. The individual diagnostic sections below contribute to this score.
Is AI lying about your brand? This panel measures how likely LLMs are to hallucinate facts when extracting information from your page.
🤖 Bot Access Matrix
Allow: / under User-agent: GPTBot in your robots.txt.👻 Rendering (Ghost Ratio) Docs
📊 Structure & Information Density Docs
🏷️ Schema Health Docs
Schema Coverage Map
📐 AI Efficiency Metrics Docs
Token Bloat Research
Multimodal Readiness
TDM Rights
🔥 Structural Entropy Check Research
🔬 AI-Crawler Simulation
See your website the way AI crawlers do. CSS stripped, structure labeled, content chunked.
Toggle to "AI Agent View" to see what GPTBot, ClaudeBot, and other AI crawlers actually extract from this page.
AI Answer Preview
NEWSee how AI models summarize your site. Left: your actual content. Right: what the LLM extracts and says about you.
The LLM Interpretation
AI-VERIFIEDSEODiff AI analyzed the extracted content of amazon.co.jp and produced this structured business intelligence. Fields marked SEMANTIC VOID indicate information the AI could not find — a critical gap in your site’s machine-readability.
🔧 Tech Stack
Performance & Speed
80/100 20 % of Global Score 🟢 High Confidence⏱️ Time to First Byte
Google considers <200 ms "good". AI crawlers may have even shorter timeouts.
📦 Page Weight
DOM nodes
HTML payload
🗄️ Cache & CDN
- ✓ Cache-Control header →
no-store, max-age=0 - ✗ CDN cache status
- ✓ CDN detected → cloudfront
🔬 Tracker Tax
tracker scripts
third-party domains
token overhead
📐 How the Performance Pillar score is calculated
Perf Pillar = TTFB (35 pts) + Page Weight (25 pts) + Cache/CDN (20 pts) + Tracker Tax (20 pts)
TTFB <200 ms = full marks. DOM >3000 or payload >300 KB incurs heavy penalties. Tracker scripts beyond 5 reduce score.
Architecture & Trust
46/100 15 % of Global Score 🔴 Low Confidence🗺️ Sitemap & Robots
- ✗ Sitemap declared in robots.txt
- ✓ Googlebot allowed
- ✗ GPTBot allowed
- ✗ ClaudeBot allowed
🔗 Linking
internal links
external links
🔒 Security & Trust
- ✗ HSTS header (Strict-Transport-Security)
- ✗ Content-Security-Policy header
- ✗ HTTP status 200 OK (got 202)
♿ Accessibility Signals
- ✓ HTML lang attribute → en
- ✓ Meta viewport for mobile
- ✗ Single H1 for screen readers
📐 How the Architecture Pillar score is calculated
Arch Pillar = Sitemap & Robots (30 pts) + Linking (25 pts) + Security (25 pts) + Accessibility (20 pts)
Having a valid sitemap, allowing AI bots, HSTS, and a good internal link count are the highest-impact items.
🏅 AI-Verified Trust Badge
Your site scores 11/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.
<a href="https://seodiff.io/radar/domains/amazon.co.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=amazon.co.jp" alt="AI-Verified by SEODiff" width="280" height="52"></a>
💡 Paste in your site footer, GitHub README, or email signature. Badge updates automatically as your score changes.
� Deep Crawl Analysis 21 pages · Deep-10
| Page | Type | ACRI | Token Bloat | Words | Status |
|---|---|---|---|---|---|
| careers | 43 | 150.4× | 245 | ✓ | |
| pricing | 41 | 398.6× | 80 | 💰 Pricing | |
| trust | 27 | 12.7× | 22 | ✓ | |
| pricing | 22 | 71.8× | 6 | ✓ | |
| support | 22 | 71.8× | 6 | ✓ | |
| docs | 0 | 0.0× | 0 | ✓ | |
| blog | 0 | 0.0× | 0 | ✓ | |
| blog | 0 | 0.0× | 0 | ✓ | |
| about | 0 | 0.0× | 0 | ✓ | |
| product | 0 | 0.0× | 0 | ✓ | |
| product | 0 | 0.0× | 0 | ✓ | |
| product | 0 | 0.0× | 0 | ✓ | |
| docs | 0 | 0.0× | 0 | ✓ | |
| conversion | 0 | 0.0× | 0 | ✓ | |
| conversion | 0 | 0.0× | 0 | ✓ | |
| social-proof | 0 | 0.0× | 0 | ✓ | |
| support | 0 | 0.0× | 0 | ✓ | |
| support | 0 | 0.0× | 0 | ✓ | |
| support | 0 | 0.0× | 0 | ✓ | |
| integrations | 0 | 0.0× | 0 | ✓ |
| Path | Pages | Avg ACRI | Ghost % | Bloat | Top Issue |
|---|---|---|---|---|---|
| /trust/ | 1 | 27 | 0% | 12.7× | High JS Bloat |
| /guides/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /resources/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /support/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /api/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /terms/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /contact/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /faq/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /blog/ | 1 | 41 | 1% | 398.6× | Bot Blocked |
| /pricing/ | 1 | 22 | 0% | 71.8× | High JS Bloat |
| /help/ | 1 | 22 | 0% | 71.8× | High JS Bloat |
| /demo/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /solutions/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /products/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /features/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
Scores update automatically each month. Create a free account for on-demand re-crawls (3/month free).
🔌 API Access
Pull this data programmatically. All sub-page metrics are available via our public API.
curl https://seodiff.io/api/v1/deep10/domain/amazon.co.jpGet your free API key — 100 requests/month included.
🔗 Similar social Sites
Domains with a similar tech stack, industry, and AI readiness profile to amazon.co.jp. Compare side-by-side.
| Domain | ACRI | AI Score | Tech Stack | Token Bloat | Schema | |
|---|---|---|---|---|---|---|
| amazon.co.jp (this site) | 11 | 15 | Custom / Proprietary | 11.0× | 0 | — |
| kosmetista.ru | 36 | 66 | Custom / Proprietary | 6.0× | 1 | Compare → |
| audiokniga.one | 36 | 56 | Custom / Proprietary | 3.6× | 0 | Compare → |
| hedgescompany.com | 36 | 60 | Custom / Proprietary | 1.2× | 0 | Compare → |
| lagenceunique-occitanieculture.fr | 36 | 66 | WordPress | 11.2× | 0 | Compare → |
| timwhitlock.info | 36 | 69 | WordPress | 10.6× | 0 | Compare → |
📊 Semantic Share of Voice
How often would an AI cite amazon.co.jp when users ask about topics in this domain's niche? We run entity queries through our 188k-page search index and measure citation probability.
Analyzing citation landscape…
Bait & Switch Delta
D 3 PAGESCompares your homepage rendering quality with inner pages. A high drift score means AI crawlers see a polished homepage but degraded inner content — the "bait & switch" that erodes trust.
Worst Inner Pages
E-E-A-T Trust Signals
F 0/100Trust indicators extracted from surface pages. These signals help AI systems verify your site's Experience, Expertise, Authoritativeness, and Trustworthiness.
Citation Profile
22 DOMAINSOutbound citation patterns across surface-crawled pages. Sites that cite diverse, authoritative sources signal higher E-E-A-T to AI systems.
amazon-press.jp
amazon.science
affiliate.amazon.co.jp
advertising.amazon.co.jp
instagram.com
aboutamazon.jp
aws.amazon.com
amazon.jobs
AI trust scores for the domains amazon.co.jp links to. Citing high-trust sources lifts your own credibility signal.
Remediation Patches
COPY-PASTEAuto-generated code fixes tailored to amazon.co.jp. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Co",
"url": "https://amazon.co.jp",
"logo": "https://amazon.co.jp/logo.png",
"sameAs": []
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Co",
"url": "https://amazon.co.jp",
"potentialAction": {
"@type": "SearchAction",
"target": "https://amazon.co.jp/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
</script>
User-agent: GPTBot Allow: / User-agent: ChatGPT-User Allow: /
User-agent: ClaudeBot Allow: / User-agent: anthropic-ai Allow: /
<!-- Ensure main content is in the initial HTML response --> <main id="content"> <!-- Server-rendered content goes here --> <h1>Co</h1> <p>Your key content should render without JavaScript.</p> <!-- Move <script> tags to the bottom of <body> --> </main> <!-- In your framework config, enable SSR/prerendering: --> <!-- your framework -->
Projected Impact
ROI EST.If you apply the patches above, here's the estimated improvement for amazon.co.jp:
*Estimates based on SEODiff's scoring model. Actual results depend on implementation quality.
📋 Data Export
Download scores and metadata for audits, client reports, or CI/CD pipelines. Exports contain computed metrics only (no copyrighted content).
All data is generated automatically and updated with each crawl. JSON exports contain scores and metadata only (no copyrighted content).
Is this your company?
Monitor your AI visibility score weekly and get alerted when changes happen.
Start Free →