Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 64 out of 100
- Agent Ease of Use 50 out of 100
- Security & Trust 73 out of 100
- GEO, AIO and AEO 56 out of 100
- SEO 85 out of 100
- Performance 42 out of 100
- Accessibility 0 out of 100
What AI sees of your website
Retail Technology Solutions - Sensormatic
The global leader in retail systems including RFID, EAS, anti-theft tags & labels, detachers, inventory management & retail traffic solutions.
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 | 64 | Needs work | 30 | 1 | 1 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 68 | Needs work | 18 | 1 | 1 | View details |
| Bot Access Control | 58 | Needs work | 4 | 0 | 0 | |
| Agent Ease of Use | 50 | Needs work | 22 | 4 | 1 | View details |
| API | 44 | Priority fix | 7 | 4 | 1 | View details |
| Auth | 54 | Needs work | 5 | 0 | 0 | |
| MCP | 45 | Priority fix | 2 | 0 | 0 | |
| Agent Commerce | 58 | Needs work | 7 | 0 | 0 | |
| Google Agentic Browsing | 50 | Needs work | 1 | 0 | 0 | |
| GEO, AIO and AEO | 56 | Needs work | 6 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| Security & Trust | 73 | Needs work | 17 | 0 | 0 | |
| Security & Trust | 73 | Needs work | 17 | 0 | 0 | |
| Performance | 42 | Priority fix | 9 | 1 | 0 | View details |
| Performance | 42 | Priority fix | 9 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
63 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
Needs attention
API Catalog
Issue
Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.
Details
Why it matters
API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.
Check name
API Catalog
Score
37/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.
Result
API Catalog failed at "Validate API catalog media type".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not return a 2xx/3xx response.
API catalog HEAD Link discovery is incomplete
Validate API catalog media type
Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.
API catalog media type is not application/linkset+json
Validate Linkset shape
Unexpected token '<', " <!DOCTYPE "... is not valid JSON
API catalog Linkset shape is invalid
Unexpected token '<', " <!DOCTYPE "... is not valid JSON
Classify API catalog relations
API catalog did not include API endpoint links or useful API discovery relations.
API catalog lacks useful API relations
Validate API catalog targets
API catalog did not expose any href targets to validate.
API catalog targets are unreachable or media types mismatch
Evidence log5 steps · 23 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not return a 2xx/3xx response.INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=404 contentType="text/html"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not return a 2xx/3xx response. status="warning"Validate API catalog media type [fail]! Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual="text/html; charset=utf-8" expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.Validate Linkset shape [fail]! Unexpected token '<', " <!DOCTYPE "... is not valid JSONINFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=false expected=trueFAILCompare top-level linkset item count actual=0 expected="> 0"FAILCompare extracted href target count actual=0 expected="> 0"FAILLinkset shape issue issue="Unexpected token '<', \"\r\n\r\n\r\n\r\n<!DOCTYPE \"... is not valid JSON"FAILLinkset JSON parse error error="Unexpected token '<', \"\r\n\r\n\r\n\r\n<!DOCTYPE \"... is not valid JSON"FAILUnexpected token '<', " <!DOCTYPE "... is not valid JSONClassify API catalog relations [fail]! API catalog did not include API endpoint links or useful API discovery relations.INFOClassify API catalog relationsINFOClassify API catalog relation types relations=[] summary={"registered":[],"metadata":[],"adjacent":[],"community":[],"legacy":[],"unknown":[]}FAILCompare registered or metadata API relation count actual=0 expected="> 0"FAILAPI catalog did not include API endpoint links or useful API discovery relations.Validate API catalog targets [fail]! API catalog did not expose any href targets to validate.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILCompare API catalog target failure count actual=0 expected=0FAILAPI catalog did not expose any href targets to validate.
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
45 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.
Details
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
55/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.
Schema.org author attribution is missing or incomplete
Author identity quality
No named author or publisher identity could be extracted.
Author identity quality is incomplete
Evidence log2 steps · 8 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 extracted
PerformancePerformanceBrowser audit
Avoid large layout shifts
100 Fail
PerformancePerformanceBrowser audit
Avoid large layout shifts
Check name
Avoid large layout shifts
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
5 layout shifts found
Fix guidance
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)
References
web.dev/learn/performanceEvidence
{
"displayValue": "5 layout shifts found",
"description": "These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)"
}Sign in to see 54 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