Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 54 out of 100
- Agent Ease of Use 77 out of 100
- Security & Trust 75 out of 100
- GEO, AIO and AEO 34 out of 100
- SEO 100 out of 100
- Performance 25 out of 100
- Accessibility 93 out of 100
What AI sees of your website
monday.com Marketplace
monday.com app marketplace, Expand the capabilities of your Work OS with monday apps
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 | 54 | Needs work | 22 | 3 | 1 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 16 | Priority fix | 9 | 3 | 1 | View details |
| Bot Access Control | 75 | Mostly ready | 5 | 0 | 0 | |
| Agent Ease of Use | 77 | Mostly ready | 39 | 3 | 1 | View details |
| API | 94 | Strong | 13 | 0 | 0 | |
| Auth | 74 | Needs work | 11 | 0 | 0 | |
| MCP | 57 | Needs work | 2 | 0 | 0 | |
| Skill Discovery | 64 | Needs work | 10 | 3 | 1 | View details |
| Google Agentic Browsing | 100 | Strong | 3 | 0 | 0 | |
| GEO, AIO and AEO | 34 | Priority fix | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| SEO | 100 | Strong | 9 | 0 | 0 | |
| SEO | 100 | Strong | 9 | 0 | 0 | |
| Security & Trust | 75 | Mostly ready | 17 | 1 | 0 | View details |
| Security & Trust | 75 | Mostly ready | 17 | 1 | 0 | View details |
| Performance | 25 | Priority fix | 9 | 0 | 0 | |
| Performance | 25 | Priority fix | 9 | 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.
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.
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=2 attempts=6WARNCheck matching sitemap lastmod actual="invalid match" expected="valid match when available" sitemapUrl="https://monday.com/sitemap-apps-mp.xml" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=6
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
65 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
Needs attention
agents.json
Issue
agents.json does not match the expected Wildcard OpenAPI workflow shape.
Details
Why it matters
Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.
Check name
agents.json
Score
35/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.
Result
agents.json failed at "Validate Wildcard schema shape".
Validation steps
Validate Wildcard schema shape
agents.json does not match the expected Wildcard OpenAPI workflow shape.
agents.json schema shape is invalid or incomplete
Validate API actions
Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.
agents.json action definitions are invalid or missing
Validate flows and links
No executable flows were found.
agents.json flows or links are invalid
Review examples and LLM usability
Examples or descriptions are too thin for reliable agent argument generation.
agents.json examples or descriptions need improvement
Evidence log4 steps · 21 lines
Validate Wildcard schema shape [fail]! agents.json does not match the expected Wildcard OpenAPI workflow shape.INFOValidate Wildcard schema shapeINFOParse agents.json and classify contract shape shape="unknown" version="1.0"FAILCompare contract shape actual="unknown" expected="wildcard"FAILCompare missing required schema fields actual="none" expected="none"FAILCompare Content-Type with JSON expectation actual=true expected=trueINFORecorded remote OpenAPI/schema reference reference="https://api.monday.com/v2/get_schema?format=sdl"INFORecorded remote OpenAPI/schema reference reference="https://monday.com/.well-known/mcp.json"WARNSchema-shape warning warning="schema/spec version 1.0 is newer or different than the researched 0.1.x proposal"WARNSchema-shape warning warning="one or more OpenAPI/schema references are cross-origin"FAILagents.json does not match the expected Wildcard OpenAPI workflow shape.Validate API actions [fail]! Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.INFOValidate API actionsFAILCompare API action count actual=0 expected="> 0"FAILCompare invalid action definitions actual=0 expected=0FAILWildcard agents.json must include valid OpenAPI-derived action or operation definitions.Validate flows and links [fail]! No executable flows were found.INFOValidate flows and linksFAILCompare workflow flow count actual=0 expected="> 0"FAILCompare operation link issues actual=0 expected=0FAILNo executable flows were found.Review examples and LLM usability [warning]! Examples or descriptions are too thin for reliable agent argument generation.INFOReview examples and LLM usabilityWARNCompare usable example count actual=0 expected="> 0 when actions are present"WARNExamples or descriptions are too thin for reliable agent argument generation.
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
60 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
Needs attention
Content-Security-Policy
Issue
Applicable HTML response is missing an enforcing Content-Security-Policy header.
Details
Why it matters
Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.
Check name
Content-Security-Policy
Score
40/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.
Result
Content-Security-Policy failed at "Find enforcing CSP delivery".
Validation steps
Find enforcing CSP delivery
Applicable HTML response is missing an enforcing Content-Security-Policy header.
Enforcing Content-Security-Policy header is missing
Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.Sign in to see 39 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