Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 56 out of 100
- Agent Ease of Use 61 out of 100
- Security & Trust 89 out of 100
- GEO, AIO and AEO 67 out of 100
- SEO 92 out of 100
- Performance 84 out of 100
- Accessibility 100 out of 100
What AI sees of your website
Document Automation, Web Forms & SharePoint Tools | Plumsail
Plumsail automates document generation, web forms, and customer support for Microsoft 365 and SharePoint, helping teams save time and cut manual work.
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 | 56 | Needs work | 25 | 1 | 0 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 60 | Needs work | 16 | 0 | 0 | |
| Bot Access Control | 45 | Priority fix | 1 | 1 | 0 | View details |
| Agent Ease of Use | 61 | Needs work | 4 | 1 | 0 | View details |
| Skill Discovery | 55 | Needs work | 2 | 1 | 0 | View details |
| Google Agentic Browsing | 100 | Strong | 2 | 0 | 0 | |
| GEO, AIO and AEO | 67 | Needs work | 9 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 89 | Mostly ready | 25 | 2 | 1 | View details |
| Security & Trust | 89 | Mostly ready | 25 | 2 | 1 | View details |
| Performance | 84 | Mostly ready | 17 | 0 | 0 | |
| Performance | 84 | Mostly ready | 17 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
69 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
Details
Why it matters
AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.
Check name
AI bot rules in robots.txt
Score
31/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.
Result
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Validation steps
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
47 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
Needs attention
Content-Security-Policy
Issue
CSP does not define default-src; several fetch directives may have no restrictive fallback.
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
53/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 fetch baseline".
Validation steps
Evaluate fetch baseline
CSP does not define default-src; several fetch directives may have no restrictive fallback.
CSP fetch baseline is too broad or missing
Evaluate script execution
No script-src or default-src directive constrains script execution.
CSP script execution policy is unsafe
Review hardening directives
CSP is missing recommended hardening directives: object-src, form-action.
CSP hardening directives are missing or weak
Evidence log3 steps · 12 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=[]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives baseUri=["'self'"] frameAncestors=["'self'","https://account.plumsail.com","https://auth.plumsail.com","https://forms.plumsail.com"] formCount=1WARNCompare recommended hardening coverage actual=["object-src","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, form-action."WARNCSP is missing recommended hardening directives: object-src, form-action.
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".
29 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".
Needs attention
DNS-AID Agent Discovery
Issue
One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.
Details
Why it matters
DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.
Check name
DNS-AID Agent Discovery
Score
71/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.
Result
DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".
Validation steps
Validate HTTPS/SVCB shape
One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.
DNS-AID HTTPS/SVCB records are malformed
Malformed record issues
[ { "ownerName": "_index._agents.plumsail.com", "rrtype": "HTTPS", "ttl": 300, "mode": "unknown", "targetName": "61", "params": [ { "key": "00", "value": "present" }, { "key": "01", "value": "present" }, { "key": "00", "value": "present" }, { "key": "00", "value": "present" }, { "truncated": true, "omittedCount": 57, "originalCount": 61 } ], "mandatory": [], "alpn": [], "endpointIssue": "missing endpoint", "unknownParams": [ "00", "01", "00", "00", { "truncated": true, "omittedCount": 57, "originalCount": 61 } ], "parseWarnings": [ "SvcPriority is missing or not numeric." ], "source": "cloudflare-doh-json", "raw": "\\# 61 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 08 68 15 15 b6 ac 43 c7 c9 00 06 00 20 26 06 47 00 30 30 00 00 00 00 00 00 68 15 15 b6 26 06 47 00 30 31 00 00 00 00 00 00 ac 43 c7 c9" }, { "ownerName": "_a2a._agents.plumsail.com", "rrtype": "HTTPS", "ttl": 300, "mode": "unknown", "targetName": "61", "params": [ { "key": "00", "value": "present" }, { "key": "01", "value": "present" }, { "key": "00", "value": "present" }, { "key": "00", "value": "present" }, { "truncated": true, "omittedCount": 57, "originalCount": 61 } ], "mandatory": [], "alpn": [], "endpointIssue": "missing endpoint", "unknownParams": [ "00", "01", "00", "00", { "truncated": true, "omittedCount": 57, "originalCount": 61 } ], "parseWarnings": [ "SvcPriority is missing or not numeric." ], "source": "cloudflare-doh-json", "raw": "\\# 61 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 08 68 15 15 b6 ac 43 c7 c9 00 06 00 20 26 06 47 00 30 30 00 00 00 00 00 00 68 15 15 b6 26 06 47 00 30 31 00 00 00 00 00 00 ac 43 c7 c9" } ]
Evidence log1 step · 6 lines
Validate HTTPS/SVCB shape [fail]! One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.INFOValidate HTTPS/SVCB shapeFAILCompare parsed DNS-AID record count actual=2 expected="> 0"FAILCompare ServiceMode record count actual=0 expected="> 0"FAILDNS-AID record has parse/shape warnings ownerName="_index._agents.plumsail.com" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILDNS-AID record has parse/shape warnings ownerName="_a2a._agents.plumsail.com" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILOne or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.Sign in to see 31 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