Speed Insights
Not captured
No performance data
https://datafa.st
From datafa.st
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
86
out of 100
80
out of 100
82/102 rule points
96
out of 100
69/72 rule points
79
out of 100
54/68 rule points
88
out of 100
74/84 rule points
Category point breakdown
Biggest score-losing checks
Label public form fields
Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 0 of 4 eligible user-facing form control(s).
Priority
Priority 7: fix during launch polish.
Fix Prompt
Add a useful meta description
Why this needs attention
The page does not expose a strong short summary for search and answer engines.
A missing description makes previews weaker when early users share or find the page.
Recommended correction
Evidence
Meta description is 189 characters.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Add common public security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 4 of 5 common public security controls. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: frame protection (x-frame-options or content-security-policy frame-ancestors).
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Add basic structured data
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s).
Priority
Priority 12: fix during launch polish.
Fix Prompt
Balance landing page copy
Why this needs attention
The page has too little or too much detectable text for a useful launch page.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 1971 visible word(s). General page range: 80-1800 words.
Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 2 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low. Coverage: 0 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 2 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low. Coverage: 0 review and 0 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
Failed checks
These checks need attention.
Meta description
Why this needs attention
The page does not expose a strong short summary for search and answer engines.
A missing description makes previews weaker when early users share or find the page.
Recommended correction
Evidence
Meta description is 189 characters. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Schema presence
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
Fix Prompt
Common security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 4 of 5 common public security controls. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: frame protection (x-frame-options or content-security-policy frame-ancestors). Failed: earned 15 of 18 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Form labels
Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 0 of 4 eligible user-facing form control(s). Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: fix during launch polish.
Fix Prompt
Text density
Why this needs attention
The page has too little or too much detectable text for a useful launch page.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 1971 visible word(s). General page range: 80-1800 words. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Page-level AEO readiness
Shared eligibility and content signals that affect every search and answer agent.
Index and citation eligibility
No general noindex directive was detected.
Snippet and answer controls
No general nosnippet or max-snippet:0 control was detected.
Canonical alignment
The canonical resolves to the scanned public URL.
Sitemap coverage and freshness
A sitemap index was found; this safe scan did not recursively fetch child sitemaps.
Structured data
Semantic schema score 0/100. Detected 0 JSON-LD block(s), 0 parse error(s), 0 graph node(s), and types none. No primary schema type matched the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 55/100 for “Revenue-first analytics”. Title/H1 token overlap is 0%; description match detected; identity schema not detected.
Answer-ready visible text
Answerability scored 90/100 from 1247 main-content words, 5 concise answer block(s), 1 question heading(s), 12 definition(s), 7 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected home page role.
Published or updated date
Freshness metadata is contextual for the detected home page role.
Supporting-source links
Supporting sources are contextual for the detected home page role and do not affect readiness.
Rendered content availability
Rendered browser audit could not run in this environment.
Synthetic search-agent reachability
8 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
No llms.txt file was found; this is optional and does not reduce core AEO readiness.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
AnthropicClaude model trainingClaudeBotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 99% parity
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.
The image refreshes from FreeScan after a completed rescan. Clicking it always opens the newest public report saved for this exact scanned URL.
Scan evidence is included as untrusted data. The implementation brief instructs agents to verify findings before editing and to avoid destructive or speculative changes.
