The Technical Score measures whether AI crawlers can actually reach and understand your content. It’s one of zued’s two primary KPIs — because perfectly aligned content is irrelevant if AI crawlers can’t access it.
Technical issues always receive the highest priority in zued’s recommendation system. Fix them before any content changes.
Components
| Component | Weight | What it checks |
|---|
| JS Rendering | Highest | How much of your content is visible without JavaScript execution |
| Core Web Vitals | High | LCP, FID/INP, CLS — page load and stability signals |
| Bot Accessibility | High | robots.txt rules and meta robots tags per AI crawler |
| Structured Data | Moderate | Presence and validity of Schema.org markup |
| Meta Tags | Lower | Title tag and meta description presence |
Score levels
| Score | What it means |
|---|
| 90–100 | Excellent — AI crawlers can access and parse your content effectively |
| 70–89 | Minor gaps — typically structured data or meta tag issues |
| 50–69 | Crawlability affected — JS rendering or performance issues |
| < 50 | Critical problems — bot blocking or severe JS dependency |
Bot accessibility
zued checks access individually for each AI crawler: GPTBot, ClaudeBot, PerplexityBot, Bingbot, Google-Extended, and others. A single robots.txt rule or meta robots tag can block one engine while leaving others unaffected.
Blocking an AI crawler in robots.txt or via meta robots means zero visibility for that engine — regardless of content quality. zued flags these as Priority 100 issues.
JS rendering
If your content requires JavaScript to appear, some AI crawlers may never see it. zued compares your page before and after JavaScript execution and flags content that only appears post-render as a crawlability risk.
Structured data
Structured data (Schema.org) is confirmed to assist Copilot’s understanding. Its direct benefit for ChatGPT, Perplexity, and Gemini citation behavior is not established. zued scores its presence accurately for what it affects.
