Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 68 out of 100
- Agent Ease of Use 50 out of 100
- Security & Trust 46 out of 100
- GEO, AIO and AEO 64 out of 100
- SEO 92 out of 100
- Performance 66 out of 100
- Accessibility 0 out of 100
What AI sees of your website
IT Support Company - Forum Info-Tech - IT Solutions That FIT
Your IT shouldn’t be lagging behind, it should be leading the pack. Choose our IT support company to be your guiding light and grow.
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 | 68 | Needs work | 35 | 1 | 0 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 75 | Mostly ready | 24 | 1 | 0 | View details |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 50 | Needs work | 1 | 1 | 0 | View details |
| Google Agentic Browsing | 50 | Needs work | 1 | 1 | 0 | View details |
| GEO, AIO and AEO | 64 | Needs work | 8 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 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 | 46 | Priority fix | 8 | 1 | 0 | View details |
| Security & Trust | 46 | Priority fix | 8 | 1 | 0 | View details |
| Performance | 66 | Needs work | 14 | 0 | 0 | |
| Performance | 66 | Needs work | 14 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
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.AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
0 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are invalid: dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)..
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
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
Check date validity and consistency
dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).
Freshness dates are invalid or inconsistent
Evidence log1 step · 4 lines
Check date validity and consistency [fail]! dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).; dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=16 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."},{"severity":"fail","message":"dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."}]FAILInvalid freshness date issue found issues=["dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).","dateModified (2026-04-16T15:30:12+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).","dateModified (2026-04-16T15:30:56+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).","dateModified (2026-04-17T13:55:57+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00).","dateModified (2026-06-12T00:11:45+00:00) is earlier than datePublished (2026-06-12T13:09:00+00:00)."]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 40 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
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 51/100 | Level 3, Bot-Aware | Current report |