Speed Insights
Grade A
99% performance
https://callify.ai
From callify.ai
LCP
604ms
Largest paint
TBT
8ms
Blocking time
CLS
0.000
Layout shift
39
out of 100
53
out of 100
75/142 rule points
100
out of 100
72/72 rule points
90
out of 100
72/80 rule points
90
out of 100
100/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. AEO crawler readiness is 20%: discovery 0/45, index and snippet eligibility 20/25, synthetic reachability 0/20, sitemap freshness 0/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
Priority
Priority 2: 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 68/100, answer-ready text 70/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
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 a canonical URL
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.
Priority
Priority 9: fix during launch polish.
Fix Prompt
Add relevant structured data
Why this needs attention
The page is missing a primary JSON-LD entity that matches its actual role, or its named entity is not supported by visible content.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
No JSON-LD schema blocks were detected.
Priority
Priority 12: fix during launch polish.
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.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 2 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 2 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: 2 review and 1 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
No failed checks in this category.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 2 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. AEO crawler readiness is 20%: discovery 0/45, index and snippet eligibility 20/25, synthetic reachability 0/20, sitemap freshness 0/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. 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 68/100, answer-ready text 70/100, semantic structured data 0/100. Detected role: home (high confidence). Failed: earned 21 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
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
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
Relevant schema coverage
Why this needs attention
The page is missing a primary JSON-LD entity that matches its actual role, or its named entity is not supported by visible content.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
No JSON-LD schema blocks were detected. 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
Basic contrast
Why this needs attention
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Low contrast makes a launch page feel less polished and can exclude users with low vision.
Recommended correction
Evidence
17 of 287 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 3.27. Mobile 390px viewport: 17 of 287 failed; worst ratio 3.27:1. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
Problems We Solve

to

to
to
Fix Prompt
Rendered composition and spacing
Why this needs attention
Rendered geometry found cramped text, overly long lines, undersized body copy, or too many competing actions in the first viewport.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Desktop 1366px: 2 unique above-fold action(s), 26 body sample(s) below 14px, 0 cramped line-height sample(s), and 6 overlong line sample(s). Mobile 390px: 2 unique above-fold action(s), 26 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Repeated CTA labels are deduplicated and do not earn extra credit. Failed: earned 2 of 7 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 25: 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
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 primary types none. Completeness: 0/100. Graph connectivity: 0/100. 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 68/100 for “Source. Screen. Schedule. Interview. Offer. Collect Documents. Engage. Onboard. CRM”. Title/H1 token overlap is 43%; description match detected; identity schema not detected.
Answer-ready visible text
Answerability scored 70/100 from 1173 main-content words, 10 concise answer block(s), 0 question heading(s), 6 definition(s), 0 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 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
No llms.txt file was found; this is optional and does not reduce core AEO readiness.
OpenAIChatGPT searchOAI-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
OpenAIOpenAI model trainingGPTBotPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
OpenAIChatGPT user fetchesChatGPT-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
AnthropicClaude model trainingClaudeBotPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
AnthropicClaude user fetchesClaude-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: unknown
Synthetic probe: not tested · access is unverified
GoogleGoogle Search and AI featuresGooglebotUNKNOWN · Toggle crawler details
Search and discovery
Robots: unknown
Synthetic probe: not tested · access is unverified
GoogleGemini data use and groundingGoogle-ExtendedPOLICY UNKNOWN · Toggle crawler details
Data-use policy control
Robots: unknown
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotUNKNOWN · Toggle crawler details
Search and discovery
Robots: unknown
Synthetic probe: not tested · access is unverified
PerplexityPerplexity searchPerplexityBotUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
PerplexityPerplexity user fetchesPerplexity-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
AppleSiri, Spotlight, and Safari searchApplebotUNKNOWN · Toggle crawler details
Search and discovery
Robots: unknown
Synthetic probe: not tested · access is unverified
AppleApple foundation-model trainingApplebot-ExtendedPOLICY UNKNOWN · Toggle crawler details
Data-use policy control
Robots: unknown
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
Mistral AIMistral user fetchesMistralAI-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: unknown
Synthetic probe: not tested · access is unverified
MetaMeta AI model and product datameta-externalagentPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherUNKNOWN · Toggle crawler details
User-requested fetch
Robots: unknown
Synthetic probe: not tested · access is unverified
AmazonAmazon model trainingAmazonbotPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
AmazonAlexa user fetchesAmzn-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: unknown
Synthetic probe: not tested · access is unverified
Common CrawlOpen web datasetsCCBotPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
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.
