Last scanned Sep 24, 2026 · Methodology v4.7 · View Leaderboard →
Very little readable content on this page
The page carried too few words for content-dependent checks to mean much. Scores that depend on the text are reported with that limit rather than as findings about your writing.
named.net scored 24/100 on AI-readiness across 48 parameters measured against ChatGPT, Claude, Grok, Perplexity, and Gemini visibility checks. 9 parameters passed, 28 failed, and 2 need improvement. Strongest area: Crawlability & Access. Weakest: Discovery & Metadata. Compared to other Other sites, this score is in the 21st percentile.
9 Pass
28 Fail
2 Needs Improvement
These are derived on-page readiness estimates for each engine's grounding index — not live engine queries.
How easily AI engines can extract and cite this page. Combines freshness, schema, and answer-block placement.
Freshness
Fresh — last modified 0 days ago. Inside the 7–14 day refresh window AI engines reward.
Source:last_modified_headerFreshness: page modified 0 days ago. Inside Perplexity 2–3 day window. Inside 13-week recent band. Far from 26-week at-risk threshold.
Perplexity 2–3dSchema / Structured Data
No structured data detected. Schema.org markup states what a page is about in a form assistants parse directly, instead of leaving them to infer it from prose.
Answer Block
No answer block in the first 200 words. Your first 200 words contain navigation, a {{introWordCount}}-word intro, and a product description. Open with a 40–60 word direct answer.
No answer block detected.
Parameters that determine how well AI crawlers can discover and index your content.
robots.txt accessibilityLearn more | Pass |
HTTP status and reachabilityLearn more | Pass |
Fail | |
Pass | |
AI crawler access controlLearn more | Pass |
Paywall and login gating detectionLearn more | Pass |
Search-bot network reachabilityLearn more | Pass |
sitemap.xml availabilityLearn more | Partial |
Structured Data (schema.org)Learn more | Fail |
Page metadataLearn more | Fail |
URL stabilityLearn more | Fail |
Structured data (schema.org/JSON-LD) coverageLearn more | Fail |
Security headers baselineLearn more | Fail |
Fail | |
Internal link coverageLearn more | Fail |
Content-type schema alignmentLearn more | N/A |
IndexNow push-protocol adoptionLearn more | Fail |
Entity grounding via sameAs linksLearn more | Fail |
N/A | |
N/A | |
N/A | |
Fail | |
Fail | |
N/A |
Fail | |
Content visibility without JavaScriptLearn more | Fail |
Pass | |
Fail | |
Nosnippet directive detectionLearn more | Pass |
Paragraph length distributionLearn more | Fail |
Section length distributionLearn more | Fail |
Dated statistics ratioLearn more | N/A |
Comparison table presenceLearn more | N/A |
Entity name consistencyLearn more | N/A |
Multimedia coverage and alignmentLearn more | Fail |
AI manifests coverageLearn more | Fail |
Fail | |
UCP manifest availabilityLearn more | N/A |
Pass | |
Core Web Vitals (page experience)Learn more | Fail |
Parameters that influence how AI systems cite and surface your content in answers.
N/A | |
N/A | |
N/A | |
Fail | |
Fail | |
Fail | |
N/A | |
Pass |
Fail | |
Pass | |
Pass | |
Author authority signalsLearn more | Fail |
Fail | |
Content depthLearn more | Fail |
Citation and evidence densityLearn more | Fail |
Fail | |
Answer-oriented content structureLearn more | Fail |
Answer-first H2 complianceLearn more | Fail |
Chunk extractability (self-contained H2 blocks)Learn more | Fail |
TL;DR / Key Takeaways sectionLearn more | Fail |
Answer block shapeLearn more | Partial |