Speed Insights
Incomplete capture
Missing LCP
https://twitter.com/inachu
From Www.x.com/inachu
LCP
N/A
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
47
out of 100
50
out of 100
22/44 rule points
69
out of 100
36/52 rule points
0
out of 100
0/18 rule points
68
out of 100
26/38 rule points
Category point breakdown
Biggest score-losing checks
Remove exposed sensitive files
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response.
Priority
Priority 1: fix before sharing the page publicly.
Fix Prompt
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. robots.txt blocks OAI-SearchBot, Claude-SearchBot, PerplexityBot, and 3 more from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User, meta-externalfetcher, and 1 more from user-requested fetches. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 31%: discovery 11/45, index and snippet eligibility 20/25, synthetic reachability 0/20, sitemap freshness 0/10.
Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
Fix 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 4 violation rule(s), including 2 serious or critical rule(s). Top rules: document-title (1), html-has-lang (1), landmark-one-main (1), page-has-heading-one (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Documents must have <title> element to aid in navigation
Fix any of the following: Document does not have a non-empty <title> element
<html> element must have a lang attribute
Fix any of the following: The <html> element does not have a lang attribute
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
Page should contain a level-one heading
Fix all of the following: Page must have a level-one heading
Fix Prompt
Add responsive viewport metadata
Why this needs attention
The page is missing the viewport meta tag used for mobile layout.
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Recommended correction
Evidence
No viewport meta tag was detected.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Publish a valid sitemap
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
sitemap at /sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Priority
Priority 7: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 2 high, 1 medium, 0 low.
Security
Severity mix: 2 critical, 1 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 1 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 1 high, 2 medium, 1 low.
SEO / AEO
Severity mix: 1 critical, 2 high, 1 medium, 0 low.
Accessibility
Severity mix: 0 critical, 1 high, 0 medium, 0 low.
Security
Severity mix: 2 critical, 1 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 1 high, 2 medium, 1 low.
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. robots.txt blocks OAI-SearchBot, Claude-SearchBot, PerplexityBot, and 3 more from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User, meta-externalfetcher, and 1 more from user-requested fetches. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 31%: discovery 11/45, index and snippet eligibility 20/25, synthetic reachability 0/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
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
sitemap at /sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root. 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
Sensitive file probes
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response. Failed: earned 0 of 16 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 1: 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 4 violation rule(s), including 2 serious or critical rule(s). Top rules: document-title (1), html-has-lang (1), landmark-one-main (1), page-has-heading-one (1). Failed: earned 0 of 18 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Documents must have <title> element to aid in navigation
Fix any of the following: Document does not have a non-empty <title> element
<html> element must have a lang attribute
Fix any of the following: The <html> element does not have a lang attribute
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
Page should contain a level-one heading
Fix all of the following: Page must have a level-one heading
Fix Prompt
Responsive viewport basics
Why this needs attention
The page is missing the viewport meta tag used for mobile layout.
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Recommended correction
Evidence
No viewport meta tag was detected. Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
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
No canonical URL was detected.
Sitemap coverage and freshness
The exact scanned URL was not found in the fetched sitemap.
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 0/100 for “an unnamed subject”. Title/H1 token overlap is 0%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 0/100 from 0 main-content words, 0 concise answer block(s), 0 question heading(s), 0 definition(s), 0 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected other page role.
Published or updated date
Freshness metadata is contextual for the detected other page role.
Supporting-source links
Supporting sources are contextual for the detected other page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 0 visible text element(s).
Synthetic search-agent reachability
0 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://twitter.com/llms.txt returned HTTP 301; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
OpenAIOpenAI model trainingGPTBotModel training
Robots: blocked by * disallow: / · line 100
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: blocked by * disallow: / · line 100
Probe: not tested for this control
AnthropicClaude searchClaude-SearchBotAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed
Probe: redirected · HTTP 301
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: blocked by google-extended disallow: * · line 75
Probe: not tested for this control
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed
Probe: redirected · HTTP 301
PerplexityPerplexity searchPerplexityBotAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
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: blocked by * disallow: / · line 100
Probe: not tested for this control
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Mistral AIMistral searchMistralAI-IndexAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
MetaMeta AI model and product datameta-externalagentModel training
Robots: blocked by meta-externalagent disallow: * · line 89
Probe: not tested for this control
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: blocked by meta-externalfetcher disallow: * · line 95
Probe: not tested for this control
AmazonAmazon model trainingAmazonbotModel training
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Common CrawlOpen web datasetsCCBotModel training
Robots: blocked by * disallow: / · line 100
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.
