Speed Insights
Grade A
99% performance
https://web-git-feature-socialdata-opportunity-radar-back-7e43bb-ex-eks.vercel.app
LCP
1.1s
Largest paint
TBT
9ms
Blocking time
CLS
0.000
Layout shift
76
out of 100
28
out of 100
40/142 rule points
81
out of 100
58/72 rule points
98
out of 100
78/80 rule points
95
out of 100
105/110 rule points
Category point breakdown
Biggest score-losing checks
For your AI agent
Share this audit’s URL with ChatGPT, Claude, or your coding agent to turn findings into fixes. Your agent can open the saved evidence below when it needs more detail; these files never start a new scan.
Agent-readable files
Improve AI search and crawler readiness
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, Googlebot, and 5 more. OAI-SearchBot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Claude-SearchBot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Googlebot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Bingbot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. PerplexityBot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Applebot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. MistralAI-Index: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Amzn-SearchBot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. AEO crawler readiness is 25%: discovery 0/45, index and snippet eligibility 5/25, synthetic reachability 20/20, sitemap freshness 0/10.
Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
Add common public security headers
Why this needs attention
Several browser protection headers are missing or present only as weak, narrow policies.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 1 of 5 common public security controls. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Needs strengthening: none.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Strengthen answer-engine content quality
Why this needs attention
The page is technically discoverable, but its entity clarity, answer-ready copy, structured data, evidence, authorship, or freshness is not yet complete.
Search and answer systems need clear, extractable, verifiable facts in addition to crawl access and metadata.
Recommended correction
Evidence
Role-aware AEO content components: entity clarity 60/100, answer-ready text 85/100, semantic structured data 0/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Remove noindex signals
Why this needs attention
The page appears to tell crawlers not to index it.
A noindex directive can prevent the launch page from appearing in search results.
Recommended correction
Evidence
A noindex directive was detected.
Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
Shorten the meta description
Why this needs attention
The meta description is 207 characters, so it is longer than the recommended maximum.
Long descriptions are likely to be truncated or rewritten, which can hide the most useful part of the message.
Recommended correction
Evidence
Meta description is 207 characters, above the 170-character maximum.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 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, 6 medium, 0 low. Coverage: 0 review and 2 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, 8 high, 3 medium, 1 low. Coverage: 0 review and 2 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 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.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
Failed checks
These checks need attention.
Crawler access
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, Googlebot, and 5 more. OAI-SearchBot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Claude-SearchBot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Googlebot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Bingbot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. PerplexityBot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Applebot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. MistralAI-Index: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. Amzn-SearchBot: No robots.txt file was published, so this token is allowed by default. Synthetic User-Agent probe returned HTTP 200 with 97% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: index, follow; X-Robots-Tag: noindex. AEO crawler readiness is 25%: discovery 0/45, index and snippet eligibility 5/25, synthetic reachability 20/20, sitemap freshness 0/10. Failed: earned 4 of 14 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
Answer-engine content quality
Why this needs attention
The page is technically discoverable, but its entity clarity, answer-ready copy, structured data, evidence, authorship, or freshness is not yet complete.
Search and answer systems need clear, extractable, verifiable facts in addition to crawl access and metadata.
Recommended correction
Evidence
Role-aware AEO content components: entity clarity 60/100, answer-ready text 85/100, semantic structured data 0/100. Detected role: home (high confidence). Failed: earned 22 of 40 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 74 characters. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 8: fix during launch polish.
Fix Prompt
Meta description
Why this needs attention
The meta description is 207 characters, so it is longer than the recommended maximum.
Long descriptions are likely to be truncated or rewritten, which can hide the most useful part of the message.
Recommended correction
Evidence
Meta description is 207 characters, above the 170-character maximum. 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
Canonical tag
Why this needs attention
The page does not declare which public URL is the preferred version.
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Recommended correction
Evidence
No canonical link tag was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
robots.txt reachability
Why this needs attention
The standard crawler instruction file was not reachable.
A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives.
Recommended correction
Evidence
HTTP 404 returned for robots_txt. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 11: fix during launch polish.
Fix Prompt
Sitemap validity
Why this needs attention
The sitemap file was not reachable or did not look like valid sitemap XML.
A sitemap helps search engines discover the landing page and related public pages sooner.
Recommended correction
Evidence
HTTP 404 returned for sitemap_xml. Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: fix during launch polish.
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
Open Graph basics
Why this needs attention
The page is missing several social preview fields.
Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.
Recommended correction
Evidence
Detected 2 of 4 Open Graph basics. Failed: earned 0 of 5 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Indexability signals
Why this needs attention
The page appears to tell crawlers not to index it.
A noindex directive can prevent the launch page from appearing in search results.
Recommended correction
Evidence
A noindex directive was detected. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
Common security headers
Why this needs attention
Several browser protection headers are missing or present only as weak, narrow policies.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 1 of 5 common public security controls. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Needs strengthening: none. Failed: earned 4 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
Rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 1 violation rule(s); 1 non-contrast rule(s) are scored here, including 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: landmark-unique (1). Failed: earned 16 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.
Affected elements
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
Fix any of the following: The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
Fix Prompt
Credibility and proof
Why this needs attention
The page does not expose enough verifiable credibility for its detected role.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 1 commercial proof signal(s) and 0 source or methodology signal(s) for this home page. Failed: earned 5 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: 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
A general noindex directive prevents search indexing and citation eligibility.
Snippet and answer controls
No general nosnippet or max-snippet:0 control was detected.
Canonical alignment
No canonical URL was detected.
Sitemap coverage and freshness
Sitemap coverage could not be verified.
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. The primary schema entity was not clearly supported by visible page content.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 60/100 for “Find where your next customers are already talking.”. Title/H1 token overlap is 17%; description match detected; identity schema not detected.
Answer-ready visible text
Answerability scored 85/100 from 688 main-content words, 6 concise answer block(s), 0 question heading(s), 9 definition(s), 8 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 audit completed with 108 visible text element(s).
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-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow; X-Robots-Tag: noindex
OpenAIChatGPT user fetchesChatGPT-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
Controls: robots meta: index, follow; X-Robots-Tag: noindex
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow; X-Robots-Tag: noindex
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
GoogleGoogle Search and AI featuresGooglebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow; X-Robots-Tag: noindex
MicrosoftBing and CopilotBingbotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
PerplexityPerplexity user fetchesPerplexity-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
Controls: robots meta: index, follow; X-Robots-Tag: noindex
AppleSiri, Spotlight, and Safari searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow; X-Robots-Tag: noindex
Mistral AIMistral searchMistralAI-IndexFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow; X-Robots-Tag: noindex
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow; X-Robots-Tag: noindex
AmazonAlexa and Rufus searchAmzn-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 97% sampled-content parity
Controls: robots meta: index, follow; X-Robots-Tag: noindex
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow; X-Robots-Tag: noindex
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. 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.
