davidyurman.com 70 B
🛡️ SEO 54 🤖 GEO 86 ⚡ Perf 34 🏗️ Arch 99

davidyurman.com — Global SEODiff Score 70/100

davidyurman.com
📊

At 80/100, the ACRI for davidyurman.com indicates strong fundamentals in AI extractability, surpassing the majority of indexed sites. Within the infrastructure vertical, this places davidyurman.com above the industry average of 58 —, suggesting strong competitive positioning in AI search. Server-side rendering keeps the ghost ratio near zero, giving AI systems direct access to all visible content. A 6.6× bloat ratio is typical for sites in this tech tier — not wasteful, but streamlining could further boost extractability. Structured data coverage is solid at 3 blocks, covering core entities — expanding to include FAQ or Breadcrumb schemas could strengthen the profile further. The site maintains an open-door policy for AI crawlers — GPTBot, ClaudeBot, and other major agents are all allowed.

70
B — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (34) is your bottleneck.
🎯 Top Fix: Monitor weekly to catch regressions early
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
📈 ACRI Trend 16 snapshots
Feb 22 Feb 26
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than davidyurman.com?
Run the same 40-signal audit on your own domain — free, instant results.
Scan Your Site Free →
🧮 Score Transparency — How is this calculated?
🛡️ Traditional SEO (25% weight)54 × 0.25 = 13.5
🤖 AI Readiness / GEO (40% weight)86 × 0.40 = 34.4
⚡ Performance (20% weight)34 × 0.20 = 6.8
🏗️ Architecture & Trust (15% weight)99 × 0.15 = 14.8
Weighted sum = 13.5 + 34.4 + 6.8 + 14.8
Global SEODiff Score = 70 (B)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
62
Structure
avg 36
46
Schema
avg 9
55
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 4%
Rank #44404
Aligned
Gap
AI (ACRI)
Top 6%
Score 80/100

davidyurman.com has balanced Google and AI visibility — both rank roughly in the same tier. ACRI measures technical crawler readiness. Read the methodology →

Why davidyurman.com ranks here

Tech stackExpress
RenderingSSR
Schema coverage3 blocks
Token bloat6.6×

Fastest improvements

  • Reduce token bloat (navigation/footer/code) so agents reach your main content faster (see Token Bloat).
  • Create an llms.txt file 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 →
🧪

JavaScript Rendering Check

We check what AI crawlers miss when they skip JavaScript execution.

Running headless browser to simulate AI extraction…
🛡️

Traditional SEO

54/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

59 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

150 chars
Good length

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

  • ✗ Exactly 1 <h1> tag — found 0
  • ✓ Has <h2> headings — found 37
  • ✗ <h2> not before <h1>

🔍 Indexability

  • ✓ Canonical tag present → https://www.davidyurman.com/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → en-US
  • ✓ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — David Yurman | Designer Jewelry & Watches for Women and Men
  • ✓ og:description — Shop iconic collections, Cable bracelets, sculptural creations, and innovative ring and necklace designs from America's foremost luxury jewelry brand.
  • ✗ og:image
  • ✓ twitter:card — summary
📐 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

86/100 40 % of Global Score 🟢 High Confidence

This pillar aggregates citation share, hallucination risk, bot access, schema health, and content extractability. The individual diagnostic sections below contribute to this score.

🔗

Citation Alternatives

Research
💡
Insight: In the infrastructure sector, safely.co.jp (ACRI: 90) currently has stronger AI extractability. AI models tend to prefer sources with higher semantic structure and schema coverage. Domains with ACRI < 40 see 3.5× more hallucinations. Read the research →
davidyurman.com
71
Your ACRI Score
90
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. safely.co.jp has schema coverage of 3 blocks and uses WordPress. Improve your score by implementing the remediation patches below.
📊 Side-by-Side Comparison →
🚨

Hallucination Risk

Research

Is AI lying about your brand? This panel measures how likely LLMs are to hallucinate facts when extracting information from your page.

Analyzing hallucination risk…

🤖 Bot Access Matrix

GPTBot (OpenAI)
Allowed
ClaudeBot (Anthropic)
Allowed
CCBot (Common Crawl)
Allowed
Google-Extended
Allowed
Googlebot
Allowed

👻 Rendering (Ghost Ratio) Docs

Ghost Ratio 5%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type SSR

📊 Structure & Information Density Docs

Structure Grade 62/100 — Good
Structured Elements 202 elements (202 lists, 0 rows, 0 headers)
Total Words1745
Raw Density11.6%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks3 blocks

Schema Coverage Map

3/7 schema types detected
✅ Organization
❌ Product/Service
✅ Breadcrumb
❌ FAQ
❌ Article
✅ WebSite
💡Product / Service schema missing. AI models don't know this is a SaaS product. Add Product or SoftwareApplication schema so AI understands what you offer and can surface pricing/features.
💡FAQ schema missing. Adding FAQPage schema lets AI models directly extract Q&A pairs for Featured Snippets and chatbot answers.

📐 AI Efficiency Metrics Docs

70
AI Extractability
High
Crawl Cost
None
Blocklist Risk
Extractability70/100 — AI models can easily extract answers from this page
Crawl CostHigh (70/100) — expensive for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

15%
🗑️ 85%
Useful Content (85.4 KB)Bloat (477.3 KB)
Token Bloat Ratio6.6× — Normal

Multimodal Readiness

Visual Context96% Optimized for Vision
Image Alt Coverage75 / 78 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 84.8% · SNR: 0.18 · Signal: 21862 / Noise: 122191 tokens

🔬 AI-Crawler Simulation

See your website the way AI crawlers do. CSS stripped, structure labeled, content chunked.

🌐
This is what humans see — styled, branded, visual.
Toggle to "AI Agent View" to see what GPTBot, ClaudeBot, and other AI crawlers actually extract from this page.
🤖

AI Answer Preview

NEW

See how AI models summarize your site. Left: your actual content. Right: what the LLM extracts and says about you.

Simulating AI extraction…

🔧 Tech Stack

FrameworkExpress
AI-Readiness Score55/100
ServerDYF
CDN
HTTP Status200
Load Time1340 ms
Raw HTML Size562.7 KB
Visible Text Size85.4 KB

Performance & Speed

34/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1340 ms
Slow — bots may time out or deprioritise

Google considers <200 ms "good". AI crawlers may have even shorter timeouts.

📦 Page Weight

2766
DOM nodes
563 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → no-cache, no-store, must-revalidate
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

0
tracker scripts
0
third-party domains
0.0%
token overhead
Minimal tracker load — clean signal for bots
📐 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

99/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://www.davidyurman.com/sitemap_index.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

331
internal links
15
external links
Good internal linking — helps crawlers discover content

🔒 Security & Trust

  • ✓ HSTS header (Strict-Transport-Security)
  • ✓ Content-Security-Policy header
  • ✓ HTTP status 200 OK (got 200)

♿ Accessibility Signals

  • ✓ HTML lang attribute → en-US
  • ✓ 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 71/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

AI-Verified badge for davidyurman.com
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/davidyurman.com" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=davidyurman.com" 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.

🔗 Similar infrastructure Sites

Domains with a similar tech stack, industry, and AI readiness profile to davidyurman.com. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
davidyurman.com (this site) 71 80 Express 6.6× 3
tilibraexpress.com.br 87 87 Express 1.9× 3 Compare →
sandervunderink.nl 86 86 Express 2.2× 4 Compare →
sigmaflows.com 88 93 Express 2.3× 1 Compare →
jagoanchetslot.com 87 92 Express 6.5× 8 Compare →
sos-ricambi.it 86 94 Express 2.6× 13 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to davidyurman.com. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →

Add FAQ Schema
Medium Impact ⏱ 10 min
FAQ schema lets AI models directly extract Q&A pairs. This is the easiest way to get featured in AI responses.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Davidyurman?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Davidyurman does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Davidyurman work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Davidyurman."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for davidyurman.com:

Current Score
80
Projected Score
86
Improvement
+6 pts
Reduce token bloat +3 pts
Add FAQ schema +3 pts

*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 →

🧭 Self-Diffing (Private Layer)

For owned domains, combine this world snapshot with private drift + regression history.
Template Drift
Track in My Site
Drift → Traffic Impact
In development coming soon
Regression Incidents
Track in My Site
Internal Linking
Deep Audit graph
Semantic Structure
GEO view in Deep Audit
Content Quality
Thin/duplicate tracking

🕒 History

Score over timeAvailable in My Site history
Drift eventsTemplate timeline + incidents
Drift → Revenue AttributionComing soon
Schema/rendering/extractability changesTracked per scan in project history