Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 51 out of 100
- Agent Ease of Use 62 out of 100
- Security & Trust 54 out of 100
- GEO, AIO and AEO 46 out of 100
- SEO 92 out of 100
- Performance 40 out of 100
- Accessibility 93 out of 100
What AI sees of your website
SinCode
Discover, use and build agents to create your personal AI agent team.
Next step
Turn this report into a fix workflow
2 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 | 51 | Needs work | 23 | 4 | 2 | View details |
| Discoverability | 40 | Priority fix | 4 | 0 | 0 | |
| Content Readiness | 28 | Priority fix | 10 | 4 | 2 | View details |
| Bot Access Control | 77 | Mostly ready | 9 | 0 | 0 | |
| Agent Ease of Use | 62 | Needs work | 24 | 1 | 2 | View details |
| API | 73 | Needs work | 5 | 1 | 2 | View details |
| Auth | 67 | Needs work | 10 | 0 | 0 | |
| MCP | 45 | Priority fix | 2 | 0 | 0 | |
| Skill Discovery | 60 | Needs work | 5 | 0 | 0 | |
| Google Agentic Browsing | 67 | Needs work | 2 | 0 | 0 | |
| GEO, AIO and AEO | 46 | Priority fix | 5 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 54 | Needs work | 10 | 0 | 0 | |
| Security & Trust | 54 | Needs work | 10 | 0 | 0 | |
| Performance | 40 | Priority fix | 12 | 0 | 0 | |
| Performance | 40 | Priority fix | 12 | 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.
Last-Modified freshness signal is missing or invalid
Validate structured freshness dates
No Schema.org freshness dates were found.
Structured freshness dates are missing or invalid
Validate metadata freshness dates
No Open Graph, Dublin Core, or generic meta freshness date was found.
Metadata freshness dates are missing or invalid
Corroborate with sitemap lastmod
Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.
Sitemap lastmod corroboration is missing
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
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
27 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
Needs attention
API Catalog
Issue
API catalog target https://agent.ai/api/specs/openapi.json (service-desc) returned HTTP 403 instead of a 2xx/3xx response.
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
73/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 targets".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
API catalog HEAD Link discovery is incomplete
Validate API catalog media type
Content-Type "application/json; charset=utf-8" is JSON-compatible but not application/linkset+json.
API catalog media type is not application/linkset+json
Validate API catalog targets
API catalog target https://agent.ai/api/specs/openapi.json (service-desc) returned HTTP 403 instead of a 2xx/3xx response.
API catalog targets are unreachable or media types mismatch
Evidence log3 steps · 21 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="application/json; charset=utf-8"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [warning]! Content-Type "application/json; charset=utf-8" is JSON-compatible but not application/linkset+json.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/json; charset=utf-8" expected="application/linkset+json"WARNCompare JSON compatibility fallback actual=true expected=trueWARNContent-Type "application/json; charset=utf-8" is JSON-compatible but not application/linkset+json. status="warning"Validate API catalog targets [fail]! API catalog target https://agent.ai/api/specs/openapi.json (service-desc) returned HTTP 403 instead of a 2xx/3xx response.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILAPI catalog target failed validation rel="service-desc" href="https://agent.ai/api/specs/openapi.json" statusCode=403 contentType="text/html; charset=UTF-8" advertisedType="application/vnd.oai.openapi+json" typeMatches=falseSKIPSkipped API catalog target fetch rel="service-doc" href="https://docs.agent.ai/api-reference" resolvedUrl="https://docs.agent.ai/api-reference" reason="Same-site target was recorded but not fetched."PASSAPI catalog target is reachable rel="service-meta" href="https://agent.ai/.well-known/oauth-authorization-server" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="service-meta" href="https://agent.ai/.well-known/oauth-protected-resource" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"SKIPSkipped API catalog target fetch rel="item" href="https://mcp.agent.ai/mcp" resolvedUrl="https://mcp.agent.ai/mcp" reason="Same-site target was recorded but not fetched."FAILAPI catalog target failed validation rel="item" href="https://agent.ai/ask" statusCode=403 contentType="text/html; charset=UTF-8" typeMatches=truePASSAPI catalog target is reachable rel="item" href="https://agent.ai/.well-known/agent-card.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"PASSAPI catalog target is reachable rel="item" href="https://agent.ai/.well-known/ai-plugin.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"PASSAPI catalog target is reachable rel="item" href="https://agent.ai/.well-known/agent.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"FAILCompare API catalog target failure count actual=3 expected=0FAILAPI catalog target https://agent.ai/api/specs/openapi.json (service-desc) returned HTTP 403 instead of a 2xx/3xx response.
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
22 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
Sign in to see 41 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