Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 71 out of 100
- Agent Ease of Use 51 out of 100
- Security & Trust 94 out of 100
- GEO, AIO and AEO 69 out of 100
- SEO 85 out of 100
- Performance 94 out of 100
- Accessibility 0 out of 100
What AI sees of your website
FormFactor Inc. | Semiconductor Test and Measurement
Industry leader providing advanced solutions for on-wafer test and measurement, including engineering probe stations, analytical probes, probe cards, and 3D surface metrology.
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 | 71 | Needs work | 37 | 0 | 0 | |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 84 | Mostly ready | 26 | 0 | 0 | |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 51 | Needs work | 3 | 2 | 1 | View details |
| Agent Commerce | 72 | Needs work | 2 | 1 | 1 | View details |
| Google Agentic Browsing | 33 | Priority fix | 1 | 1 | 0 | View details |
| GEO, AIO and AEO | 69 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| Security & Trust | 94 | Strong | 25 | 1 | 1 | View details |
| Security & Trust | 94 | Strong | 25 | 1 | 1 | View details |
| Performance | 94 | Strong | 16 | 0 | 0 | |
| Performance | 94 | Strong | 16 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".
28 Fail
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".
Needs attention
ACP - Agentic Commerce Protocol
Issue
ACP discovery returned 429 or 503 without Retry-After.
Details
Why it matters
ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.
Check name
ACP - Agentic Commerce Protocol
Score
72/100
Status
fail
Category
Agent Commerce
Maturity
Informational
Goal
Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.
Result
ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".
Validation steps
Fetch ACP discovery
ACP-like signals were found, but /.well-known/acp.json was not available.
ACP discovery is missing or not parseable
Review ACP cache and retry metadata
ACP discovery returned 429 or 503 without Retry-After.
ACP discovery cache or retry metadata needs review
Evidence log2 steps · 10 lines
Fetch ACP discovery [warning]! ACP-like signals were found, but /.well-known/acp.json was not available.INFOFetch ACP discovery status="warning"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=429 contentType="text/html; charset=UTF-8" parsed=falseINFOFetch compatibility ACP discovery /.well-known/acp statusCode=429 contentType="text/html; charset=UTF-8" parsed=falseWARNCheck canonical ACP discovery response actual=false expected=true canonicalFound=false compatibilityFound=falseWARNACP-like signals were found, but /.well-known/acp.json was not available.Review ACP cache and retry metadata [fail]! ACP discovery returned 429 or 503 without Retry-After.INFOReview ACP cache and retry metadata status="fail"INFOInspect ACP discovery cache headers and retry guidance statusCode=429 cacheControl=null retryAfter=nullFAILCheck Cache-Control header on successful discovery actual="missing" expected="present for cacheable public discovery"FAILCheck Retry-After on rate-limit or unavailable responses actual="not required" expected="present only for 429 or 503"FAILACP discovery returned 429 or 503 without Retry-After.
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate script execution".
27 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate script execution".
Needs attention
Content-Security-Policy
Issue
script-src allows dangerous script schemes: blob:.
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
73/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 "Evaluate script execution".
Validation steps
Evaluate script execution
script-src allows dangerous script schemes: blob:.
CSP script execution policy is unsafe
Review CSP reporting
CSP does not define a reporting endpoint.
CSP reporting is missing or incomplete
Evidence log2 steps · 8 lines
Evaluate script execution [fail]! script-src allows dangerous script schemes: blob:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","*.ceros.com","cdn-cookieyes.com","*.licdn.com","*.matomo.cloud","*.clarity.ms","*.youtube.com","youtu.be","*.ytimg.com","www.googletagmanager.com","*.google.com","*.gstatic.com","*.googleapis.com","*.google-analytics.com","*.opendns.com","*.pingdom.net","*.vimeo.com","'unsafe-inline'","'unsafe-eval'","blob:"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":true,"hasBroadScheme":false,"dangerousSchemes":["blob:"]} expected="constrained script sources without unsafe execution allowances" issue="script-src allows dangerous script schemes: blob:."FAILscript-src allows dangerous script schemes: blob:.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
100 Fail
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
Check name
Accessibility tree is not well-formed
Score
0/100
Status
fail
Device
desktop
Category
Google Agentic Browsing
Fix guidance
A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.
Evidence
{
"description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}Sign in to see 36 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