Evidence: security probe returned HTTP 403. Cloudflare header(s): cf-ray, server, cf-cache-status. URL: https://garageexit.com/.env
Review Cloudflare WAF, bot protection, rate-limit, and challenge rules for public marketing/content routes. Allow safe public scans and legitimate search or AI user-fetch crawlers to reach public pages while keeping admin, authenticated, preview, and private paths protected.
Speed Insights
Grade A
95% performance
https://garageexit.com
From garageexit.com
LCP
1.7s
Largest paint
TBT
112ms
Blocking time
CLS
0.02
Layout shift
89
out of 100
99
out of 100
110/111 rule points
100
out of 100
76/76 rule points
72
out of 100
68/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
Improve AI search and crawler readiness
-1 rule ptsWhat failed
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks Claude-SearchBot, PerplexityBot from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User 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 93%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 10/10.
Priority
Priority 2: fix before sharing the page publicly.
Why it matters
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
How to fix it
Use the component scores and exact matched robots rules in the crawler report. Fix blocked search agents, noindex or snippet restrictions, canonical or sitemap gaps, and synthetic WAF/challenge failures. Preserve intentional training opt-outs and keep private, admin, and authenticated paths protected before rescanning.
Agent Prompt
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (4).
Affected elements
Quick verification to keep subscriptions human.
Main Builder at GarageExit
<a class="font-bold text-brand underline decoration-brand/35 underline-offset-4 transition-colors hover:text-brand-dark focus-visible:outline-none focus-visible:ring-2 focus-visibl
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
How to fix it
Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Agent Prompt
Fix rendered layout ergonomics
-9 rule ptsWhat failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 21.
Affected elements
X
Read the full post
Visit the blog
Priority
Priority 13: fix during launch polish.
Why it matters
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
How to fix it
Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
Agent Prompt
Add trust signals
-10 rule ptsWhat failed
The page does not expose detectable proof, customer, review, security, or credibility signals.
Evidence
Detected 0 trust-signal keyword occurrence(s).
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters
Trust signals reduce hesitation when strangers see the product for the first time.
How to fix it
Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
Agent Prompt
Improve detectable color contrast
-8 rule ptsWhat failed
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Evidence
6 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.89.
Affected elements
A sharp verbal brand makes yours the one
people remember, and choose, first.
Quick verification to keep subscriptions human.
Quick verification to keep subscriptions human.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Why it matters
Low contrast makes a launch page feel less polished and can exclude users with low vision.
How to fix it
Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
Agent Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
Crawler access
13/14FreeScan.app reached the public page with HTTP 200. robots.txt blocks Claude-SearchBot, PerplexityBot from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User 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 93%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 10/10.
Failed: earned 13 of 14 points from partial coverage.
Priority: Priority 2: fix before sharing the page publicly.
Why it matters: AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Fix: Use the component scores and exact matched robots rules in the crawler report. Fix blocked search agents, noindex or snippet restrictions, canonical or sitemap gaps, and synthetic WAF/challenge failures. Preserve intentional training opt-outs and keep private, admin, and authenticated paths protected before rescanning.
Agent Prompt
Basic contrast
0/86 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.89.
Affected elements
A sharp verbal brand makes yours the one
people remember, and choose, first.
Quick verification to keep subscriptions human.
Quick verification to keep subscriptions human.
Failed: earned 0 of 8 points.
Priority: Priority 20: lower-risk cleanup after urgent launch blockers.
Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
Agent Prompt
Rendered axe accessibility violations
0/18axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (4).
Affected elements
Quick verification to keep subscriptions human.
Main Builder at GarageExit
<a class="font-bold text-brand underline decoration-brand/35 underline-offset-4 transition-colors hover:text-brand-dark focus-visible:outline-none focus-visible:ring-2 focus-visibl
Failed: earned 0 of 18 points.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Agent Prompt
Trust signals
0/10Detected 0 trust-signal keyword occurrence(s).
Failed: earned 0 of 10 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters: Trust signals reduce hesitation when strangers see the product for the first time.
Fix: Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
Agent Prompt
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 21.
Affected elements
X
Read the full post
Visit the blog
Failed: earned 0 of 9 points.
Priority: Priority 13: fix during launch polish.
Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Fix: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
Agent 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 URL appears in the fetched sitemap with lastmod 2026-08-22T21:07:45.520Z.
Structured data
Semantic schema score 65/100. Detected 2 JSON-LD block(s), 0 parse error(s), 2 graph node(s), and types Organization, WebSite. The schema type matches the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 70/100 for “Make your product easier to understand and easier to choose.”. Title/H1 token overlap is 0%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 85/100 from 1221 main-content words, 2 concise answer block(s), 1 question heading(s), 22 definition(s), 2 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 123 visible text element(s).
Synthetic search-agent reachability
6 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://garageexit.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 98% parity
OpenAIOpenAI model trainingGPTBotModel training
Robots: blocked by gptbot disallow: / · line 55
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 claudebot disallow: / · line 46
Probe: not tested for this control
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by * allow: / · line 31
Probe: blocked · HTTP 403
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: blocked · HTTP 403
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 98% parity
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: blocked by google-extended disallow: / · line 52
Probe: not tested for this control
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 98% parity
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by * allow: / · line 31
Probe: blocked · HTTP 403
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 31
Probe: reachable · HTTP 200 · 98% parity
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: blocked by applebot-extended disallow: / · line 37
Probe: not tested for this control
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 98% parity
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: blocked · HTTP 403
MetaMeta AI model and product datameta-externalagentModel training
Robots: blocked by meta-externalagent disallow: / · line 58
Probe: not tested for this control
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 98% parity
AmazonAmazon model trainingAmazonbotModel training
Robots: blocked by amazonbot disallow: / · line 34
Probe: not tested for this control
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 98% parity
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 98% parity
Common CrawlOpen web datasetsCCBotModel training
Robots: blocked by ccbot disallow: / · line 43
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.
