wislawjournal.com 45 D
🛡️ SEO 46 🤖 GEO 82 ⚡ Perf 47 🏗️ Arch 73

wislawjournal.com — Global SEODiff Score 45/100

wislawjournal.com
📊

AI crawlers face major barriers indexing wislawjournal.com, resulting in a low 15/100 ACRI rating that demands urgent attention. In the infrastructure sector, wislawjournal.com underperforms relative to the average (57), indicating room for competitive improvement. Content is delivered server-side, meaning bots and AI agents can parse the full page without executing JavaScript. Token bloat registers at 7.0× — acceptable, but reducing inline scripts and redundant markup could yield measurable gains. The site includes 3 schema blocks, providing adequate structured data for basic entity recognition. Complete AI crawler restriction cuts this domain off from the growing AI search ecosystem entirely.

45
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Traditional SEO (46) needs urgent attention.
🎯 Top Fix: Allow GPTBot + ClaudeBot in robots.txt → lift the score cap
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
Does your site score higher than wislawjournal.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)46 × 0.25 = 11.5
🤖 AI Readiness / GEO (40% weight)82 × 0.40 = 32.8
⚡ Performance (20% weight)47 × 0.20 = 9.4
🏗️ Architecture & Trust (15% weight)73 × 0.15 = 10.9
Weighted sum = 11.5 + 32.8 + 9.4 + 10.9
⚠️ Fatal multiplier: All major AI bots blocked → ×0.5
Global SEODiff Score = 45 (D)
🚫
Gatekeeper Rule: Score cannot exceed 15. Both GPTBot and ClaudeBot are blocked in robots.txt. No major AI assistant can cite this site. Allow at least one major AI crawler to lift the cap. See Bot Access →
📊 ACRI Sub-Scores (AI Readiness Detail)
20
Bot Access
avg 92
100
Rendering
avg 93
67
Structure
avg 35
46
Schema
avg 10
85
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #553154
+8 pts
Gap
AI (ACRI)
Top 63%
Score 15/100

wislawjournal.com shows stronger AI visibility than traditional SEO ranking. Great AI foundation to build on. ACRI measures technical crawler readiness. Read the methodology →

Why wislawjournal.com ranks here

Tech stackWordPress
RenderingSSR
Schema coverage3 blocks
Token bloat7.0×

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.”
  • 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

46/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

49 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

271 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

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

🌐 Social / OpenGraph

  • ✓ og:title — Wisconsin Law Journal - WI Legal News & Resources
  • ✓ og:description — A legal newspaper dedicated to providing court opinions, verdicts, settlements, appellate decisions, and legal news to give lawyers information essential to the practice of law in Wisconsin. Print and online subscriptions are available to attorneys / legal professionals.
  • ✓ og:image — preview
  • ✓ 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

82/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 →
wislawjournal.com
61
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)
Blocked
ClaudeBot (Anthropic)
Blocked
CCBot (Common Crawl)
Blocked
Google-Extended
Blocked
Googlebot
Allowed
💡GPTBot is blocked. To appear in ChatGPT citations, add Allow: / under User-agent: GPTBot in your robots.txt.
💡ClaudeBot is blocked. To be cited by Claude, allow ClaudeBot in robots.txt.

👻 Rendering (Ghost Ratio) Docs

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

📊 Structure & Information Density Docs

Structure Grade 67/100 — Good
Structured Elements 246 elements (246 lists, 0 rows, 0 headers)
Total Words1825
Raw Density13.5%

🏷️ 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

71
AI Extractability
Low
Crawl Cost
Critical
Blocklist Risk
Extractability71/100 — AI models can easily extract answers from this page
Crawl CostLow (30/100) — efficient for AI crawlers to process
Blocklist RiskCritical — 4 of 5 AI crawlers blocked

Token Bloat Research

14%
🗑️ 86%
Useful Content (27.1 KB)Bloat (163.1 KB)
Token Bloat Ratio7.0× — Normal

Multimodal Readiness

Visual Context20% Optimized for Vision
Image Alt Coverage7 / 35 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Only 20% of images have alt text. Add descriptive alt attributes so multimodal AI (ChatGPT Vision) can understand your images.

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 85.7% · SNR: 0.17 · Signal: 6947 / Noise: 41761 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

FrameworkWordPress
AI-Readiness Score85/100
Servercloudflare
CDNcloudflare
HTTP Status200
Load Time1130 ms
Raw HTML Size190.3 KB
Visible Text Size27.1 KB

Performance & Speed

47/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1130 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1375
DOM nodes
190 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✓ Cache-Control header → max-age=600, must-revalidate
  • ✓ CDN cache status → DYNAMIC
  • ✓ CDN detected → cloudflare

🔬 Tracker Tax

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

73/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✗ Sitemap declared in robots.txt
  • ✓ Googlebot allowed
  • ✗ GPTBot allowed
  • ✗ ClaudeBot allowed

🔗 Linking

222
internal links
71
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 61/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
wislawjournal.com (this site) 61 15 WordPress 7.0× 3
masslawyersweekly.com 61 15 WordPress 7.0× 3 Compare →
veevee.app 61 82 WordPress 7.1× 3 Compare →
maunaup.com 61 77 WordPress 6.9× 3 Compare →
chtoukapress.com 61 74 WordPress 7.1× 3 Compare →
mostbetaz-yukle.com 61 71 WordPress 7.2× 3 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

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

Allow GPTBot in robots.txt
High Impact ⏱ 2 min
GPTBot is blocked — your content cannot appear in ChatGPT citations. Add this to your robots.txt:
text
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /
Allow ClaudeBot in robots.txt
Medium Impact ⏱ 2 min
ClaudeBot is blocked — Claude cannot cite your content. Many AI assistants rely on it.
text
User-agent: ClaudeBot
Allow: /

User-agent: anthropic-ai
Allow: /
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 Wislawjournal?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Wislawjournal does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Wislawjournal work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Wislawjournal."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
15
Projected Score
34
Improvement
+19 pts
Allow GPTBot +8 pts
Allow ClaudeBot +5 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