Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 41 out of 100
- Agent Ease of Use 60 out of 100
- Security & Trust 97 out of 100
- GEO, AIO and AEO 44 out of 100
- SEO 92 out of 100
- Performance 99 out of 100
- Accessibility 89 out of 100
What AI sees of your website
SemanticDiff for GitHub
SemanticDiff allows you to review GitHub commits and pull requests using a language aware diff.
Next step
Turn this report into a fix workflow
1 failed check is 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 | 41 | Priority fix | 13 | 5 | 2 | View details |
| Discoverability | 40 | Priority fix | 4 | 0 | 0 | |
| Content Readiness | 13 | Priority fix | 6 | 5 | 2 | View details |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 60 | Needs work | 7 | 0 | 0 | |
| API | 93 | Strong | 6 | 0 | 0 | |
| Auth | 48 | Priority fix | 1 | 0 | 0 | |
| GEO, AIO and AEO | 44 | Priority fix | 3 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| SEO | 92 | Strong | 8 | 0 | 0 | |
| SEO | 92 | Strong | 8 | 0 | 0 | |
| Security & Trust | 97 | Strong | 25 | 0 | 0 | |
| Security & Trust | 97 | Strong | 25 | 0 | 0 | |
| Performance | 99 | Strong | 19 | 1 | 0 | View details |
| Performance | 99 | Strong | 19 | 1 | 0 | View details |
| Accessibility | 89 | Mostly ready | 3 | 0 | 0 | |
| Accessibility | 89 | Mostly ready | 3 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
50 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
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
35 Warning
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
Needs attention
Author attribution
Issue
No named author or publisher identity could be extracted.
Why it matters
Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.
Check name
Author attribution
Score
30/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Identify content authors or publishers for trust and attribution.
Result
Author attribution is partially implemented.
Validation steps
Schema.org attribution
Schema.org attribution is incomplete or relies only on publisher/fallback evidence.
Author identity quality
No named author or publisher identity could be extracted.
Visible byline parity
Structured author/publisher names were not found in visible byline text.
Evidence log3 steps · 12 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extractedVisible byline parity [fail]! Structured author/publisher names were not found in visible byline text.INFOVisible byline parityINFOComparing structured contributor names with visible byline evidenceFAILCheck visible attribution matches actual=0 expected="> 0 or visible byline present" visibleByline=false bylineCount=0FAILNo visible byline parity found
PerformancePerformanceBrowser audit
LCP request discovery
100 Fail
PerformancePerformanceBrowser audit
LCP request discovery
Check name
LCP request discovery
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
References
web.dev/learn/performanceEvidence
{
"description": "[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading"
}Sign in to see 27 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