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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability38%Agent Easeof Use50%Security& Trust87%GEO, AIO, AEO40%SEO100%Performance96%Accessibility24%
  • AI Discoverability 38 out of 100
  • Agent Ease of Use 50 out of 100
  • Security & Trust 87 out of 100
  • GEO, AIO and AEO 40 out of 100
  • SEO 100 out of 100
  • Performance 96 out of 100
  • Accessibility 24 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Yahoo Search - Web Search favicon

Yahoo Search - Web Search

The search engine that helps you find exactly what you're looking for. Find the most relevant information, video, images, and answers from all across the Web.

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.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
38
Priority fix1031View details
Discoverability
40
Priority fix400
Content Readiness
4
Priority fix331View details
Bot Access Control
63
Needs work300
GEO, AIO and AEO
40
Priority fix200
AIO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong800
SEO
100
Strong800
Security & Trust
87
Mostly ready2221View details
Security & Trust
87
Mostly ready2221View details
Performance
96
Strong1810View details
Performance
96
Strong1810View details

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

Needs attention

Content freshness signals

Failed check
01

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

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

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

  1. Validate Last-Modified header

    No valid Last-Modified HTTP header was found.

  2. Validate structured freshness dates

    No Schema.org freshness dates were found.

  3. Validate metadata freshness dates

    No Open Graph, Dublin Core, or generic meta freshness date was found.

  4. Corroborate with sitemap lastmod

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

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

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

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

42 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

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

    object-src allows broad object/plugin loading.

  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'","'nonce-tPZpb1wZZmQF5VFXfFBoJg=='","'unsafe-eval'","https://*.yahoo.net","https://*.yahoo.com","https://*.yimg.com","https://*.uservoice.com","*.oath.com","https://*.hereapi.com","https://*.youtube.com","*.yahooapis.com","blob:","*.googletagmanager.com"]FAILCompare script execution posture actual={"hasNonce":true,"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 [fail]! object-src allows broad object/plugin loading.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrc=["*"] frameAncestors=["'none'"] formCount=2FAILCompare recommended hardening coverage actual=["base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="object-src allows broad object/plugin loading."FAILobject-src allows broad object/plugin loading.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.

PerformancePerformanceBrowser audit

Font display

100 Fail

Check name

Font display

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 60 ms

Fix guidance

Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).

Evidence
{
  "displayValue": "Est savings of 60 ms",
  "description": "Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks)."
}

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.

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
53/100Level 3, Bot-AwareCurrent report