Speed Insights
Grade A
100% performance
https://local-service-outbound.surge.sh
LCP
264ms
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
80
out of 100
61
out of 100
87/142 rule points
75
out of 100
54/72 rule points
97
out of 100
78/80 rule points
85
out of 100
88/103 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. robots.txt blocks OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more for this page path. 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 20%: discovery 0/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
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 0 of 5 common public security controls. Present: none. Missing: strict-transport-security, 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 72/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
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
HTTP 404 returned for sitemap_xml.
Priority
Priority 7: fix during launch polish.
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 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. 0 result(s) require review. Top rules: region (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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: 1 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 1 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: 1 review and 1 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: 1 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. robots.txt blocks OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more for this page path. 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 20%: discovery 0/45, index and snippet eligibility 20/25, synthetic reachability 0/20, sitemap freshness 0/10. Failed: earned 3 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 72/100, answer-ready text 85/100, semantic structured data 0/100. Detected role: home (high confidence). Failed: earned 24 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
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
Internal link basics
Why this needs attention
The page has too few detectable links to other public pages on the same site.
Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.
Recommended correction
Evidence
Detected 1 internal link(s). Failed: earned 0 of 6 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
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 0 of 5 common public security controls. Present: none. Missing: strict-transport-security, 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 0 of 18 points.
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. 0 result(s) require review. Top rules: region (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
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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 0 commercial proof signal(s) and 1 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
Rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 191ms. Load complete: 682ms. First contentful paint: 264ms. Resources: 10. Scripts: 0. Images: 10. Third-party origins: 10. Transfer: 111KB. Potential render-blocking resources: 0. Exceeded thresholds: Third-party origins 10 origins (threshold 8 origins). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 14: fix during launch polish.
Load contributors
Asset timings are observed request durations. They are not added together because browsers can load requests in parallel.
Third-party origins
2 origins over the rendered audit threshold.
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 does not resolve to the scanned URL: https://viglundur.gumroad.com/l/ymjnoy
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 72/100 for “Cold email + DM scripts that get meetings with plumbers, HVAC, roofers, lawn care & electricians”. Title/H1 token overlap is 57%; description match detected; identity schema not detected.
Answer-ready visible text
Answerability scored 85/100 from 696 main-content words, 1 concise answer block(s), 6 question heading(s), 2 definition(s), 6 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 83 visible text element(s).
Synthetic search-agent reachability
0 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: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
OpenAIOpenAI model trainingGPTBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
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
AnthropicClaude model trainingClaudeBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
GoogleGoogle Search and AI featuresGooglebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
GoogleGemini data use and groundingGoogle-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
MicrosoftBing and CopilotBingbotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
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
AppleSiri, Spotlight, and Safari searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
AppleApple foundation-model trainingApplebot-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
Mistral AIMistral searchMistralAI-IndexFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
MetaMeta AI model and product datameta-externalagentOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
MetaMeta AI user fetchesmeta-externalfetcherFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
AmazonAmazon model trainingAmazonbotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
AmazonAlexa and Rufus searchAmzn-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
AmazonAlexa user fetchesAmzn-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: blocked by * disallow: / · line 2
Synthetic probe: not tested · access is unverified
Controls: robots meta: index,follow
Common CrawlOpen web datasetsCCBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by * disallow: / · line 2
Synthetic probe: not applicable to this policy 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. 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.
