CrawlProof
View raw .md

AEO Audit for clinikally.com

Target: https://www.clinikally.com/
Score: 51 / 100
Generated: 2026-05-13T10:10:24.994Z
Pages crawled: 9
Findings: 35 pass · 30 warn · 2 fail · 0 unknown


1. Crawl Summary

2. Data Found

Data PointFound?SourceNotes
PricingNo
Customer logosNo
Social proofNo
Recent launchesYesPress/news pageshttps://www.clinikally.com/blogs/news/unlocking-youthful-skin-the-anti-aging-power-of-kale-extract
Blog post activityYesBloghttps://www.clinikally.com/blogs/news/unlocking-youthful-skin-the-anti-aging-power-of-kale-extract
New hiresNoOften only on a /blog/team or LinkedIn page
Headline copyYesHomepageClinikally
PositioningNo
Executive teamNoNavigation links
Product/service descriptionsYesHomepageFrom meta description
Case studies or testimonialsNo
Contact/demo/signup pathsYesNavigation links

3. Homepage Audit

  • Alt text coverage: 41% 88/213 images have alt text.
  • Homepage fetched successfully HTTP 200 · 1741669 bytes · 245ms
  • Page load time: 0.24s Fast — well within AI crawler budgets.
  • declared
  • Single H1 Clinikally
  • <title> present (68 chars)
  • Meta description present (152 chars)
  • Canonical present https://www.clinikally.com/
  • Open Graph tags complete
  • Twitter Card tags complete
  • Critical content is server-rendered Raw and rendered text are within 1% of each other.
  • Content volume: 2787 words Substantive content — AI models have enough to summarize and recommend.
  • Heading structure: 17 (h1:1, h2:11, h3:5) Multiple headings help AI chunk and outline your page.
  • Internal links: 360 360 internal + 57 external links help crawlers navigate.

4. Schema / Structured Data Audit

  • ⚠️ SoftwareApplication missing Adding SoftwareApplication JSON-LD helps LLMs identify your entity.
  • ⚠️ FAQPage JSON-LD missing Add an FAQPage block on pages that answer common questions — high-value for AI summaries.
  • 4 JSON-LD block(s) found Types: Organization, WebPage, WebSite, BreadcrumbList
  • Organization present
  • WebSite present

5. robots.txt and sitemap.xml Audit

  • robots.txt present 5927 chars
  • robots.txt references sitemap(s)
  • sitemap.xml present (8 URLs)

6. LLM / AI Crawler Accessibility

  • ⚠️ Applebot-Extended not explicitly addressed No User-agent: Applebot-Extended block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
  • ⚠️ skill.md missing Add /skill.md describing what your site lets agents do — speeds up agent task routing.
  • ⚠️ /.well-known/security.txt missing Publish a /.well-known/security.txt with at least a Contact: line. Crawlers and security researchers expect it; AI systems use it as a trust signal.
  • GPTBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • ClaudeBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • PerplexityBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • Google-Extended has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • OAI-SearchBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • CCBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • llms.txt present 1010 chars

7. Positioning Clarity

  • ⚠️ No pricing/plans link found AI summaries commonly include pricing. Add a /pricing page even if pricing is custom.
  • ⚠️ Value-prop language not detected Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize.
  • About/Team path discoverable
  • H1 communicates value Clinikally
  • Contact / signup path discoverable

8. Missing or Hard-to-Find Information

  • 7 data point(s) could not be found from public pages · Pricing · Customer logos · Social proof · New hires · Positioning · Executive team · Case studies or testimonials
  • ⚠️ Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.

  • ⚠️ Add alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.

  • ⚠️ Allow Applebot-Extended in robots.txt Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.

  • ⚠️ Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.

  • ⚠️ Publish /.well-known/security.txt A security contact builds trust with crawlers and researchers. Minimal example:

    Contact: mailto:security@yourdomain.com
    Expires: 2027-01-01T00:00:00.000Z
    Preferred-Languages: en
    
  • ⚠️ State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.

  • ⚠️ Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.

  • ⚠️ Add FAQPage JSON-LD Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.

10. Priority To-Do List

  • P2 — Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.

  • P3 — Add alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.

  • P3 — Allow Applebot-Extended in robots.txt Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.

  • P3 — Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.

  • P3 — Publish /.well-known/security.txt A security contact builds trust with crawlers and researchers. Minimal example:

    ```
    Contact: mailto:security@yourdomain.com
    Expires: 2027-01-01T00:00:00.000Z
    Preferred-Languages: en
    ```
    
  • P3 — State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.

  • P3 — Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.

  • P3 — Add FAQPage JSON-LD Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.


Report by CrawlProof. Reusable after every major website change.