Speed Insights
Incomplete capture
Missing LCP
https://x.com/inachu
From x.com/inachu
LCP
N/A
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
81
out of 100
73
out of 100
75/103 rule points
79
out of 100
60/76 rule points
79
out of 100
68/86 rule points
91
out of 100
100/110 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 56%: discovery 11/45, index and snippet eligibility 25/25, synthetic reachability 20/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
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
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
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 1 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 3 high, 4 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 1 low.
Accessibility
Severity mix: 0 critical, 3 high, 4 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 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 56%: discovery 11/45, index and snippet eligibility 25/25, synthetic reachability 20/20, sitemap freshness 0/10. Failed: earned 8 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
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
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
Trust signals
Why this needs attention
The page does not expose detectable proof, customer, review, security, or credibility signals.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 trust-signal keyword occurrence(s). Failed: earned 0 of 10 points.
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
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
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 70/100 for “inachu”. Title/H1 token overlap is 100%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 43/100 from 125 main-content words, 0 concise answer block(s), 0 question heading(s), 1 definition(s), 2 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected directory page role.
Published or updated date
Freshness metadata is contextual for the detected directory page role.
Supporting-source links
Supporting sources are contextual for the detected directory page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 0 visible text element(s).
Synthetic search-agent reachability
2 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://x.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OAI-SearchBotAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
GPTBotModel training
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
ClaudeBotModel training
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
Claude-SearchBotAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
Claude-UserUser-requested fetch
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
GooglebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Google-ExtendedData-use policy control
Robots: blocked by google-extended disallow: * · line 75
Probe: not tested for this control
Controls: robots meta: index, follow
BingbotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
PerplexityBotAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
ApplebotSearch and discovery
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
Applebot-ExtendedData-use policy control
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
MistralAI-IndexAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
MistralAI-UserUser-requested fetch
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
meta-externalagentModel training
Robots: blocked by meta-externalagent disallow: * · line 89
Probe: not tested for this control
Controls: robots meta: index, follow
meta-externalfetcherUser-requested fetch
Robots: blocked by meta-externalfetcher disallow: * · line 95
Probe: not tested for this control
Controls: robots meta: index, follow
AmazonbotModel training
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
Amzn-SearchBotAI search
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
Amzn-UserUser-requested fetch
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
CCBotModel training
Robots: blocked by * disallow: / · line 100
Probe: not tested for this control
Controls: robots meta: index, follow
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.
