Evidence: landing page returned HTTP 403. Cloudflare header(s): cf-ray, server, cf-mitigated, content-security-policy. URL: https://aiagentskills.net
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
98% performance
https://aiagentskills.net
LCP
384ms
Largest paint
TBT
85ms
Blocking time
CLS
0.000
Layout shift
50
out of 100
41
out of 100
18/44 rule points
92
out of 100
48/52 rule points
0
out of 100
0/18 rule points
68
out of 100
26/38 rule points
Category point breakdown
Biggest score-losing checks
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
page fetch returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks OAI-SearchBot, Claude-SearchBot, Googlebot, and 3 more from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User from user-requested fetches. AEO crawler readiness is 72%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 7/20, sitemap freshness 0/10.
Priority
Priority 2: 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 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Delayed refresh under 20 hours must not be used
Fix any of the following: <meta> tag forces timed refresh of page (less than 20 hours)
Fix Prompt
Add responsive viewport metadata
Why this needs attention
The page is missing the viewport meta tag used for mobile layout.
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Recommended correction
Evidence
No viewport meta tag was detected.
Priority
Priority 3: fix before sharing the page publicly.
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 403 returned for sitemap_xml.
Priority
Priority 7: fix during launch polish.
Fix Prompt
Add common public security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 4 of 5 common public security controls. Present: content-security-policy, x-content-type-options, frame protection (x-frame-options), referrer-policy. Missing: strict-transport-security.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 2 high, 1 medium, 0 low.
Security
Severity mix: 2 critical, 1 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 1 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 1 high, 2 medium, 1 low.
SEO / AEO
Severity mix: 1 critical, 2 high, 1 medium, 0 low.
Accessibility
Severity mix: 0 critical, 1 high, 0 medium, 0 low.
Security
Severity mix: 2 critical, 1 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 1 high, 2 medium, 1 low.
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
page fetch returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks OAI-SearchBot, Claude-SearchBot, Googlebot, and 3 more from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User from user-requested fetches. AEO crawler readiness is 72%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 7/20, sitemap freshness 0/10. Failed: earned 0 of 14 points.
Priority
Priority 2: fix before sharing the page publicly.
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 403 returned for sitemap_xml. Failed: earned 0 of 12 points.
Priority
Priority 7: fix during launch polish.
Fix Prompt
Common security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 4 of 5 common public security controls. Present: content-security-policy, x-content-type-options, frame protection (x-frame-options), referrer-policy. Missing: strict-transport-security. Failed: earned 14 of 18 points from partial coverage.
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), including 1 serious or critical rule(s). Top rules: meta-refresh (1). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Delayed refresh under 20 hours must not be used
Fix any of the following: <meta> tag forces timed refresh of page (less than 20 hours)
Fix Prompt
Responsive viewport basics
Why this needs attention
The page is missing the viewport meta tag used for mobile layout.
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Recommended correction
Evidence
No viewport meta tag was detected. Failed: earned 0 of 12 points.
Priority
Priority 3: fix before sharing the page publicly.
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
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.
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 0 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 8 visible text element(s).
Synthetic search-agent reachability
2 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://aiagentskills.net/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed by oai-searchbot allow: / · line 27
Probe: challenged · HTTP 403 · 0% parity
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed by gptbot allow: / · line 27
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: allowed by claudebot allow: / · line 27
Probe: not tested for this control
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by claude-searchbot allow: / · line 27
Probe: challenged · HTTP 403 · 0% parity
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by claude-user allow: / · line 27
Probe: challenged · HTTP 403 · 0% parity
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by googlebot allow: / · line 27
Probe: challenged · HTTP 403 · 0% parity
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed by google-extended allow: / · line 27
Probe: not tested for this control
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by bingbot allow: / · line 27
Probe: reachable · HTTP 200 · 0% parity
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by perplexitybot allow: / · line 27
Probe: challenged · HTTP 403 · 0% parity
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 applebot allow: / · line 27
Probe: challenged · HTTP 403 · 0% parity
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed by applebot allow: / · line 27
Probe: not tested for this control
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 2
Probe: challenged · HTTP 403 · 0% parity
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: challenged · HTTP 403 · 0% parity
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 0% parity
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 0% parity
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 0% parity
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed by * allow: / · line 2
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.
