Speed Insights
Incomplete capture
Missing LCP
https://www.betanything.eu
From betanything.eu
LCP
N/A
Largest paint
TBT
646ms
Blocking time
CLS
0.000
Layout shift
35
out of 100
8
out of 100
12/142 rule points
72
out of 100
55/76 rule points
18
out of 100
10/56 rule points
41
out of 100
35/85 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. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, Googlebot, and 5 more. OAI-SearchBot: No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Claude-SearchBot: No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Googlebot: No matching robots.txt rule blocks Googlebot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Bingbot: No matching robots.txt rule blocks Bingbot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. PerplexityBot: No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Applebot: No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. MistralAI-Index: No matching robots.txt rule blocks MistralAI-Index from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Amzn-SearchBot: No matching robots.txt rule blocks Amzn-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. AEO crawler readiness is 25%: discovery 0/45, index and snippet eligibility 5/25, synthetic reachability 20/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 0/100, answer-ready text 0/100, semantic structured data 0/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
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
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 5 violation rule(s); 5 non-contrast rule(s) are scored here, including 3 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: document-title (1), frame-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
Frames must have an accessible name
Fix any of the following: Element has no title attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element's default semantics were not overridden with role="none" or role="presentation"
<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
Fix Prompt
Make the primary CTA obvious
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit.
Priority
Priority 4: fix before sharing the page publicly.
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 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 0 review and 4 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 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: 0 review and 4 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 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. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, Googlebot, and 5 more. OAI-SearchBot: No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Claude-SearchBot: No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Googlebot: No matching robots.txt rule blocks Googlebot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Bingbot: No matching robots.txt rule blocks Bingbot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. PerplexityBot: No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Applebot: No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. MistralAI-Index: No matching robots.txt rule blocks MistralAI-Index from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. Amzn-SearchBot: No matching robots.txt rule blocks Amzn-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 67% sampled-content parity. The page has a noindex signal, so search and citation eligibility is blocked even if crawling is allowed. Relevant page controls: robots meta: NOINDEX, NOFOLLOW. AEO crawler readiness is 25%: discovery 0/45, index and snippet eligibility 5/25, synthetic reachability 20/20, sitemap freshness 0/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. 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
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 0/100, answer-ready text 0/100, semantic structured data 0/100. Detected role: home (high confidence). Failed: earned 0 of 40 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
No title tag was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 8: fix during launch polish.
Fix Prompt
Meta description
Why this needs attention
No meta description was detected in the public page metadata.
Without a description, search and answer previews may select less useful page text automatically.
Recommended correction
Evidence
No meta description was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Heading structure
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 0 visible H1 heading(s) and 0 visible heading(s) in the page markup. Heading-level order is assessed separately under Accessibility. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: 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 0 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
Indexability signals
Why this needs attention
The page appears to tell crawlers not to index it.
A noindex directive can prevent the launch page from appearing in search results.
Recommended correction
Evidence
A noindex directive was detected. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 2: fix before sharing the page publicly.
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 0 visible internal link target(s) in the page markup. 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
Visible cookie flags
Why this needs attention
The safe public scan could not inspect private or browser-set cookies, so cookie flag coverage was not verified.
Session and preference cookies should avoid unnecessary exposure before early users sign in or submit forms.
Recommended correction
Evidence
Observed 2 cookie(s) without storing names or values. Secure: 0/2. HttpOnly: 1/2. SameSite: 0/2. SameSite=None without Secure: 0. Failed: earned 1 of 4 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Heading order
Why this needs attention
Heading levels appear to jump or start without a clear hierarchy.
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Recommended correction
Evidence
Visible heading levels found: none (page markup). Failed: earned 0 of 11 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Fix Prompt
Landmark presence
Why this needs attention
The page is missing common landmarks such as header, nav, main, or footer.
Landmarks make the page easier to navigate for assistive technology and keyboard users.
Recommended correction
Evidence
Detected 0 visible main landmark(s) and 0 visible landmark element(s) or roles. A page should expose one main landmark. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
Fix Prompt
HTML language
Why this needs attention
The html lang attribute is missing.
Screen readers use the language attribute to pronounce content correctly.
Recommended correction
Evidence
No html lang attribute was detected. The page text appears to be en, but detected language cannot replace an explicit declaration for assistive technology. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 19: lower-risk cleanup after urgent launch blockers.
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 5 violation rule(s); 5 non-contrast rule(s) are scored here, including 3 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: document-title (1), frame-title (1), html-has-lang (1), landmark-one-main (1), page-has-heading-one (1). Failed: earned 2 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
Documents must have <title> element to aid in navigation
Fix any of the following: Document does not have a non-empty <title> element
Frames must have an accessible name
Fix any of the following: Element has no title attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element's default semantics were not overridden with role="none" or role="presentation"
<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
Fix Prompt
Visible primary CTA
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 4: fix before sharing the page publicly.
Fix Prompt
Hero clarity signals
Why this needs attention
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 0 visible H1 heading(s), 0 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 0 actionable CTA(s). Static page markup was used because rendered semantic evidence was unavailable. The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. Detected role: home (high confidence). Failed: earned 0 of 13 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Text density
Why this needs attention
The page may not provide enough useful context for its detected role, or its rendered structure needs review.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 6 visible word(s) in the page markup. The contextual range is 120-1200 words for the detected home page role. Failed: earned 1 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
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 0 source or methodology signal(s) for this home page. 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
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: 170ms. Load complete: 715ms. First contentful paint: not available. Largest contentful paint: not available. Total blocking time: 646ms. Cumulative layout shift: 0. Resources: 1. Scripts: 0. Images: 0. Third-party origins: 0. Transfer: 734KB. Potential render-blocking resources: 0. Metrics outside the good range: Total blocking time 646ms (good at or below 200ms; poor range). Failed: earned 6 of 10 points from partial coverage.
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.
Total blocking time
446ms 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
A general noindex directive prevents search indexing and citation eligibility.
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 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 6 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 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 1 visible text element(s).
Synthetic search-agent reachability
8 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: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: NOINDEX, NOFOLLOW
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: NOINDEX, NOFOLLOW
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: NOINDEX, NOFOLLOW
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
GoogleGoogle Search and AI featuresGooglebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: NOINDEX, NOFOLLOW
MicrosoftBing and CopilotBingbotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
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: NOINDEX, NOFOLLOW
AppleSiri, Spotlight, and Safari searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: NOINDEX, NOFOLLOW
Mistral AIMistral searchMistralAI-IndexFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: NOINDEX, NOFOLLOW
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: NOINDEX, NOFOLLOW
AmazonAlexa and Rufus searchAmzn-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 67% sampled-content parity
Controls: robots meta: NOINDEX, NOFOLLOW
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: NOINDEX, NOFOLLOW
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.
