Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 33 out of 100
- Agent Ease of Use 59 out of 100
- Security & Trust 76 out of 100
- GEO, AIO and AEO 50 out of 100
- SEO 100 out of 100
- Performance 100 out of 100
- Accessibility 76 out of 100
What AI sees of your website
LinkedIn: meld u aan of schrijf u in
Meer dan 1 miljard leden | Beheer uw professionele identiteit. Bouw uw professionele netwerk op en breid dit uit. Krijg toegang tot kennis, ideeën en nieuwe mogelijkheden.
Next step
Turn this report into a fix workflow
3 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 33 | Priority fix | 11 | 3 | 1 | View details |
| Discoverability | 20 | Priority fix | 2 | 0 | 0 | |
| Content Readiness | 9 | Priority fix | 6 | 3 | 1 | View details |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 59 | Needs work | 2 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 2 | 0 | 0 | |
| GEO, AIO and AEO | 50 | Needs work | 4 | 2 | 3 | View details |
| GEO Readiness | 42 | Priority fix | 1 | 2 | 3 | View details |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 76 | Mostly ready | 20 | 1 | 1 | View details |
| Security & Trust | 76 | Mostly ready | 20 | 1 | 1 | View details |
| Performance | 100 | Strong | 15 | 0 | 0 | |
| Performance | 100 | Strong | 15 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
7 items need attention
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
100 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.
Details
Why it matters
Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.
Check name
Content freshness signals
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval, citation, and ranking.
Result
Content freshness signals is missing or incomplete.
Validation steps
Validate Last-Modified header
No valid Last-Modified HTTP header was found.
Validate structured freshness dates
No Schema.org freshness dates were found.
Validate metadata freshness dates
No Open Graph, Dublin Core, or generic meta freshness date was found.
Corroborate with sitemap lastmod
Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.
Evidence log4 steps · 16 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [fail]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaFAILCheck structured freshness date count actual=0 expected="> 0" invalidDateCount=0 formats={} alternateDates=[]FAILNo structured freshness dates foundValidate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=1WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=1
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection failed at "Validate CSP frame-ancestors".
40 Fail
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection failed at "Validate CSP frame-ancestors".
Needs attention
Frame protection
Issue
frame-ancestors contains invalid source expressions: *.www.linkedin.com:*.
Why it matters
Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking and UI redressing risk.
Check name
Frame protection
Score
60/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.
Result
Frame protection failed at "Validate CSP frame-ancestors".
Validation steps
Validate CSP frame-ancestors
frame-ancestors contains invalid source expressions: *.www.linkedin.com:*.
Review CSP and XFO interaction
CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.
Evidence log2 steps · 8 lines
Validate CSP frame-ancestors [fail]! frame-ancestors contains invalid source expressions: *.www.linkedin.com:*.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=true reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=1 duplicateDirectives=[]FAILCompare effective frame-ancestors directive actual={"values":["'self'","*.www.linkedin.com:*"],"mode":"malformed","valid":false,"restrictive":false,"broadSources":[]} expected="valid restrictive enforcing frame-ancestors" issue="frame-ancestors contains invalid source expressions: *.www.linkedin.com:*."FAILframe-ancestors contains invalid source expressions: *.www.linkedin.com:*.Review CSP and XFO interaction [warning]! CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.INFOReview CSP and XFO interactionINFOCompare modern CSP and legacy XFO behavior modernBrowserMechanism="csp-frame-ancestors" cspOverridesXfo=true cspMode="malformed" xfoDirective="sameorigin"WARNCheck CSP/XFO policy alignment actual="aligned or single mechanism" expected="no conflicting framing policy" issue="CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting."WARNCSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: AI retrieval access
GEO: AI retrieval access scored 0/100 and needs a fix.
7 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: AI retrieval access
GEO: AI retrieval access scored 0/100 and needs a fix.
Needs attention
GEO: AI retrieval access
Issue
Relevant AI retrieval crawler(s) appear blocked for this URL: ChatGPT-User, PerplexityBot, Perplexity-User, ClaudeBot, Claude-SearchBot, Claude-User. Snippet or data-nosnippet controls restrict extractable/citable text.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: AI retrieval access
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: AI retrieval access scored 0/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 35/100 and needs a fix.
5 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 35/100 and needs a fix.
Needs attention
GEO: Citable passages
Issue
No evidence-backed, citation-length explanatory paragraph was found.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Citable passages
Score
35/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Citable passages scored 35/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 50/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 50/100 and needs improvement.
Needs attention
GEO: Source and trust signals
Issue
Missing source or trust signals: authorOrOwner, freshnessDate, entityLinks.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Source and trust signals
Score
50/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Source and trust signals scored 50/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 63/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 63/100 and needs improvement.
Needs attention
GEO: Structured extraction
Issue
Missing or weak extraction signals: summary or key takeaways, FAQ or question-answer section where appropriate, typed JSON-LD structured data.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Structured extraction
Score
63/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Structured extraction scored 63/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 85/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Entity clarity
GEO: Entity clarity scored 85/100 and needs improvement.
Needs attention
GEO: Entity clarity
Issue
Title/H1 terms missing from description: linkedin, meld, aan, schrijf, welkom, bij, community.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Entity clarity
Score
85/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Entity clarity scored 85/100 and needs improvement.
Sign in to see 35 other issues and the full report
Create a free account to unlock every issue, evidence details, exports, and higher free limits.
Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history