Speed Insights
Grade B
87% performance
https://moinvit.com
From moinvit.com
LCP
3.7s
Largest paint
TBT
0ms
Blocking time
CLS
0.001
Layout shift
22
out of 100
37
out of 100
53/142 rule points
75
out of 100
54/72 rule points
34
out of 100
24/70 rule points
77
out of 100
78/101 rule points
Category point breakdown
- Search discovery is materially blocked.
- Material high-impact failures span 4 categories.
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 99% 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 99% 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 99% 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 99% 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 99% 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 99% 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 99% 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 99% 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 30%: discovery 0/45, index and snippet eligibility 10/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
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 40/100, answer-ready text 45/100, semantic structured data 0/100. Detected role: home (high confidence).
Priority
Priority 6: 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 5 violation rule(s); 5 non-contrast rule(s) are scored here, including 1 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: link-name (1), landmark-one-main (1), region (15), skip-link (1), aria-allowed-role (6).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers 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 has no title attribute
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
Fix Prompt
Remove noindex 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.
Priority
Priority 2: 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 1 not applicable.
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.
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. 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 99% 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 99% 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 99% 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 99% 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 99% 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 99% 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 99% 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 99% 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 30%: discovery 0/45, index and snippet eligibility 10/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 40/100, answer-ready text 45/100, semantic structured data 0/100. Detected role: home (high confidence). Failed: earned 13 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
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 2 visible H1 heading(s) and 13 visible heading(s) in the rendered page. Heading-level order is assessed separately under Accessibility. Failed: earned 3 of 8 points from partial coverage.
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
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
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
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 1 visible internal link target(s) in the rendered page. 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
Image alt text
Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 0 image(s) with no alt attribute and 14 image(s) with empty alt text that appear informative, out of 26. 0 empty-alt image(s) looked decorative and were not counted as failures. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 11: fix during launch polish.
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: 1, 1, 2, 2, 2, 2, 6, 6, 6, 6, 6, 6, 2 (rendered page). 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 2 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
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 1 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: link-name (1), landmark-one-main (1), region (15), skip-link (1), aria-allowed-role (6). Failed: earned 7 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
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers 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 has no title attribute
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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 2 visible H1 heading(s), 25 H1 characters, 122 introductory supporting-copy characters after excluding bylines and short labels, and 12 actionable CTA(s). Rendered evidence was used where available. 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 9 of 13 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
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: 4 unique above-fold action(s), 0 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Mobile 390px: 4 unique above-fold action(s), 2 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. More than three distinct actions compete in a captured first viewport. 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
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: 4561ms. Load complete: 5566ms. First contentful paint: 3376ms. Largest contentful paint: 3732ms. Total blocking time: 0ms. Cumulative layout shift: 0.001. Resources: 89. Scripts: 27. Images: 9. Third-party origins: 2. Transfer: 1035KB. Potential render-blocking resources: 62. Metrics outside the good range: DOMContentLoaded 4561ms (good at or below 2500ms); Load complete 5566ms (good at or below 4500ms); First contentful paint 3376ms (good at or below 2200ms); Largest contentful paint 3732ms (good at or below 2500ms); Script requests 27 scripts (good at or below 20 scripts). 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.
DOMContentLoaded
2061ms over the rendered audit threshold.
Load complete
1066ms over the rendered audit threshold.
First contentful paint
1176ms over the rendered audit threshold.
Largest contentful paint
1232ms 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
The canonical resolves to the scanned public URL.
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 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 40/100 for “Undangan Digital Kekinian”. Title/H1 token overlap is 0%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 45/100 from 503 main-content words, 0 concise answer block(s), 1 question heading(s), 0 definition(s), 10 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 45 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 · 99% 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 · 99% 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 · 99% 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 · 99% 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 · 99% sampled-content parity
Controls: robots meta: noindex, nofollow
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 99% 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 · 99% 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 · 99% 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 · 99% 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 · 99% 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 · 99% 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 · 99% 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.
To refresh your Pro site score and fixes, open your Pro dashboard and run a site audit.
