Rescan Report
Share Report
Copy Report Link
Rescan Report
Share Report
Copy Report Link
Export Report
62/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability42%Agent Easeof Use51%Security& Trust79%GEO, AIO, AEO76%SEO100%Performance86%Accessibility93%
  • AI Discoverability 42 out of 100
  • Agent Ease of Use 51 out of 100
  • Security & Trust 79 out of 100
  • GEO, AIO and AEO 76 out of 100
  • SEO 100 out of 100
  • Performance 86 out of 100
  • Accessibility 93 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

UBS financial services in your location | UBS India favicon

UBS financial services in your location | UBS India

UBS is a global firm providing financial services in over 50 countries. Visit our site to find out what we offer in India.

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.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
42
Priority fix2421View details
Discoverability
20
Priority fix200
Content Readiness
61
Needs work2111View details
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
51
Needs work100
Skill Discovery
54
Needs work100
GEO, AIO and AEO
76
Mostly ready1100
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable500
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
79
Mostly ready2012View details
Security & Trust
79
Mostly ready2012View details
Performance
86
Mostly ready1400
Performance
86
Mostly ready1400

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

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

02

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

  1. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

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=0

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate script execution".

35 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

script-src allows dangerous script schemes: blob:.

02

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

65/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

  1. Evaluate script execution

    script-src allows dangerous script schemes: blob:.

  2. Review hardening directives

    CSP is missing recommended hardening directives: base-uri.

  3. Review CSP reporting

    CSP does not define a reporting endpoint.

Evidence log3 steps · 12 lines
Evaluate script execution [fail]! script-src allows dangerous script schemes: blob:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","'unsafe-inline'","'unsafe-eval'","blob:","*.ubs.com","*.ubs.net","*.adobedtm.com","*.demdex.net","*.decibelinsight.net","*.decibel.com","*.adform.net","*.everesttech.net","*.googleapis.com","*.brightcove.net","*.2o7.net","*.omtrdc.net","*.tt.omtrdc.net","*.zencdn.net","*.akamaihd.net","*.facebook.net","*.googleadservices.com","*.googletagmanager.com","*.google.com","*.doubleclick.net","*.cloudflare.com","*.zmags.com","*.raisenow.com","*.adobe.com","fuse.ubs.com","*.mkt.dynamics.com","*.azureedge.net","*.microsoft.com","*.windows.net","*.adnxs.com","*.ipify.org","*.google-analytics.com","*.tiktok.com","*.datatrans.com","*.paypal.com","snap.licdn.com","*.teads.tv","*.yimg.jp","*.yahoo.co.jp","*.bing.com","*.bing.net","*.adsrvr.org","*.stripe.com","pixel.byspotify.com"]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 hardening directives [warning]! CSP is missing recommended hardening directives: base-uri.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrc=["*.ubs.com","*.ubs.net","https://players.brightcove.net"] formAction=["*.ubs.com","*.ubs.net"] frameAncestors=["*.ubs.com","*.ubs.net","*.homegate.ch","*.financescout24.ch","*.immoscout24.ch","*.acheter-louer.ch","*.buy-rent.ch","*.kaufen-mieten.ch","*.pwj.com","*.credit-suisse.com","*.csintra.net","*.houzy.ch","*.moneyland.ch","*.mkt.dynamics.com","*.azureedge.net","*.microsoft.com"] formCount=0WARNCompare recommended hardening coverage actual=["base-uri"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: base-uri."WARNCSP is missing recommended hardening directives: base-uri.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.

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

0 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are invalid: dateModified (2026-05-14T13:32:45.090+02:00) is earlier than datePublished (2026-05-18T09:55:12.545+02:00)..

Details

02

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

100/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

  1. Corroborate with sitemap lastmod

    Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.

  2. Check date validity and consistency

    dateModified (2026-05-14T13:32:45.090+02:00) is earlier than datePublished (2026-05-18T09:55:12.545+02:00).

Evidence log2 steps · 8 lines
Corroborate 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=1Check date validity and consistency [fail]! dateModified (2026-05-14T13:32:45.090+02:00) is earlier than datePublished (2026-05-18T09:55:12.545+02:00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=1 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2026-05-14T13:32:45.090+02:00) is earlier than datePublished (2026-05-18T09:55:12.545+02:00)."}]FAILInvalid freshness date issue found issues=["dateModified (2026-05-14T13:32:45.090+02:00) is earlier than datePublished (2026-05-18T09:55:12.545+02:00)."]

Sign in to see 40 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Development Note:

Please configure GOOGLE_CLIENT_ID in .env to activate live login.

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

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
62/100Level 3, Bot-AwareCurrent report